Arrow768

Imho this is a very interesting take. As mentioned above, a lot of jobs are already pretty closely regulated by ooc guidelines which determine what you can and can not do. Therefore I think the skill system would be more useful in applying certain (mechanical) restrictions to the character, if the player so chooses. I.e. that could be a inability to perform certain tasks, taking slightly more damage, ...

Given that each player was talked to for quite a while before being turned into one of these "pets", I do not see how it is gank given that there was roleplay involved. In any case, this was not ahelped by the players in question. I´ll leave the log-diving to alberyk, but I want to point out a few things: I have asked multiple times if there are any questions and advised them to ahelp or use aooc if there are any issues or questions. I specifically mentioned: "Your primary goal however is not to kill "everyone" you come across." I gave instructions that they should roleplay with the people before they knock them out and move them to the "back room". The players that have been "turned" have been offered to get TCB after 15min. I advised them to relocate the shuttle once a large amount of security arrives. (To avoid a firefight situation) This has been dealt with in the round, so I do not see how it is relevant for the complaint. Unless you are dissatisfied with the outcome of the ahelp someone else made, I again do not see how this is relevant for a staff complaint. I am a bit confused about that response, because above you said that "what really made you [make]" the complaint was the shuttle gank and the "ganking" that occured when people were turned. I want to re-iterate again that we do not have a accepted policy that limits the types of events that can be run.

I am only going to address a few more things here and then wait for Alberyk. (Two parts because the forum doesnt like it in one part) First of all. I do not have direct control over the actions the players take. I can only indirectly influence the players by making recommendations or providing guidelines that they should follow. If they follow these guidelines is up to the individual players. Once they do not follow them, I can take action again. Quite similar to how the rules enforcement works; (What that action is depends on what they did.) In this case a player activated the turrets on the shuttle and the player has been dealt with as a result of that action. I should also mention that everyone except the captain decided to try and fight out that situation instead of ahelping it as the gank that it was. If security had not responded to the fight, informed the entire station of it and instead ahelped it, I could have rejuved the people involved and we could have "reverted" that situation. When the entire station is aware of a fight and the fight has escalated to the degree it has,, a "rejuv and revert" is pretty much out of the question. Therefore my only option left was to deal with the player who activated the turrets. So much for the players activating a "killbox" on the shuttle. In the future, if you think something is gank, ahelp immediately and dont inform the entire station of it. (That just limits the options) Regarding the claims of OP gear. Given my experience with the past events and antag-rounds it is pretty clear that antags require somewhat decent gear to deal with security once they come running with proper gear. (Especially if its 4 antags vs 1 full security department) If the antags are not geared properly security will steamroll them at the first escalation. Given that a merc-team also has 4 people, I did not see an issue with allowing them access to the standard-gear of a merc team. Again, these things rely on the players escalating properly.

Ill keep it short. The following custom event info was set: Indicating that it will not be completely canon and pretty much telling people to expect deaths. (This was for the people that got moved into the animals tough; I didnt expect the shootout.) The shootout in the shuttle was not planned and has been ahelped by someone else and handled. At the start of the round the antags were advised that they should try to avoid killing unless it is required. (Given how events usually go) You were also advised to ahelp in the round if you had any issues with the conduct of the antags, which you did not do. Regarding non-canon LRP events (which the animal-transfer part was clearly intendet to be): You have made a policy suggestion about that in the past which has been rejected.

