JacketOfGreen
Grandmaster Knight
Name of the server you were on N/A
Name of the person causing trouble Rocon/Rocond/Dennis/1tesPmrs_Rek_rocon
Nature of their offense Trolling every regiment possible.
Time and date of their offense Er... probably about 2:30PM BST.
If needed, what your relationship was to the offense in question. Kicked him from our reg.
Any proof if you have it, For instance screenshots. (use spoilers!) Nope.
So here's my ban request. This isn't a conventional ban request, I'm not requesting for this person to be banned from a particular server, more like every server. Preferably to ban him, but at best warn you all of him, and to make sure you are aware of the situation.
The person in question is called Dennis. Or maybe Rocon/Rocond. It all depends. Some of you may remember him from a long time ago when he used to troll ts.22nd.eu under the name USSR Supreme Soviet Commander Dennis, or something along those lines. I know the 1er will remember him, they had a run in with him a long time ago which almost led to a lot of their members leaving.
Well, this guy is back in the community. But, under his new name he joined our regiment with me unaware. However I quickly realised who he was when my teamspeak was flooded with people complaining about someone called 1tesPmrs_Rek_rocon was trolling their teamspeaks. A lot of them.
So, here we are. I have banned him from our TS, he has been banned from the 22nd ts for an hour I think, and the Prussian Army TS for 24 hours. But not only is he refusing to remove his tags, he is also now directing people to our teamspeak to try to get them to rage at me and to blame me for this. He has been kicked from the regiment but, as I stated, has refused to change his tags and has insisted on trolling under our name. So here's the double edged sword of my point: do not blame us for this, nor do not consider the 1tes to be the cause of this, we do not condone it and he is not in our reg.
tl;dr Please ban 1tesPmrs_Rek_rocon if he joins your teamspeak or game server. I think a community ban might be in order.
Name of the person causing trouble Rocon/Rocond/Dennis/1tesPmrs_Rek_rocon
Nature of their offense Trolling every regiment possible.
Time and date of their offense Er... probably about 2:30PM BST.
If needed, what your relationship was to the offense in question. Kicked him from our reg.
Any proof if you have it, For instance screenshots. (use spoilers!) Nope.
So here's my ban request. This isn't a conventional ban request, I'm not requesting for this person to be banned from a particular server, more like every server. Preferably to ban him, but at best warn you all of him, and to make sure you are aware of the situation.
The person in question is called Dennis. Or maybe Rocon/Rocond. It all depends. Some of you may remember him from a long time ago when he used to troll ts.22nd.eu under the name USSR Supreme Soviet Commander Dennis, or something along those lines. I know the 1er will remember him, they had a run in with him a long time ago which almost led to a lot of their members leaving.
Well, this guy is back in the community. But, under his new name he joined our regiment with me unaware. However I quickly realised who he was when my teamspeak was flooded with people complaining about someone called 1tesPmrs_Rek_rocon was trolling their teamspeaks. A lot of them.
So, here we are. I have banned him from our TS, he has been banned from the 22nd ts for an hour I think, and the Prussian Army TS for 24 hours. But not only is he refusing to remove his tags, he is also now directing people to our teamspeak to try to get them to rage at me and to blame me for this. He has been kicked from the regiment but, as I stated, has refused to change his tags and has insisted on trolling under our name. So here's the double edged sword of my point: do not blame us for this, nor do not consider the 1tes to be the cause of this, we do not condone it and he is not in our reg.
tl;dr Please ban 1tesPmrs_Rek_rocon if he joins your teamspeak or game server. I think a community ban might be in order.
