J3LLY83AN Griefing

Discussion in 'Grief Report' started by MuttleyJames, Nov 9, 2011.

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

    MuttleyJames New Member

    Well, I am Co-Owner of Quiet_Sands. User_1241 left the game and i was on my way back home. As i arrived there was this massive lava flow running in User_1241's office. So i asked who done this. J3LLY83AN blamed Nrayf and i asked him but he said he did not. So i used Hawkeye tool and finally found who did this. It was J3LLY83AN. I kicked him out of the town and then he went on some griefing rage around town. Here are some pictures to prove it :
  2. User_1241

    User_1241 New Member VIP

    I'm shocked to log in and find this. All the redstone circuits are broken which took a long time to make! This needs to be fixed, however I may have a talk with the griefer. Seeing as MuttleyJames didn't put it in the format I will:

    What is your IGN?

    Coordinates of the location (use /getpos to display the coordinates X Y and Z)
    X: -1740
    Y: 77
    Z: 3127

    Is this on PvP or Peaceful side of the map?

    What exactly got griefed? Please be specific.
    Windows, wool floor, redstone circuits, glass

    About how many blocks were broken/replaced?

    Who did the griefing?

    Did you talk to the player who did the griefing?
    I spoke to him before. Seemed like a nice guy. However not after the incident

    What did they say?

    Do you think they should be banned for this?
    Uncertain, I would like to speak to him first

    Do you need an admin to come and rollback the damage?
  3. nrayf

    nrayf Active Member VIP

    Also, you listed no witnesses. I saw everything that happened, and pretty sure I took screenies of the chat log of J3LLY83ANS griefing. Once told he would be reported, he continued to destroy everything he could, as revenge. And also, Jelly broke the rules before, as he fistrushed me about 7 times because I slept in his bed, and there was no way for me to warp away, as he would tag me the moment I respawned.
Thread Status:
Not open for further replies.