Tug wrote:
Sporkinator wrote:
I refuse to blame Tug at this point, as I did not ban Tug's IP to stop the packeting, nor did I ban Dx.
What happened after that "point" and now that made you start blame me?
Me giving good advice?
Are you being serious?
Are you being serious? No, you're playing games...
Tug wrote:
How nice of you to not blame me.
Clearly I am too nice. You are first to reply. Sign of guilt and "relief" that I "didn't" blame you. I suspected you all along, I just said otherwise on purpose to see how you would reply. When you stop playing games with me, maybe I'll stop playing games with you.

Quote:
Me giving good advice?
What advice? Oh! You mean deflecting the blame by telling me to contact the server owner and telling him to restart it? That's got to be the dumbest piece of "advice" I ever heard.
1. Eddy owns the server.
2. I do not have Eddy's email.
3. Eddy wouldn't listen to me even if I did.
4. Do servers typically flood connections on their own? Yeah right.

battlezone1.net never did that. Perhaps Eddy hacked more parts of the server and a glitch occurred?

Which is it? I got banned from Eddy's server. Then when I got unbanned, the high ping appeared. Coincidence? No.
6. My IP changes when I reconnect, and I was being packeted every time. The server would ping the whole range I was in? I then switched ranges and it temporarily solved it... but then I got packeted again once you got my new IP.
5. Restarting the server would be disruptive... oh I forgot, nobody plays there. That would work perfectly!

7. You, Dx, Eddy, and the rest of Team Dummy are all the same to me, so even if you "didn't do it" (what a joke), I realize now you should share the blame regardless. Until you separate yourself from Team Dummy and make public apology for working against BZ, hacking, and lying, you are scum and I will trample you.