Report against Candycaneore [TACO]/removal of Slay

Discussion in 'TTT Staff/Player Reports' started by JAckh45, Jun 28, 2014.

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

    JAckh45 Member

    Name of Staff/Player: Candycaneore [TACO]

    SteamID of Staff/Player: no idea

    Server: West

    Time of Occurrence: Around 4pm

    Reason For Report: Would like a slay removed from my profile.

    Evidence And/Or Witnesses: The map was POOL and it was the first round of the map. Start of round I rushed inside grabbed a weapon and then exited the building. A tactic I always use for this map is sitting at spawn pretending to be AFK while T's return to slay AFKers... or the Teleport off to the side and run back in, as I can see the only exit from the building...

    Anyway, I was sitting at the very back of spawn, with a D MrLooting (as he knows my tactics for this map). The player AspiringSun then proceeded to return to spawn and started looking over the AFKers... I believe (and this is where the word v word argument comes into trial) he shot and missed one of the AFKers, thus me and MrLooting continued to kill him before he could make the kill. He was indeed a T.

    I was reported (and replied thinking it was towards another player I killed on that map called Atticus, as the respond will indicate, sorry for that) however after talking with Candy, they corrected me and I responded that AspiringSun did try and kill someone but was stopped before it could happen... I asked them to ask MrLooting as he was with me at the time... I never heard back and was slayn.

    I believe this is a word v word dispute... (unless you can see in logs when/if someone discharged thier weapon)... So I would like the slayn removed from my profile if that is possible.

    I don't record, and the only screen shots I could supply are simply chat, which is seen in logs anyway...
    Thanks for reading.
     
  2. Enigmatica

    Enigmatica The Song Lives On Banned

    Hello, thanks for the report! @Candycaneore will reply when she can.

    I was in a Skype call with her during this and heard her discussing this situation. I was not in-game with her at the time. She claims that it was not, in fact, AspiringSun that did any shooting. Rather, it was another player who attempted to kill the detective. You and MrLooting killed the wrong guy in that situation.
     
  3. Candycaneore

    Candycaneore Neko Candy VIP Silver

    AspiringSun was the player that shot the D, as I told you. I also told you that you both shot Atticus! who did nothing. Atticus! was a T but, had done nothing and the D had shot him. You ended up killing Atticus!, which was rdm toward him. I slayed you for rdming Atticus! who had done nothing traitorous to be killed. Lastly i will not and can't remove a slay off your record as its not possible.
     
  4. Enigmatica

    Enigmatica The Song Lives On Banned

    Oh, right. I had the names switched in my story. But the reason is the same; you shot the wrong guy.
     
  5. JAckh45

    JAckh45 Member

    Maybe I am mistaken then, I shot at only 2 people that round... I cannot recall which is which (as proven in replying to the report...) and I do not know which was which, the logs should show, sorry.

    The first player I shot at as stated above, he tried to shoot a AFKer and I shot him.
    The second was in a cluster, when he and another player came to spawn and were shooting all over, (I believe this was Atticus, but could be wrong and the names could be reversed...) Who was being (as stated above) shot by the D (MrLooting) so naturally if a D is shooting someone I also will shot down that person, as the D is law amirite?...
    Also the D called out a KOS on that person before I killed him... (Which as you will see, i responded to you via PM (logs will confirm).
    Both slays are not RDM in my case and still are seen as word v word to me also?


    And I know you might not be able to remove a slay... but on my record an Admin could I believe (not sure how your administrative records work but have seen this stated on other reports.)
     
  6. DocFox

    DocFox The Best Is Yet To Come VIP Silver Emerald

    Staff do not remove slays on player records as they occur so often, even accidental, and do not impact you whatsoever.

    If a slay is found to be false, the staff member that issued the slay will slay themselves.
     
  7. Enigmatica

    Enigmatica The Song Lives On Banned

    @Candycaneore and I will review the logs at the time of your alleged RDM to get a more clear picture of what may have happened.

    We used to add notes to user records every time a slay was voided but it made records sloppy and messy so we decided to stop doing that. With that said, the total number of slays on your record is not usually a determining factor in further punishments.
     
  8. JAckh45

    JAckh45 Member

    If I wish to apply for Mod isnt the Slays placed on you used ?
     
  9. JAckh45

    JAckh45 Member

    Please keep me updated on this, as I would apologise if this was a false report.
     
  10. DocFox

    DocFox The Best Is Yet To Come VIP Silver Emerald

    Do you know how many slays I have on record? It's less than 100, but it's all about your attitude towards the slays. If you gracefully accept when you're wrong, you will be perceived as a better player. Staff look more at bans and time played than anything else in your adminstats.
     
  11. JAckh45

    JAckh45 Member

    Fair enough then, would still be good to know that I didnt RDM tho and to figure out who was in the wrong.
     
  12. ZeRo

    ZeRo :sneaky: Banned VIP Silver

    If slays really mattered and impacted the mod selection process, then I should have never been a mod considering I have around 158 slays on my record. Mango is correct when it comes to the point about the mod selection being made.
     
  13. JAckh45

    JAckh45 Member

    Sall good, understand my slay cannot be removed and doesnt impact me, main thing I would like to know is just if I'm in the wrong.
     
  14. Enigmatica

    Enigmatica The Song Lives On Banned

    Hey @JAckh45 ! I have taken the time to find the logs of the current situation. From what I can gather, AspiringSun shot the detective, MrLooting, after which MrLooting retaliated, but also started shooting Atticus! Your story-- where you mention simply following in the footsteps of a detective-- checks out. Based on the evidence below, it has been deemed that you did not RDM. If anything, it's the detective's fault and if it was deemed RDM on the part of the detective, he would be slain, not you.

    [​IMG]
    [​IMG]
     
  15. JAckh45

    JAckh45 Member

    Thanks for going to the effort Event. Glad to know I didnt just open this for nothing. Appreciate the work to clarify it.
     
  16. MrLooting

    MrLooting New Member

    Jack informed me of this post.

    The reason I had shot Atticus! was because he was standing next to AspiringSun as he was flaring bodies. Guilty by association. I did call a KOS on both players at the time. No RDM was done.

    I know you had said "If anything, it's the detective's fault and if it was deemed RDM on the part of the detective, he would be slain, not you."

    Not implying I did RDM but I'm just covering myself.
     
  17. Enigmatica

    Enigmatica The Song Lives On Banned

    You wouldn't have been punished simply based on lack of evidence against you. For the very possibility of the reason stated above :)

    Crossfire and GBA were my first guesses so I'm glad to know it was one of my guesses :D
     
  18. JAckh45

    JAckh45 Member

    Plus I already got punished so its cool ;)
     
  19. Enigmatica

    Enigmatica The Song Lives On Banned

    Yup, unfortunately. Mistakes happen from time to time, I'm glad you have been understanding and co-operative throughout this investigation. It really helped us resolve and come to a conclusion where everyone is happy. I apologize for any inconvenience the unjustified slay has caused, and I hope to see you in-game sometime :)

    I'm going to go ahead and lock this as it is resolved.
     
Thread Status:
Not open for further replies.