Recently there has been a discord discussion about faxing Central Command. A few misconceptions about faxes and CCIA have been floating around in that discussion. To clear them up and explain a few things, I have created this topic. Formatting Your fax should look somewhat decent. In times long gone by, faxes would regularly get rejected with a "Invalid Fax Format" announcement for minor mistakes in the form. This no longer happens, but you should still try to make a fax look "decent". You can start doing that by using one of the forms in the forms database in the message consoles. I recommend to start with the "General Fax" (ID 1002) or the "Situation Report" (ID 0108). These two are good enough for most messages that are sent between the station and CentCom. When writing your fax, make sure to be clear and concise. You will not loose your command whitelist / get your character demoted if you use a improper fax format. Fax Content One of the regular questions that gets asked is if a gimmick by Antags is "real". The problem with that question is, that revealing the antagonists (too early) will stop whatever story they are trying to drive. As revealing the antagonist is counterproductive it will not happen until the late-/end-game (when it has become obvious that the are not who they claim to be). Another common topic is "faxing for direct intervention". As command member you are expected to deal with issues that arise on the station without needing external support. You are generally expected to handle situations with the resources available to you. For example, faxing for a emergency response team is pointless when you are capable of launching the distress beacon. However sometimes there might be situations where you are unable to deal with these situations with the available resources. At that point you should send a fax or EBS mentioning the danger, why you are unable to deal with it and what response you would like. When the round is coming to an end, you can send a fax to central command requesting them to take certain actions (i.e. have a medic-team on stand-by, ...) CCIA has the capability to enable various spawners on the Odin (i.e. checkpoint-security, medical-team). Keep in mind that some more complex things might require a admin intervention to set that up (and some time). In addition, all the requests that need odin-characters are dependent on ghosts willing to play them. Fax Timing You do not have to write a fax, informing Central Command about a active shooter the moment they show up. It is perfectly fine to handle the incident first and then write a report about it, if there is time to do so afterwards. It is also fine not to report it at all if you do not have time to do so. One of the messages that you might get when you are on red alert past the 2h mark with little "movement" is the "Alert Status With no Reports". This message is usually used as a subtle way of letting you know that you should consider wraping up the round as it has been dragging on for a while. Consider if you need additional resources to deal with the situation (Possibly call a ERT). If you can spare the time, inform Central Command about the biggest issue you face and if you need something to resolve it. Afterwards proceed to resolve it. One of the complaints that has been voiced is that it often takes people 10+ minutes to write a fax. You do not have to take soo much time, if you do not want to. A clear and concise fax is perfectly fine. For example if there are mercs shooting up your departments, you could just write: "We have 4 shooters on board the station. Security is currently handling the situation. A ERT might be required later on and will be requested by activating the distress beacon if needed." When to send a message to Central Command There are a few cases when you really should send a message: You want something from Central Command You have been asked to to provide some information to Central Command. There is something that is likely impact the Odin Primarily if you intent to transfer a artifact/dangerous prisoner/... to the Odin/ on the crew shuttle. However that does not mean that you can only send a message in these cases. You can always send a fax to Central Command for roleplay purposes if you want to. How to send the message You have two primary options of sending a message: Fax EBS (Emergency Broadcast System) If the situation you want to contact Central Command about is not critical or unlikely to impact operations on the Odin, you should use a fax. If there is an emergency or it is likely that the situation has a impact on the Odin (i.e. there has been a fight in departures and you need a medical response team upon arrival) you should use a EBS.

We have recently added the requirement that command-whitelisteed players must have their forum account linked to their ckey. This serves two goals: It helps us ensure that all whitelisted players have access to the section of the forum reserved for command whitelisted players by automating the assignment of the forum group. It enables us to consolidate our role- and permission-management infrastructure to a single location in a followup-project which simplifies the management of the permissions and roles that are assigned across our various services (server, discord, forum, bots, ...) We are currently in the process of rolling out this requirement. To check if you have linked your forum-account to your ckey, you can take a look at the post-info-bit and check if your ckey is displayed there. (You might have to visit this on a computer/switch to desktop-view; See the attached image below) You can also log into the Web-Interface by visiting: https://byond.aurorastation.org and checking if you can see your characters. If you do not have your ckey linked, visit this URL: https://byond.aurorastation.org/user/link Afterwards a linking-request should show up if you join the game. If it does not, use the "OOC -> Check Linking Requests" command.

I was wondering when that application was going to happen given the number of PRs made by you.

