Jump to content

tymur


Tyler123
 Share

Recommended Posts

In-game name:

tymur

Steam ID:

tymur03

Date of ban:

17/2/17

Staff member that banned you:

Tidus

Reason for ban:

Breaking NLR

Why do you think you were banned:

For breaking NLR

Do you believe your ban was unjustified, if so explain why:

No, because i believed i was getting RDMed so when i was killed i spawned back there to call an admin however i was instantly killed so i spawned again and was killed i believed i was being killed by an admin so i continuously respawned in the same place in an attempt to do the right thing and approach the admin to inform him on the RDM

If you believe your ban was justified why should you be unbanned:

I do not believe my ban was justified

Where there any extenuating circumstances that contributed to your ban:

No there were not

Please confirm you've read & understood the rules

Yes

Please confirm you understand there is no timeframe

Yes

Edited by Tyler123
Link to comment
Share on other sites

If you're going to get continuously RDM'ed in the same situation, you shouldn't keep returning to the situation; instead go onto Reborn's Teamspeak and go to the 'Requesting Staff Help Waiting Room' where a Community Support will come and help you resolve your situation, even if it is going to involve a member of staff. Returning to the same situation continuously just makes it look like you're blatantly breaking NLR,as you're not contacting any of the Staff team so from their POV you're just breaking server rules. Any member of staff will be happy to help you resolve the situation; you just need to go about your situation appropriately.

I wasn't involved in the situation, and so I will leave this for @Tidus to process.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.