Jump to content

Faris

Members
  • Posts

    1,480
  • Joined

  • Last visited

Everything posted by Faris

  1. The reason it's a permanent ban is to force communication. The reason illustrates that you logged off upon contact, so we can't assign intent or reasoning behind your actions if we don't speak to you. [mention]Alberyk[/mention] will handle your appeal.
  2. Locking this on behalf of Skull. No issues visible.
  3. Hello, this is for feedback regarding an event I made. I hope you enjoyed it and I do apologize for those that didn't. The round similar to my other events was essentially free-form. I tried to provide hints and clues as to how to act, without artificially forcing anything to happen. I'll be obscure on some of the details since I intend to run it again, albeit differently It started with announcements regarding carps, that was supposed to be a opener to the sequence. I had placed the location of a "boss" somewhat north of the armory. A person going EVA or going through maintenance might've seen the presence of carp in the area. As you'd approach the location you'd be able to see that the carp would be thinned down, gore and dead carp more prevalent until you hit its location. For the station itself, the carp and even some sharks would've been "crazier", I even had one bit through the mental ward and land directly into medical reception. A few more incidents of them burrowing around, biting through areas to get deeper inside. I tried to emphasize them going more aggressive and disoriented, since this type of behavior is super uncommon. I also wanted to show that they may potentially be looking for things, such as the tainted zones. As for the tainted zones, I had 4 preset locations of them. They'd progress in size and defenses which ranged from pylons to creatures. To defeat a tainted zone from expanding, you'd need to destroy the docile pylon. It wouldn't remove the taint, but it would stop anything hostile from spawning. The crew were required to only destroy 3/4 docile pylons, that's three tainted zones cleansed before the location would have been revealed courtesy of Central. I felt I put enough emphasis directly by narration, the spread of taint and CC announcements to showcase this. I did a lot of spooks too, the crew saw a lot of creatures. Bodies suddenly falling from the sky, blood and gore, skeletons rapidly appearing and disappearing and all manner of stuff. I tried my best to avoid directly killing anyone, most of my efforts was to wound and scare. The only time I was fine with lethal intent was the evacuation attempt before the "boss" was taken out, where I sent two juggy's to destroy departures, but I noticed a lot of people sticking around, even though they were breaching in, which I felt wasn't even the most optimal route, that's where the only real casualties happened. Though I decided to let the pod people be. I felt I put enough emphasis that departures and the shuttle itself was not safe, but a few people disagreed, so I'll try to make it more apparent in the future, since it turned into a massacre. Do give me advice, feedback and the sort. I do a lot of prep work for these events and on that basis don't do it often, so I get less experience hosting than my other staff, so every bit you post here counts. Do include bits you felt I did well and that you enjoyed, I can do more of that and put more effort into it as well.
  4. Ban lifted. Locking and archiving.
  5. Just tell us if it ever happens. Grab a mod/admin you know is online and we'll cryo you in a minute. I'll accept this appeal, should be remove in an hour to two. I'll update it when I've done it.
  6. Hi, anyone that receives a warning can review it on the greetings tab. So the warnings were visible for you to check, you simply may not have been aware of this. I'm willing to write a note to provide context as I'm willing to take you for your word here. I admit I may have been a bit harsh in terms of the punishment here as well, a bit too much. So I do personally apologize for that. A question though. Do you have phone service? If you had some form of access to discord, you could privately message an admin that you're unable to come back. Furthermore, while we do understand your circumstances here, this would be an issue if this was an extremely common occurrence. Especially with how vital and active security is needed to be.
  7. Reporting Personnel: Khaled Al-Bastaki Rank of Reporting Personnel: Head of Security Game ID: bUE-b4BP Personnel Involved: (Name, Rank: Offender/Witness/Other (Ckey)) - Ashai Dazai, Bartender: Offender Note: Shellframe - Tim Johanson, Roboticist: Possible Offender Note: Lack of evidence to determine for certain The following names would most likely be secondary witnesses. They may or may not have any sound insight over all this. - Maline Trell, Roboticist: Possible Offender Note: Lack of evidence to determine for certain - Kharzvar Fuz'kal, Security Officer: Witness Note: First Officer to arrive on scene of suicide attempt. - Yisheng-6, Medical Doctor: Witness Note: Medical IPC cited in report. They arrived on the scene and gave some insight. Time of Incident: Real time: 1500GMT+4 01/06/18 Location of Incident: Bar, Brig, Escape Shuttle Nature of Incident: [X]Workplace Hazard []Accident/Injury []Destruction of Property [X]Neglect of Duty []Harassment []Assault []Misconduct [X]Other Untagged Shell impersonating a Human Overview of the Incident: The short overview would be that Ashai Dazai was detected as a Shell Frame without a tag by a few different cues considered as evidence. They were taken into custody, they were tagged. It was verbally belligerent but not physically, most likely due to the security presence along with restraints. Investigation into the tag removal was not conducted due to the fact a transfer shuttle arrived, but I did manage to acquire some testimonies, but sadly not on tape due to time constraints. Long version: Kharzvar Fuz'ka, a Security Officer notified me over department radio that an attempted suicide was being made in the bar. I notified that I'm headed that way as I wanted to oversee the situation itself in its handling. Upon my arrival, Ashai Dazai who I will refer to as it for simplicity sake was restrained on the table. There was a medical IPC on sight who was watching, which was odd since I'd assume they'd treat them. I'd asked about that and the officer replied that they were mostly unconscious, at which point Tim visibly paled, at which point he went on to state that they are fine and cannot suffocate, which was later confirmed by the medical IPC as they had no pulse. This is when I took it upon myself to use the health analyzer and found their readings to be similar to other untagged shell frames I've been able to find and tag. At this point we had it moved to security. It's important to note that Tim actually had a tag implanter, showing he was aware of this condition, further supported by the previous statements and actions, and also supported by what I'm going to also get into. Tim personally approached me and told me that it had supposedly gotten him drunk and had him remove its tag. They claim they had no memory of this when I pressed on this matter. Due to them being a suspect, I asked for the implanter to do the deed personally, which they obliged. It made certain statements to also support what Tim has said, implying that a member of the robotics team was responsible for the tag removal. When I made a comment about knowing who it was, they appear to have back peddled and commented that they never stated they were on board this station at this time. To note, there was another member by the name of Maline Trell also onboard, but they entered cryogenics before we detained it, so they are also a possible suspect or accomplice. After a bit transfer was called, they were moved to the shuttle under guard whereupon I implanted the proper tag into the correct area. The suicide note that occured originally seemed to be some form of protest, speaking about the difference in treatment between organics and shell frames. The note they had written supported this, but I did not have the time to make a copy of it to attach to this report, but I assure you that what was written has little importance to this report as a whole. Did you report it to a Head of Department or IAA? If so, who?: No. The only superior, a Captain, was not present. Actions taken: Detaining the untagged shell. Escorting untagged shell to shuttle. Implanting untagged shell. Additional Notes: I'd note that a proper and full investigation would have been conducted into the nature of this security breach had we been allotted sufficient time. The introduction of the transfer shuttle halted most of my efforts so I was never able to determine for certainty who and how this breach occurred. My professional recommendation would be the removal of this security breach in some form. While I won't advocate its immediate dismantling, I'd recommend they be reprogrammed, re-purposed and stationed else where until they can be deemed safe enough to operate on the station.
  8. Sure. If things happen again then I will point to this. Yeah, feel free to contact me personally to hash out the details on how to proceed if an issue pops up again. Going to lock and archive.
  9. Two dismissals, locking and archiving.
  10. Do you want to drop this now that mutual understanding is made?
  11. [mention]BurgerBB[/mention] anything further to add with the new post?
  12. I'll remove your ban and take you for your word, but you'll need to figure out a way to inform us, since while I do understand your circumstances, it still locks a job away from a person that could be playing, sometimes for an entire round until someone notices. Try your hand at a macro or some other solution. Edit: Ban is now lifted, I'm going to lock and archive this. Contact me on discord if there's still an issue. [mention]Itanimulli[/mention]
  13. Making an ahelp that you need to go takes 10 seconds at the very most. There's a hotkey for it and the tab for adminhelping doesn't have many verbs. You'd do either, input "I need to go" and that's all you really need. Is your family too impatient for that time frame? I'm most likely going to accept this appeal regardless of your answer. It's just that I need you to make the effort to communicate. I don't think taking up to ten seconds to adminhelp is too much to ask for. Alternatively you can tell someone on discord using your phone, if you have the application.
  14. You're not giving us a lot to work with here. Can you expand your original post?
  15. You've only got a single note and that's about going AFK for a while, which is really nothing. So you're good on that front and show to me you've got a proper understanding of the rules. You're application is also good, you touch on a lot of relevant things, especially citing life experience. I'm also fond of your interview. You mentioned starting in February but your first log in was around mid 2016. Were you an irregular user of the server or did you only log on once before in 2016? Aside from the question about which is just a matter of clarification, I can support this application.
  16. [b]Discord username + tag:[/b] (Specify your discord username and tag [Example#0001]. Contact details can be requested/provided over a more secure channel, such as PMs. Delete this comment when making the application, and replace with the answer only.) [b]Age:[/b] [b]Timezone:[/b] You forgot the age field.
  17. Your application is okay, it's nothing really special, but I'll just say it's enough. The issue with your application is that even if we remove the ban which you were successful in repealing, you have a history of repetitive behavior. Which is mostly about your play of station bound/maintenance drone, with your most recent entry on that play being a month ago. You've also got more than one entry about IC-in-OOC and OOC-in-IC, with the IC-in-OOC being done to a player after you died, making it a very deliberate thing as you did it after death. Onto a character of yours. This is your employment records on Ben Smith, a character you cited above. This whole "SpaceMart" thing strikes me as a joke. At this time, I'm not super confident of your application. I don't think it's been long enough to acknowledge that certain trends have stopped. Considering this history, just because you haven't received any severe reprimand, it doesn't mean you've fully stopped. I think you need a bit longer before I feel comfortable endorsing your trial.
  18. So I went over your application and I think it's pretty decent. You've got cited experience and people vouching for you, while I'm not really familiar with GM at all, I'll take your word for it. The interview was pretty good, a few issues on the process but those mistakes are expected for a person with no experience with SS13 moderation and can be taught. There is however an issue and that you do have recent staff entries. So while the application itself is good, your history does raise concerns, since you'd be expected to enforce said rules on other players. So the concern is how would you enforce rules that you potentially do not understand? Would you still consider applying in the future? Assuming this application is denied at this time.
  19. Alright, I'm convinced. I'm removing your ban. Note that I highly suggest you give a proper read of the rules as any punishments for repeat behavior will be severe.
  20. You've been through two permanent bans. All 11 staff entries on you are on rules violations. You even waited longer for your first accepted appeal. What's different this time? Why is it you were so unable to follow the naming rules? You've been spoken to about it five times, where you received warnings and bans.
  21. It's been ten days. [mention]kyres1[/mention]
  22. I'm a little disappointed with certain comments here. I've issued warnings and deleted comments for some. This does not mean anyone that wasn't warned is off the hook. Any post after this one which is just a person being a dick to others or attacking others may get a forum ban, not just a warning.
  23. Since I'm positively sure everyone involved has seen my reply and no further information is being brought. Locking and archiving.
×
×
  • Create New...