Arrow768

Moving to rejected suggestions due to 2 dismissals

Moving to rejected suggestions due to the votes for dismissal

Seconding the vote for dismissal for the reasons stated above. Moving to Rejected suggestions.

Yes, it is slightly more difficult to get around maint for some antags, but ultimately all of them have means to deal with that and it is more likely that they will be undisturbed in maint, even if they just go to the areas they have access to anyway. All antags can access the directly adjacent maint tunnels to their departments, while being relatively sure that they wont be disturbed in there Traitors can buy the agent id card for 3 tcs (that makes them untrackable by the AI, if they so desire and comes with maint access) Vampires can use their abilities to get maint access Lings can ling a engineer Cult/Revs can convert someone that has access or can grant them that access I am currently looking into a few options to make it easier to enable maint access if its needed: Move emergency maint access from the swipers to the command console, so a single head of staff can enable it Give heads of staff limited ability to modify ID cards (Hand out the access they have to id cards) Tie security maint access to the current alert level

Well, as I mentioned during the conversation, I am not sold on it, as the current away missions + helping science/botany is not a lot to support a role.

The argument was made that its difficult to search maint with 4 officers by multiple people, however they failed to account for all the other security staffers. My response just corrects them. Departmental security is unrelated to this topic. Edit: I dont appreciate editing your post after it has been responded to @Sheveningan, and I´ll just ignore the added content as thats now way to have a discussion.

I am going to address a few things: There are 4 officers, 2 cadets, a detective, a CSI, a HoS and a warden who can all potentially join a search in maint. And 10 people (or 9 if we ignore the warden) are easily able to search maint in an efficient manner. Paramedics regularly have to respond to miners or other injured people out on the asteroid and use the airlocks in maint to get there as fast as possible. The only regular threat security canonically encounters in maint is cavern dwellers. There is no need to respond urgently to cavern dwellers, as they arnt exactly fast when it comes to breaking down windows and even if they do, its just a broken window and a area vented. With the small number of people that have access to maint, the danger of that is minimal, so security officers can just get an engineer and have them acompany them through maint. (And maybe even fix the damage the dwellers did at the same time) Sure, if they are bad at their job. A HoS can coordinate with the other heads of staff and/or the AI to get maint access for his officers if there is a severe threat. They can also hand out guest passes to the officers that allows them to access maint. There are quite a few options: Get a head of staff to assign it to them (either through the hop, by using the spare id, or other means) Get someone with access to issue them a guest pass Get command to enable emergency maint access In addition, I am also considering to grant them the access automatically on certain alert levels (in the OP), however I first want to see how this PR is going to work out without the additional access on elevated alert levels.

This Pull Request reduces the number of people that have access to maint tunnels to: Engineering, because they are trained to perform maintenance. Paramedics, because they regularly need to access airlocks in the maint tunnels. Janitors, because they need to access the crusher. Heads of Staff, because they are the heads. What this pull request is not changing: The mapped in access departments have to the directly adjacent maint tunnels. Assistant Maint Access, because that is a config option; However that option is likely to be disabled once that pull request is merged. What is the advantage of that pull request: It makes it easier for antagonists to hide out in maint and escape areas (at the start) as there is not a constant security patrol in there and security officers cant follow them, unless they acquire access to the maint tunnels. It prevents the roundstart rush to maint from security to "clear potentially dangerous items". It might get security to include players from other departments (engineers / paramedics) in whatever is going on due to their initial access (at least until security managed to acquire access on their own) Potential follow-up PRs: Depending on how this changes the dynamic once its merged, a potential follow up might include automatic maint access for security on elevated alert levels.

It's quite intentional that the faction is taken into account for the merchant, as this prevents the player from reusing a station character as merchant.

Has been merged. Moving to the archive.

Trial has been successfully completed on 2019-11-11 Therefore moving the app to the archive

Since this suggestion is based on incorrectly presented information (as pointed out by Matt) I am voting for dismissal

