Arrow768

Alright, thats the usual "Uhh Change - Reevert !" Topic that was to be expected after the update. As usual we will wait a month before making a decision if we should revert it or not.

Visitors may not be reassigned to station roles, unless its an emergency. A SM delamination that wiped out 50% of the engineering crew and a AI that announced its Glorsh is such an emergency. With previous announcements that AI systems all over the sector were merging and taking over control. The primary objective is to keep the station intact and the crew alive. At that point it doesnt matter what job title someone has/had. Its either live or die. If there is a person on the station that is able to lead their department and card or destroy the AI, then I will recruit them for the time of the emergency. After the AI has been disabled, the CE I recruited has been restored to the visitor position again. Regarding that this specific part of the directives is a OOC policy aswell: I was not aware of it, as it is not listed on the server rules. Regarding the notion that the Skrell could keep their genocide a secret: I have never seen a mention anywhere that only Skrell can know about Glorsh. Saying that they kept it a secret is like saying that the Armenian´s or the Jews kept the genocide of their ethnic groups a secret. You can not keep a event like that a secret. Its also listed as Noteable Synthetic

I also dont really see a need to change anything with engineering. They have the option to do almost anything. Just talk to your superiors and I am sure that most of them will be more than happy to assist you with your projects.

I do not like that idea, since it would prevent users from discussing the event. Ideally it would be two-split. A general overview of the event, that includes whats going to happen should be posted in a public area so anyone can discuss it. And details if needed could either be cleared up with the admins or posted in a separate admin-only thread.

Voting for dismissal. Incidents are usually caused by stupidity as outlined above.

Somewhat implemented with that: https://github.com/Aurorastation/Aurora.3/pull/4097

Moving to completed projects. Will be in the march update

Moving to completed projects, as it has been implemented

Moving to completed projects. Will be in the march update

Moving it to completed projects then

