Invalid Report against Smash

Discussion in 'TTT Staff/Player Reports' started by Anger, Sep 8, 2015.

Thread Status:
Not open for further replies.
  1. Anger

    Anger New Member

    Name of Staff/Player:
    Smash
    Steam ID of Staff/Player:
    Im not sure on this, and im not going to bother.
    Your Steam ID:
    Which Server:
    West 1
    Which Map:
    Warehouse i think the name is?
    Which Round:
    Not sure 9-10?
    Time of Occurence:
    I dont know?
    Reason For Report:
    The mod nearly slayed me for accidently kosing a innocent player as a T which he did not even bother checking which i called him out on and he lazily apologized and said that "Humans make mistakes"

    And the second thing is that he refused to do his job and slay a player who FALSE kos'd/shot me the reason for the false slay being this https://gyazo.com/716b8dc06c48d1d72a1df3c9e84bb3ff He claimed i kos'd him WHICH i did but i corrected instantly, he would have HAD to have gone back in the logs to confirm this for kos (Which was false) or scroll up, (Which was still false) And then the mod in the middle of all this basicly said to get over it (Paraphrasing here) and that if i continued i would be muted (Which i was) and i would be punished even more if i continued further. (Which i was. I was kicked)

    I dont care if this gets solved or not but its worth looking into. i will not pursue this or chase it like a rabid dog, but contact me through steam if you have questions or just ignore it. I hate this mod so much, yeah its true. But i have more than one reason.

    Also called me a kid, what moderator does that? the hell?

    Also YES i did call him a cunt, Twice. He told me to stop calling him curse words and i did.​
    Evidence And/Or Witnesses:
     
  2. Anna

    Anna before we fade VIP

    Ill go ahead and tag @Smash who will provide his side of the story and his evidence. I will also tag his admin @BmTron who will give the final verdict. Please be patient.
     
  3. Smash

    Smash Baka VIP Silver

    Hello @Anger, I appreciate you taking the time to file a report.

    First I'd like to adress that the entire situation was started by the fact that at the start of a round I placed a slaynr on you, this was an error on my part as after skimming the report I found it invalid. However you had called a KOS on an innocent, to which I could not find a reason for, and I rather hastily placed a slay on you only to be met with a rather explicit response including you noting that you were a traitor. I killed myself, double checked the logs and removed the slay, no harm was done. You proceeded to call me a cunt, twice and I asked you to stop and apologized for the mistake. You continued to harass by calling Schoovey a "fag", to which I muted and warned you.

    [​IMG]
    [​IMG]

    Now, as seen in both your screenshots and mine I did indeed call you a kid. I apologize for that as it was uncalled for, however you were being unnecesarilly rude over something that was not an issue. I continued to try and explain why I was upset and why Schmoovery was not being slain however instead of listen to what I was saying you continued to try and prove yourself as right. I gave you my last say on the matter and left it at that, you continued to try and explain why I was wrong and you were right.

    [​IMG]

    The map changed and you sent me a screenshot along with another unnecesary remark about me not doing my job correctly, I then proceeded to kick you for Harassment as I had already given you a warning on the previous map.


    I apologize as I do not have a screenshot of the report as between attempting to explain myself, I was also trying to explain prop-surfing rules to multiple players and did not have time to screenshot the report. However, the situation was that you accidentally called a KOS on Ice, to which Schmoovey killed Ice and found him innocent. The reason this KOS was still valid was there is no way to prove that Schmoovey did or did not see you call it off, making this a word vs word situation. Thus, I didn't slay Schmoovey.

    I hope this clears things up, I'm going to tag my admin @BmTron to finish out this report. If you have anything else you'd like to say in the meantime please do so.
     
  4. pup

    pup Princess Pup

    To clear up some of your concerns:
    1.
    Because he did not actually put down a slay and you did not lose any game play, there's no real issue here. Should he have double checked your role as a T before placing the slay? Possibly, but did this make any trouble to your gameplay? No. I understand you feeling upset about him placing a slay on you when you had done nothing wrong *at this point* but believe it or not, while juggling to look over an entire server while multiple players are needing your attention, mistakes can happen. Now this is no excuse and it is rare, but in this case it was resolved rather quickly. Had the slay went through then this would have been a problem, though because he caught himself and removed it, there's no need to see this as a full on issue.

    Refer to the boxed areas.
    [​IMG]

    2.
    Now this, this here is where you have to see why Smash didn't set a slay on @SchmooveySchmoove and why Schmoove killed you.

    [​IMG]

    You as a T accidently call out Ice, an inno, at the start of the round. With you calling him out as a Traitor, players now have your word to kill Ice. You're allowed to make false callouts as a Traitor as it is a common tactic to killing the enemy team. But, with that ability, it is also traitorous as well and if someone catches you in the act, they are in the right to kill you (as said in the MOTD)

    [​IMG]
    Accidental or not, you are still held responsible for that call out and players are allowed to kill you. In this case, you say you called it off. You can't necessarily call off a kos, for it is still your responsibility and you did not make it blatantly obvious that it was to be disregarded, so Schmoove went with the kos to kill Ice to only find out he was an innocent. That gave him a valid reason to set a kos on you, and led to your death. So with that report you had on Schmoove, Smash was correct in not slaying him.

    3.

    On Smash's end, the way he responded or reacted to all this was a bit hostile/aggressive, I do see that. I can completely understand why you're frustrated with this and yes, with this I can talk to him about in a private matter. A moderator should remain calm even in tough situations like this. As well as I believe he should have explained why Schmoove wasn't slain. For this part, I will discuss over with him.

    Some of my concerns:

    • When Smash was trying to explain and apologize for this, all you had responded with was "lmfao". [​IMG]
    I'm not sure how you see this, but that to me is disrespectful and uncalled for.
    • Constantly telling him to "do his job"
    [​IMG]
    The proof was there and he noticed what went down, which was why Schmoove was not slain.

    The punishments:

    The reason you were muted/kicked was for harassment. Your initial reactions towards Smash and the actions you did is what caused that. For instance:[​IMG]
    Overall targeting Smash and calling him a "cunt" twice is a very harsh and unacceptable way to treat a player/staff member.
    [​IMG]
    The way you went about talking to Smash was basically harassment. He did make a little error, yes, but that doesn't make up for the words you said to him.

    He took the correct protocol in your punishment.
    First he muted: [​IMG]
    As stated before, it was the words you used and the rudeness that caused this mute.

    Then he kicked:[​IMG]
    What led up to the kick was how you continued to treat him after the mute, how you went on with the act of him not doing his job. After so much punches, it seems he did what any staff member would do and kick you.

    Smash followed the right protocol in this situation, and although he may have done things a bit better, he had still handled this correctly.

    I really hope this clears things up, if you would like to discuss more, I will leave this open for the next 24 hours, after that you'll have to catch me through a forum convo.

    Report: Invalid
     
    Last edited: Sep 8, 2015
Thread Status:
Not open for further replies.