Jump to content

Landerlow

Members
  • Posts

    1,101
  • Joined

  • Last visited

  • Days Won

    36

Posts posted by Landerlow

  1. Hi. I will be handling this with authorisation from Necaladun.

    My apologies for the incredibly late response. Life got in the way and this slipped the admin team's minds.

    We always appreciate feedback. It's good to get people's feelings, opinions and thoughts on our decisions. We will take this feedback with us for the future.

     

    I will now be filing this thread. 

  2. I will be replying to this, with authorisation from Necaladun. I will keep it brief.

    First of all: my apologies for the way too late reply. This complaint simply slipped our minds.

    Secondly, both parties have spoken. Continuation/further discussion about this situation is best done in a ban appeal, as this is now more about your ban than Ionward's actions. They were correct, as stated earlier. 

    I will file this complaint. 

  3. Hello. I will be handling this complaint, with authorisation from @necaladun.

    After having read your complaint as well as the logs (shown below), I can say that there is absolutely no wrongdoing on Dsdiy's part. You did not get a warning for being 'new'. You got a warning because you broke the rules You then got a bit salty about it.

    Spoiler

    ADMIN: PM: Dsdiy/()->Olivia0407/(Alice Sahli): Hi there, got a minute?
    ADMIN: PM: Olivia0407/(Alice Sahli)->Dsdiy/(): ummm
    ADMIN: PM: Olivia0407/(Alice Sahli)->Dsdiy/(): what's up?
    ADMIN: PM: Olivia0407/(Alice Sahli)->Dsdiy/(): what's up?
    ADMIN: PM: Dsdiy/()->Olivia0407/(Alice Sahli): We had an adminhelp, saying you were validhunting a cultist. And according to the attack logs, you were attacking a cultist in science maintenance, far away from your workplace.

    ADMIN: PM: Olivia0407/(Alice Sahli)->Dsdiy/(): yeah the cultist attacked someone i was talking to in front of kitchen so i followed them to save the person ADMIN: PM: Dsdiy/()->Olivia0407/(Alice Sahli): I'm afraid that, given you killed the cultist, it's against the rules. Self Antagging, and validhunting.
    ADMIN: PM: Olivia0407/(Alice Sahli)->Dsdiy/(): oh okay I didn't konw he was killed. well what can i do then
    ADMIN: PM: Dsdiy/()->Olivia0407/(Alice Sahli): Given this is your first offense, I'll let you off with a warning. Remember though, killing antags as a non-security is considered self antagging, and validhunting.

    ADMIN: PM: Olivia0407/(Alice Sahli)->Dsdiy/(): what is a warning?
    ADMIN: PM: Dsdiy/()->Olivia0407/(Alice Sahli): Exactly as it implies. We warn you not to continue similar behaviour.
    ADMIN: PM: Olivia0407/(Alice Sahli)->Dsdiy/(): i'm confused, what am i supposed to do when i'm getting attacked? like right now
    ADMIN: PM: Dsdiy/()->Olivia0407/(Alice Sahli): You can defend yourself, yes. If there's no way out, or they're using lethal force on you, you are allowed to attack them into critical condition
    ADMIN: PM: Dsdiy/()->Olivia0407/(Alice Sahli): But then you need to get away from the situation
    ADMIN: PM: Olivia0407/(Alice Sahli)->Dsdiy/(): what happens if i get warning next time

    ADMIN: PM: Olivia0407/(Alice Sahli)->Dsdiy/(): like one more warning ? how does it work?
    ADMIN: PM: Dsdiy/()->Olivia0407/(Alice Sahli): Depending on the severity of it, it'll either be another note added to your account, or a permanent ban that you will need to appeal
    ADMIN: PM: Olivia0407/(Alice Sahli)->Dsdiy/(): okay so the warning gave my account a record
    ADMIN: PM: Dsdiy/()->Olivia0407/(Alice Sahli): Indeed.
    ADMIN: PM: Olivia0407/(Alice Sahli)->Dsdiy/(): yeah i'm new and seeing how many more warning i will get i can see where it's going
    ADMIN: PM: Olivia0407/(Alice Sahli)->Dsdiy/(): well bye

    No actual punishment was applied, such as a ban - this is very standard for the first time someone breaks the rules, and over 10,000 such warnings have been applied throughout our history, including to nearly all of the admin staff.

    After 200 hours, you should have at least read, and be able to follow, our rules. You are free to play again on the server. If you decide not to, that's your loss.

     

    Complaint is without merit and can be considered resolved.

    • Like 1
  4. I honestly don't see the point don't think it's necessary. You could just make a #thread if you wanted to discuss something. I don't see how it would cause elitism though. Everyone would be allowed to post in the channels, it's just a way to split up topics. If people are being dicks because they think they're more knowledgeable than others of certain departments well .. that's the problem of those people, not the channels. And we can just deal with that. 

    • Like 1
  5. First, let me clarify that I am posting on behalf of @necaladun, with his permission.

     

    With that out of the way, to business.

    There's several things I will address, starting with Abydos' behaviour. The truth is that he did not do anything wrong, nor did he abuse his power. He's also not targeting you. All he was doing, was his job. Which is administrating the server and, if necessary, hand out warnings or take other administrative action appropriate for the situation.

    As for the situation itself, it's quite simple. You broke a rule and got warned for it. The fact that Abydos thought you were the chef instead of the geneticist, has to do with the fact that Abydos was going off the information available to them at the time. Whether you were the chef (or in this case) the geneticist, is, however, ultimately irrelevant in this case. What is relevant is that you went after antagonists, with hulk powers, when it was not your job to do so. That's considered validhunting.

    00:47:15 Say TheGreaserGuy/(Paul Corin)(?) (FLW) 'ME HELP' (181,129,2) (JMP) -- This was outside science.

    00:48:50 Say TheGreaserGuy/(Paul Corin)(?) (FLW) 'I WILL GO' (140,113,2) (JMP) - This is where you rush to medical.

    You chose to go after the antag(s), because you could, while not being a member of security. Not because you helped while witnessing something happening. Hence, that's considered validhunting.

    The whole situation was ultimately a minor issue where you are blowing this way out of proportion. We're all human, and it's fine if there's confusion that has to be cleared up but saying an administrator is 'targeting you' merely because you do not agree with their assessment of the situation or the administrative action taken, is not something you should be doing. It comes off as childish and won't do you any favours.

    This complaint is without merit and considered resolved.

  6. First of all: Let me clarify that I am posting on behalf of @necaladun, with his permission.

    Now, to business.

    As a magistrate, you do have the authority to make the decision to parole someone, as defined in the Legal Standard Operating Procedures. I will quote it here, for reference:

    Spoiler

    Eligibility for parole:

    If someone is an EOC, OR has committed a capital crime, then parole is only allowed if authorized by the Magistrate or Captain. They should not authorize this unless it is a serious emergency and the parolee is expected to help deal with the emergency. For example, a non-violent syndicate engineer may be paroled to help fight a blob.

    For all other prisoners, Magi/Captain/HoS/Warden may authorize parole at their discretion. They are advised to consider how severe the prisoner's crimes are, how co-operative they have been with security, and whether or not they are expected to commit any further crimes.

    Process for paroling a prisoner:

    Parolee must be given a tracking implant, set to "parole" status in sec records, and informed that they are on parole (along with the charge), before they are released on parole.

    Parolees who are EOC or who committed a capital crime, must additionally be stripped of all belongings prior to release. They may be issued a new basic jumpsuit, shoes, radio, and civilian-access ID.

    After release, parolee is to be kept under supervision, and watched for any sign of further criminal acts. This can be done by co-workers, and/or security.

    If the parolee commits a crime while on parole:

    If the new crime is a capital crime, or they are an EOC, they are to be immediately executed on capture.

    Otherwise, for any lesser crime, they're to be re-sentenced for BOTH the original crime they were paroled for, AND the new crime, with times stacking. They're also disqualified from any further parole for the rest of the shift.


    The thing is: When authorizing a parole, whether it be in your role as Captain or Magistrate, you have to consider if the circumstances justify it. As you can read above here, you are only allowed to parole someone in case of a station emergency. And the parolee is expected to help the station fight the emergency (for example, a blob).

    In this case, there was no imminent threat to the station that justified the parole. And while you are right in saying that you do not have to fax to authorize a parole, it is expected of players who play a role such as Captain or Magistrate, to know the SOP('s) affecting their role/department. And if you then would like to make a decision that is not in line with said SOP, (especially something like paroling someone who should rightfully be perma'd) it is expected that you send a fax to CC for permission to 'break/make a decision not in line with' SOP. If CC, after the fax, gives you the green light, go for it.

    Now, as for the confusion on the decision: While we do have certain expectations from players as explained above, it would have made things clearer if the fax from CC had contained a line explaining what exactly was done wrong to warrant a demotion. This because it isn't just because you did not fax (as you rightfully said, there is no requirement for it), it is because you paroled someone in a non-emergency situation (and thereby breaking SOP) without asking CC for permission first (which is expected with situations like these, as explained above).

    When it comes to the punishment itself: The mistake was not nearly severe enough to warrant a bwoink, so Meow19 decided to demote you IC'ly and leave it at that, which is their decision.

    It basically boils down to this:
    - There was a busy shift.
    - You decided you wanted to parole someone, not completely in line with SOP when it comes to justifiable circumstances to grant the parole. You also did not send a fax to CC, which is something to be expected to be done if you want to make decisions like these not in line with SOP.
    - A fax was sent by CC, ordering your demotion. The fax could have been clearer.

    All in all, I would say that:

    - The IC punishment is warranted
    - The confusion on your part is understandable

    I have spoken with Meow19 about this for future situations.

    The complaint is not entirely without merit, though it is based on confusion regarding an IC decision. The decision itself is not incorrect, and justified.

    I consider this complaint resolved. I will leave it open for a short time to allow for a reply if you have any additional questions or things you would like to add.

  7. First of all: Let me clarify that I am posting on behalf of @necaladun, with his permission. Apologies for the delay, life got in the way. 

     

    Now, to the point:
     

    As you are not against the decision made by Abydos but rather have a complaint about the way you have been treated while in conversation, I shall focus on that.


     

    Abydos contacted you with a question. Which you answered. Turns out, you did something wrong, hence, you got warned for it. From what I can see here, Abydos did not treat you with contempt. They were just straight to the point, nothing more.

    Abydos explained what you did wrong and that you got warned for it. From what I can see from the logs, you did not like the answer, so indeed, you asked to speak with someone else. While you may not have intended for it to come across as admin-hopping (a bit similar to a 'Dad said no, let's ask mum' scenario), I can see how it did from an admin's point of view.

    In-game and on discord, admins have the final say. You can disagree with an admin's decision or ruling and enter a discussion, but an administrator is not obliged to go into a lengthy discussion with you about it whenever you want. There's also the fact that during most rounds, there's no time for that. Many things are happening at once. And even if there are multiple admins online, things are hectic. So the fact that Abydos did not want to go into further discussion or clarification at the time, is understandable.

    To give you an example: If you work in customer service, you, as CSR, get a lot of interactions in a day, per hour, etc. A customer usually gets only *one* interaction: with the CSR they're speaking to. There's things to consider, however:
     

    1) As a customer, you are doing one thing at a time. You are in an interaction with the employee. The employee, however, may be doing multiple things at once. Having the conversation, checking information meanwhile, perhaps even doing another conversation at the same time, if the customer service is digital. As such, there isn't always time to go into great detail/discussion during your time with the employee. The employee may tell you to send an e-mail (equivalent to the complaint you made here), or will arrange a callback.

    2) The second point is: We are not a professional customer service. Yes, admins 'serve' the community. Though they do so, as volunteers. And we're not a professional business. We're a server in the SS13 game universe.

     

    Lastly, you asked what you should have done differently. It's actually quite simple. You should not have done anything, really. You should have stuck to your job and let security do theirs. 


    Complaint is without merit and can be considered resolved. 

  8. I personally am not in favour of this suggestion. Reasons have already been given by others. 

     

    Furthermore, there already is a possibility to cut out common comms, however it is not by default and it's not forced upon anyone.

     

    On normal headsets: Change the frequency to anything that isn't the default common frequency (default is 145.9).

    On command headsets for example, there is a tickbox for 'common' that you can untick, to not receive common chat.

    • Like 1
  9. RFID Scanners

    Goes off when player walks through it with a non-checked out book

    Makes a log in the librarians computer

    Special Punishments for Book Thiefs

    Lights people on fire when emagged if they steal a book

    When fully upgraded it stuns the crew member and launches the crew member back into the library

    Has an R&D circuit board



    This is the best thing EVER. 

  10. This hasn't been updated in some time. So here goes, in no particular order:

    From the last post, until now:

     

    - @dearmochi has been promoted to maintainer
    - @AffectedArc07 has unretired from their maintainer role
    - @Trololiver112 became a Game Admin and retired
    - @Jakkibecame a Game Admin and retired
    - @S34Nhas been promoted to Game Admin
    - @White In Skyhas been promoted to Game Admin
    - @Christasmurfhas been promoted to Game Admin
    - @FreeStylaLT has retired from adminship
    - @FoS has joined the staff team as Trial Admin
    - @IcyV
    has joined the staff team as a Trial Admin

    • Thanks 1
  11. Could perhaps have a mechanic similar to drasks eating soap. Just .. nibbling on clothes that you have in your hand. I personally see no harm in it. And it adds something unique to the species. Personally I'm all for diversity and things like this. You could make it like you won't actually eat the whole piece of clothing, just .. nibble on it. Like drasks do on soap. 
     

    As for light-related mechanics: I went to Engineering as a Nian to get a floodlight. But Engineering has no more floodlights these days. Sadface. 

    • Like 1
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Terms of Use