Well, I really dont like the wording of the law with the attached "excluding hivebots".

Your complaint to me was "that there is a serious conflict of interest [due to their IC interactions with Marwani]" and that you believe this post is too influenced by your IC interactions. As this post raised valid questions and Evandorf was not handling the complaint, I saw no reason to remove that post. I also told you to report posts that you believe violate forum rules. To reiterate: Your complaint to me was about a potential conflict of interest they had when making a post on your player complaint/ban request. I handled that and informed you that I dont see them being influenced by any IC actions (also they did not handle your complaint). I also advised you later on to report any forum posts that you believe violate rules. You never told me that you want to complain to me about their IC interactions with you, so I didnt handle that as I assumed it was just to provide context to your complaint about the post being too influenced. As you should know, we have a player complaint forum to handle stuff like that.

Well, I forgot to take care of that. Trial started on the 26.10.19

https://github.com/Aurorastation/Aurora.3/pull/7278

Given that both Skull and I disagreed with this suggestion and the way that escalated I´m gonna move that to the bin. As outlined above, Mice are already played in a way that is often problematic and this would just extend to station pets (who are even more visible than mice)

I have to concur with what Garn said. The peacekeepers is not a good fit. This has also been suggested in the topic that caused the removal of the borg and has been rejected back then aswell (if I remember correctly) Therefore I am second Ing the vote for dismissal on this topic. However I would not be opposed to a new module if there is a gap that needs to be filled and that gap is not filled by porting a bad meme. (but that's something for a new topic)

Yup I have to concur, mice are often played very badly and I don't see why this would be different with pets. Unless we whitelist them.

Moving to rejected due to inactivity and dismissal by Alb.

As mentioned by alb, you can already ahelp those with unbelievable prescriptions due to the "power gaming" and "believable character" rules Therefore second Ing the vote for dismissal.

BYOND Key: arrow768 Game ID: b3b-dj9w Player Byond Key/Character name: xanderdox / Klaus Eliade Staff involved: None Reason for complaint: Repeatetly Frontlining as Captain Did you attempt to adminhelp the issue at the time? If so, what was the known action taken by administration/moderation? Ahelped but ticket was not taken. Approximate Date/Time: 2019-09-12 00:00 GMT+1 Xander has been repeatetly playing his captain/HoS in a way that is frontlining and putting themselves in needless danger. In this round they went up against 3 heisters in security with a single security officer in tow (during the height of the engagement). They got shot with ballistic weapons, moved in close with the telebatton in an attempt to take them out ,did not retreat even when they head the chance and the other officer was severely wounded. They had multiple chances to retreat during the whole encounter yet they took none of them. Instead they took on multiple heisters armed only with their telebatton and disarm spam. They even managed to get into maintenance (while bleeding), yet they circled around to engage them again (after briefly patching themselves up with a medkit). This ultimately resulted in their death. This behavior should not fly as a captain and xander has been ahelped and banned a number of times for behavior like that, yet he still manages to pull it off.

What a downgrade. From moderator to CCIA. On a more serious note: I think he´s going to make a pretty good CCIA Agent. One thing I noticed in the interview is that command is generally expected to handle most things on their own and you seem to be a relatively inclined to do hand holding. (Keep in mind that ignoring a fax or replying that command "is expected to handle issues on their own or specify why that is not possible" is an option) But other than that, no complaints.

Indeed, that´s exactly the reason why the default frequency is not the common frequency. Therefore voting for dismissal as having the minor inconvenience of having to change the frequency is worth the failsafe that the station wont instantly know that there is a outside force "somewhere in coms range" if someone accidentally uses common.

After discussion the following change will be implemented: Heads of staff will no longer be able to issue work orders to employees from other departments. This solves the issue that the HoS is able to give the QM a valid order which has to be executed by them. Any employee is able to ignore work orders given to them by other heads of staff in standard operation, unless they act with captain authority once the changes are implemented. The directives and chain of command will be updated to reflect this and a announcement will be made once the changes have been fully implemented.