by Narc » Mon May 14, 2012 1:00 pm
Ok I will try and clear this up. A ticket got made friday about biggie crashing 2 different game servers. Most of you already know that weekends I am with my fiance and family. I dont do any TPG work. If I do its rare. My admins went threw the evidence and verified it was him and he did infact crash the servers. So it was just waiting my approval to go ahead and make the suspension before the next matches. It was getting late on sunday night that I got a text informing me about the whole situation. Once I got home, I had to try and get 6 for my match. I gave pat the go ahead to add the suspension because I was busy. I had the final say I gave the go ahead, Pat was following my orders thats it. I was running late and thats why it was posted so late. But if someone is crashing servers as the rule states its a permanent ban. That person should NOT be able to play a match the same week he crashed servers. So yes it was kind of a last minute ban because I got home late, but it was not ment to screw any team last minute I am sorry that it did. I just got home late, to actually give the go ahead. As for motive, when I asked you if you were playing and to ring, I honestly didnt even know what team you were on. That is why I didnt say anything to you about the ban. I really didnt put two and two together till you made that post.
I hope that shed some light on the subject. I dont regret the ban and I hope it sends out a good messege to the kids that want to crash servers.
Also for teams that allow banned players to scrim with them, how can you get mad at a team for not wanting to scrim you? They say no and you crash thier server. Why would they want to play a team that has no problems allowing a banned player to scrim with them. I dont blame them and support them 100%.
Also TPG had nothing to do with setting your team inactive. When the other team reported an FFW the site automatically sets the team inactive. I went ahead and set the team back active once I seen it. Our policy is to wait until the team that is set inactive to create a ticket and request to be set back active. However I did not wait for a ticket because of the situation.
Ok I will try and clear this up. A ticket got made friday about biggie crashing 2 different game servers. Most of you already know that weekends I am with my fiance and family. I dont do any TPG work. If I do its rare. My admins went threw the evidence and verified it was him and he did infact crash the servers. So it was just waiting my approval to go ahead and make the suspension before the next matches. It was getting late on sunday night that I got a text informing me about the whole situation. Once I got home, I had to try and get 6 for my match. I gave pat the go ahead to add the suspension because I was busy. I had the final say I gave the go ahead, Pat was following my orders thats it. I was running late and thats why it was posted so late. But if someone is crashing servers as the rule states its a permanent ban. That person should NOT be able to play a match the same week he crashed servers. So yes it was kind of a last minute ban because I got home late, but it was not ment to screw any team last minute I am sorry that it did. I just got home late, to actually give the go ahead. As for motive, when I asked you if you were playing and to ring, I honestly didnt even know what team you were on. That is why I didnt say anything to you about the ban. I really didnt put two and two together till you made that post.
I hope that shed some light on the subject. I dont regret the ban and I hope it sends out a good messege to the kids that want to crash servers.
Also for teams that allow banned players to scrim with them, how can you get mad at a team for not wanting to scrim you? They say no and you crash thier server. Why would they want to play a team that has no problems allowing a banned player to scrim with them. I dont blame them and support them 100%.
Also TPG had nothing to do with setting your team inactive. When the other team reported an FFW the site automatically sets the team inactive. I went ahead and set the team back active once I seen it. Our policy is to wait until the team that is set inactive to create a ticket and request to be set back active. However I did not wait for a ticket because of the situation.