
Arrow768
Head Admins / Devs-
Posts
1,700 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Everything posted by Arrow768
-
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"
-
Coalf Wiki Developer Application: Mark II
Arrow768 replied to Coalf's topic in Developer Applications Archives
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. -
Coalf Wiki Developer Application: Mark II
Arrow768 replied to Coalf's topic in Developer Applications Archives
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.
-
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.
-
Checking the logs again, it seems as the warning didnt save properly, so I reapplied it and verified its saved. Regarding the unban request: I´m willing to grant that as, while you did something dumb it did not really effect anyone else and I´d just call it a moment of impaired judgement which can happen. For the ban request: If you are sure you want to be banned for the merc situation then that's possible. But I do not see the reason to do so because: You already received a severe warning about it and the next instance of similar behaviour will lead to a ban anyway. The ban request shows me that you understand what you did wrong and most likely wont do it again. Unless you have any questions or further comments, I´ll just lift the perma and you´ll have to acknowledge the warning.
-
@ParadoxSpaceIs there something else that you would like me to address that was not covered in my previous post?
-
I want to address you coming after me, or making snide comments about myself or the quality of my Pull Requests (especially when I am not even present), Well, you have a track record of pull requests that are broken and not sufficiently tested for example: (I am sure that there are others that I am forgetting here) Bar signs Zorane Soda Disables ERT on Revolution You were repeatedly told to test your pull requests properly and check for both functionality, error cases and unwanted side effects, yet you still produce pull requests with issues that would have been revealed during the simplest of tests (For the bar signs PR that would have been activating the bar signs; For the Rev PR that would have been starting a rev round). This is pretty much the most harmless comment that I could make on that matter. There are things which are soo much worse that I could have said regarding your inability to test PRs after being told to do so repeatedly and this was probaply the most harmless thing that I could have said about it. The post I made about "paradox being paradox" has been addressed here: It is not my fault that you choose to name yourself paradox. If you named yourself john I would have written "its just john being john". And again, this was probably the softest way that I could address geeves question about the test merge which you described as being "nothing". I could have explained to them, that you have a proven track record of being unable to read code and therefore do not understand what this PR does, and that it is indeed quite complicated and therefore needs to be testmerged. (And we actually found two issues during the test merge one of which is a major issue which prevented the system from being used.) I choose not to say that but instead "sugarcoat" it. Regarding the "usual paradox brainfart" and "as well as even playfully dismissing peoples' opinions on things you have added" According to the oxford dictionary of english a brain fart is "A temporary mental lapse or failure to reason correctly." https://www.lexico.com/en/definition/brain_fart I believe that expressions such as these (which are stitched together from various statements during the conversation) can be described as a failure to reason correctly: This is also what I considered "valuable" opinions as most of these things do not argue about the topic objectively. Therefore I do not consider them "valuable". The "usual" before the brain fart is because you often refer to such arguments in various discussions. Is there something else that you would like me to address?
-
@ParadoxSpace What exactly is it that you would like me to address?
-
Thank you for showing how stupid this whole complaint about $people, ""people"" and $opinions is. It just comes down to what the person on the other end wants to interpret into it.
-
I did not insult them with that. I just made a comment that it is usual for them to do this. (Complain about things that they do not fully understand) A insult would look quite different.
-
Well, that was because as usual you did not read the PR or did not know what a mechanic does before commenting about it. "Basically nothing" in this case means a entire new subsystem that loads lore relevant notes from the database or a json file depending on the configuration and then places those notes in predetermined locations or computers based on tags associated with those notes. So very far from "basically nothing"
-
-
Thank you for posting this thing completely out of context. Did you contact any of the other admins or headmins/devs present at the time about this conduct and why not? I only have a limited patience, as everyone, and and if certain people come up with the same ridiculous ideas over and over again after they (again) screwed up a PR by not properly testing it as they were told to do last time (and the times before), this patience will run out eventually. Which is what happened here.
-
Staff Complaint - Drago / Alberyk
Arrow768 replied to TheSleepyCatmom's topic in Staff Complaints Archive
Well, since I have been mentioned here I´ll just post the relevant parts of the conversation here. @Alberyk / @Garnascus please correct me if I am wrong here.