Arrow768

Application is denied due to inactivity. You are encouraged to reapply once you are more active.

Definitly interesting. I might work on that soon ™️

I want to correct only one thing: The purpose of player complaints is not to request the ban of a person. That is what ban requests are for.

Well, the thing you linked is for tgui. We dont have tgui. -> We are Using vueui, which is a completely different system. But still, something like that should be possible with our GUI System aswell.

Voting for dismissal for the reasons stated by @Karolis2011 and @Shadow

Autoantag currently checks for a simple condition: If there are not sufficient active antags for the current population (there is a ratio somewhere), then new antags are added. So new antags are only added during autotraitor if one (or more) of these conditions applies The population increases Antags die (or go to cryo) The cynic in me would say: "If security wouldnt kill all the antags they find there wouldnt be a constant onslaught of antags". That said, I definitely agree that no more antags should be added if shuttle is incoming, as this will just lead to rushed action by the antags.

Well, then those holes should probs be filled instead.

Well, the PR didnt actually change the amount of rigs (in the latest revision) but still had the old changelog. So I´ll bin that.

Well yes, but the pr is not significantly different. The paramedic changes have been suggested by the op. The janitor changes have been suggested by someone in reply to the op.

When implementing a pr not only the op is relevant but also the feedback provided in the topic. As I agree with the people that mentioned (in response to the op) that access creep is not a good idea I implemented the PR the way it is. The PR does not attempt to hide anything that it does and shows clearly what it will do and anyone clicking on the PR (or just looking at the rich link embed that should show the pr title) will see what it is doing. As shown by the discussion regarding the janitor access removal in the topic, quite a few people managed to click on that link. To reiterate: - I created a PR taking feedback from the suggestion and my personal opinion into account. - I linked the PR in the feedback topic so anyone who is interested in the paramedic changes can easily see it without checking github. - I linked the feedback topic on github, so feedback can easily be provided (which people are doing. So what exactly is staff complaint worthy about that?

PR is here: https://github.com/Aurorastation/Aurora.3/pull/6768

Yup, winding would have been fair game aswell. But as I mentioned in my first post: from my point of view they played a rat not with the idea of roleplaying the gathering of nesting materials, ... but with the explicit purpose of being a annoying little beast. This is further cemented by the fact that they didn't bring up their "proper" roleplay of gathering nesting materials when I informed them that nibbling "just for fun" is not something that we like to see. With that in mind I just went for the kill option. Regarding the "you are dead now because you broke a rule that is not known or written down". Let me rephrase that: "you are dead now because you broke the dont be a dick rule by playing a rat with the explicit purpose of being a annoying beast"

Exactly. That is not something that is wanted. While you have edit access to the wiki as wiki maintainer, that access may not be used to write your own lore. You may use that to correct grammatical, design or other errors that don't change the lore itself.

My main concern is that you will use the powers given as wikidev to pull something similar as you did with your resignation letter. Another concern that has been voiced to me is that you will act as a backseat-lore-writer. What is it that you can do as a wiki developer that you can't do via the contributor system we have in place for the wiki?

Garn and Flamingo already voiced their disapproval. I have to concur and vote for dismissal aswell.

While yes, it would be easy enough to revert, it definitely wouldn't be easy to implement in a persistent manner.

For reference the text that shows up in the chat when you become a rat: In a recent PR this specific wording was proposed: We intentionally choose to go with the first wording as in the past we have had issues with players being stupid with mice (that are now rats) and do not want to enable that via the description. You were being stupid as a rat eating boxes that dont contain food in medbay (i.e. nitrile gloves, syringes, ...) to the point where the medbay players ahelped that. As you were in the process of eating boxes at the time and I wanted to check a few more things before I talked to you, I just "dusted" you. I probs could have winded you or told you to stop, but then again you are a rat nibbling boxes to annoy the people in medbay. Taking into consideration the short respawn delay for simple mobs and that they are not a "character" involved in the round I believe that the response was fitting.

Well, you were warned for consistent bad attitude, then continued that attitude in private messages with the person that talked to you, which led to your dismissal. So, what has changed since then?

I have to give this a big no, since your attitude hasn't changed after you dismissal as skrell lorewriter only a few weeks ago (for bad attitude).

Sorry for the delay. The ban is now lifted.

I havnt looked into those yet. It might be interesting to replace them aswell, so there´s one system that lists all the roles available

ERT / TCFL will be moved to that system aswell, but I am not sure how "verbose" the menu will be when telling you what it is you are signing up for. (i.e. if its just Response Team or the actual name of the team)

Humans definitely. Silicons should be possible aswell. Quite Possible

I am currently working on adding ghost roles and ghost spawners. The ghost spawner menu will replace the "Spawn Rat" and "Join as Drone" ghost command, as well as various staff spawners. The goal is to provide a single, relatively easy to expand system which can be used to add ghost roles. If you have any ideas for or questions about those roles, reply below. https://github.com/Aurorastation/Aurora.3/pull/6706

Well, then let me address the bar-sign yet again (as I have done countless times before) For those who are unaware of how the barsigns look: As you can see, it does not clip into the backroom (as it should). Your Pull Request introduced a sprite that is larger than 64x32, therefore it clipped into the backroom. To be very clear: The barsign being visible from the backroom is not an issue. The barsign clipping into the backroom and covering parts of it is a issue. And this issue was introduced by the 64x64 barsign that you added. Yes, you did express interest in a Bugfix PR, but shoved that bugfix in with a PR that adds holoplants. You were told to change this accordingly by skull, but did not do so and instead closed the PR yourself. https://github.com/Aurorastation/Aurora.3/pull/5882 Here is my Atomic PR for reference: https://github.com/Aurorastation/Aurora.3/pull/5880 Again, we gave you the opportunity to provide a fix for it, yet you failed to do so. Also the requirement for atomic PRs should not come as a surprise to you, as it is listed in our contributing guidelines and repeatedly mentioned in code-dungeon and various PRs on GitHub.