ZzTheOGzZ Why am I banned?

1. Your ingame name: ZzTheOGzZ
2. Moderator name: ZzTheOGzZ
3. A description of what rule they broke/how they broke it: I din't break anything
4. Evidence/screenshots. Nope

 

This isnt really the section to post this, you should of posted this in ban appeals.

 

Your a mod on mineverse? I didnt know that they started to make people mods already

 

They have not yet, if you click on the tab "members" then find the one called "staff members" it lists the staff members.

 

oh, ok thx

 

I have a few reasons why I dont understand this:
1. Your not a Moderator, This means who is the Mod who banned you.
2. This is in the wrong section. Post this in ban appeals
3. Without any evidence there is no way to tell how.

 

That's true.

 

He was a moderator, or well... not exactly, he was a Prison guard when Mineverse Prison was in it's first month or two of existance, as well as being a moderator on kitpvp. Thing is, he partially used his perms to his advantage in some points, for example, he would jail those who combat logged whilr fighting him, and nearly was able to lure me into wearing hacked armor that he had confiscated from another player. There was another time, in where he repetitively kicked a player just to prove that he has higher authority and that he was "better" then the regular player, I have screenshots of him kicking a player repetitively, however, I will have to dig through my screenshots for the evidence

 

Now, Due to the fact that I do not want anyone but Staff members to see this evidence, I will have to place it in a Hidden content container for moderators/Admins to view, also, @CypriotMerks

Hidden Content:

You must reply before you can see the hidden data contained here.

 

Wow , abuse much? When I met him on KitPvP he seemed like a cool , mature and responsible guys. Guess I was wrong.

 

How do you make just mods see that?

 

Hidden Content:

You must reply before you can see the hidden data contained here.

 

Ummm that didn't help

 

Thank you for your report. This report has been resolved.
This thread was moved to Reports - Archives.