Then I dont see a reason to change it. The system is fine as is. Its monitored by staff for abuse. And abusers are handled by them. The participation in aooc is voluntary. You do not have to respond if you dont want to give away that you are an antag. If only the ckey is shown, then you generally dont have the association of ckey to charname (Yes, there are some exceptions, but for most cases this is true. Therefore voting for dismissal.

The WI Incident is what I referenced in my post. You started deleting contracts on the WI, while your judgement regarding another contract was called into question. Which led to you being fired / resigning before you could be fired from staff. Here is the staff complaint in question, in case you have forgotten. And here is where one of the headmins sais that you would have been fired had you not resigned. Before that, there are quite a few other incidents where you overstepped your boundaries or misused your power. Which ultimately led to you being banned from moderating the forums for a 3 month period. We have heard the same thing before. In your moderator application: https://forums.aurorastation.org/viewtopic.php?f=31&t=7765&p=74969#p74969 So, I ask you again. Why is this different than the last time ?

That can be said about every other mechanic aswell: Tampering with bombs, Phoron Fires, Sec Officers gunning down someone in accident. Yet, we dont discuss the removal of these mechanics. Yes, it might runin someones round. I had this happen to me. I ahelped it. The player was punished and they wont do that again. However I havnt been revived and they didnt get around to clone me for the rest of the round. Tl;dr. We have mods and mins to deal with rule violations including metagaming over aooc. A solution would be to show the ckey instead of the char name in aooc. (If the char name is shown atm) That limits the metagame-potential quite drastically.

The number of staff members I have absolutely no interest in dealing with is very limited. You were one of them. You were already 3 or 4 times parts of various staff teams, and everytime it ended with some drama. During your most recent moderator application you were asked the following by Garn: You responded to that with: And a few months later the same thing happened again, with you deleting contracts from the webinterface while your judgement regarding another contract was called into question on a staff complaint. Leading to you being fired from staff / resigning before that could happen. Whats different this time ?

Yup, I thought that has already been closed.

Voting for dismissal for the points presented: If you can make a lawgiver, you can make a bag of holding, which would allow you to carry more than enough ammo. I dont like the idea of that nerf-buff. The lawgiver is powerful enough as is and also has enough drawbacks as is.

Voting for dismissal for the reasons provided by Jackboot

It seems that you want to add a group of people, that have some kind of goal in mind that is meant to provide "action" to the station. In addition they can recruit others to join them. Well, that really sounds like revolution or traitor. Traitors can already communicate with each other and decide to work together icly via the codewords and oocly via aooc. They can also try to recruit people, by either forcing them to assist them, threatening them (almost noone is using exploitable information) or possibly even bribing them. Where is the difference to rev / traitor ?

A security whitelist, that you need to apply for on the forums is a definitive no. We have had this discussion many times before and it has always been dismissed. However, a playtime requirement (as cadet) would be something that is possible and could be pursued. [mention]LordBalkara[/mention] if you would like this being talked about, then I suggest you update the title / main post accordingly (to avoid confusion)

[mention]Butterrobber202[/mention], you are correct. There is no requirement that a developer "wants" to code something. Developers are expected to implement projects they are assigned. However, the requirement of a project being assigned to a developer is also listed in the post you linked: And that's where the points raised by LordFowl come into play: We already have a huge number of cyborg sprites, where most of them fit into a general visual theme. There are some exceptions which, imho, should eventually be reworked or removed. The sprite proposed does not fit into the visual theme. If you play a cyborg, you intentionally choose to play a role that is limiting, both in its mechanical functions and its visual appearance. They are tools, the available designs should reflect that.

Moved to the archive as a topic for this already exists

There probably should have been a feedback topic before the merge. However it has been merged before this happened. Since the update is not causing any mechanical or gameplay issues, I do not see a reason for a immediate revert before our standard waiting period has passed. It should also be noted that most people on github were supportive of the change, which might have been a factor why the missing feedback topic has been overseen.

Kaed, if you look on github, you will notice that I did not write a single line of code for the update. I was just one of the people who reviewed the technical aspects of it. It is not my project. I am arguing for janitorial being part of engineering, because i as a player, want it to be part of engineering and believe that it fits better into engineering than into janitorial. Its two days after the update. And all I can see so far is the usual post update-revert topic that someone created because he didnt like what he saw after playing a few rounds. Wait a month or two and then we´ll see if there are actual issues. So far noone was able to bring up actual issues caused by the change.

This argument is absolutely over the top. Using that same argument I can currently detain the chaplain and the HoP (as well as anyone else in service and cargo, because the HoP is also the head of cargo) for neglect of duty if the floors are dirty. Doesnt make sense either and it doesnt happen right now. I never argued that changing a lightbulb requires a "endless grasp of electronics". I was merely explaining to you the many different tasks that facility management covers, which include tasks that require almost no education such as mopping floors and changing lightblubs and other tasks that require some engineering understanding, but they are all part of the same department. Again, I have never said or dismissed your argument, because "it hurt my feelings". I dismissed it, because you failed to provide reasons that explain why the janitor can not be part of engineering. You have made various claims: And did not proof them in any way / back them up with proper reasons that are not recursions on itself. You have even contradicted yourself: First you say they focus on the big picture, then you claim that the maint techs are low-intensity jobs and are made somewhat redundant by the janitor.

As explained many times before, the shuttle times, all prices, categories and the order of the items are config settings under the purview of the lore team. In addition the stuff that is planned for cargo is listed here: https://github.com/Aurorastation/Aurora.3/projects/5 Now onto some of the points raised: That is not true. CTRL+F searches the items in the currently selected category. I am not sure where you get these values from. The previous cargo system was not based on credits but on points that have nothing to do with the money in the cargo account so there cant be a percent comparison unless you pull values out of your ass. (If you divide two different units by each other you dont get percent as a result) Well, thats why cargo has these things called EFTPOS and the delivery apps on the tablets in their lockers. If you charge your customers for the items, then you wont run out of money. And if there is ever a reason why a head needs to order something that is not covered by their department, they can go to the HoP or captain and request extra funds. There´s 75.000 just sitting in the station account (in addition to the departmental funds). As mentioned at the top, there is a project on github that details whats still planned: https://github.com/Aurorastation/Aurora.3/projects/5 And finally, we have a cargo feedback thread, monitored by myself and a lore dev, which is used to update the github project and cargo config usually weekly (which slowed down due to IRL priorities in the last weeks). Therefore I am closing this here. -> Cargo Feedback thread for cargo feedback.