AFAIK this is already the case. However the current implementation uses UTC as the time base (as that makes it easier to match a ic time to a log time) So all that would be needed is a wiki update.

DM a Headmin/dev with the request to delete the account.

Moving the spare to the backroom and using tamper resistant electronics for the airlocks in the captains office sounds reasonable secure. The only other weird thing that I noticed so far were the two double airlocks, followed by a single airlock which lead to the consular section.

Not a fan of the captains office. The proposed design is much less secure now than it was before due to the windows/door exposed directly to the public hallway.

Regarding Confidential Complaints: First of all: Read the entirety of this post if you consider creating a confidential complaint We have recently added the ability to create confidential complaints. The confidential complaints are created in the confidential complaints forum. Do not create a confidential complaint in the character/player/staff-complaints forum. A confidential complaint is initially only visible to the Headmins/devs and the author of the complaint. Other people can be enabled to see/respond to the complaint as needed. (This will be announced in the complaint) Usually the person that is accused will be enabled to see and respond to the complaint. The purpose of confidential complaints is to handle sensitive topics. The subject of the complaint does not have to be a character or player; It can also be a staff member. Before creating a confidential complaint contact a headmin/dev (depending on the subject of the complaint) to determine if your complaint is suitable for that category.

The exchange rate has been removed from the wiki to prevent arguments like this. Given that we do not have a exchange rate on the wiki, this argument is as pointless as any other argument about removed lore. The point remains that we have 140k in the station accounts. A custom item that can give a player 71% of the money in all station accounts whenever the player in question chooses to is a very substantial ic advantage and raises balance concerns. There is no way something like that would be merged.

It seems really weird that someone would bring a collectors item that is "at LEAST 100.000 credits [worth to them]" every day to their workplace.

You have received a 24h posting restriction on the forum (basically what we use as a forum ban for "soft" cases) for abusive behavior on March 20, 2021. Over the last 2 years you have received a relatively large number of notes and warnings for abusive behavior (both in the game and on the forum) In the head of staff whitelist rules we have the following requirement: I do not believe that you should receive a head of staff whitelist at this time because you continuously fail to meet community standards. (Be that our ingame rules or forum rules)

I have to agree with that. It would make sense from a IC perspective to have a crematorium in the morgue, but from a gameplay perspective it would be questionable to do that for the aforementioned reason. For things like monkeys the crusher is a perfectly capable of taking care of them. Or you could go the route of cross-department coordination and ask another department to dispose of these things for you.

The preferences of all the existing players have been updated, so ghost looc is enabled by default. (As a result of the poll regarding that matter) The default preferences include ghostlooc so all new players will see ghost looc by default.

These are the results of the poll: Question: Should LOOC be removed from ghosts? I do not care: 29 Yes: 53 No: 104 Given that and the implementation of the toggle-able ghost-looc this is considered implemented and will be moved to completed projects

I’ll look into this on the weekend and close/archive this as necessary.

Due to technical constraints the number of items that can be selected (per gear slot) needs to be limited to 15 items. This limit also needs to be tweakable by configuration file in case it is revealed that this limit is too high (or too low).

This will be handled by @Garnascus in the evening. Make sure to account for the rules of this forum when considering if you should post or not.

Seconding the vote for dismissal for the above stated reasons.

If the AI is being problematic in terms of access, then you are encouraged to ahelp. The high importance areas (mentioned in law 1) are clearly defined in the station procedures and there is also a clarification what authorised means on the wiki: As for who actually counts as "authorized" in relation to law 1 and 4, they'd be the following: Persons who have direct access to an area (a security office having access to most of security, as an obvious example). Persons who have been authorized to enter an area by someone with direct access. Emergency responders (EMTs, engineers, etc.) who are responding to an ongoing emergency in the area, relevant to their job.

To clear something up: We plan to monitor how this PR works out over the coming weeks (as usual) and plan to make changes to it if needed.