Author Topic: Not again...  (Read 1731 times)

Br55HiT

  • 68 Carbine
  • Posts: 351
Not again...
« on: April 04, 2007, 02:49:08 PM »
Well it looks like another ban aimed at someone else managed to get me again.  I don't know if it was another Warhead ban or someone else.  I just know for some reason i'm banned...again.  :(

KiLo

  • Autococker
  • Posts: 2086
Re: Not again...
« Reply #1 on: April 04, 2007, 02:53:20 PM »
This might be the ban aimed at eNergizer because Jits banned 24.141.xxx.xxx so if your IP starts like that it might be the culprit.

jitspoe

  • Administrator
  • Autococker
  • Posts: 18802
Re: Not again...
« Reply #2 on: April 04, 2007, 04:22:10 PM »
This should be fixed now.  Let me know if you're still banned after about 30 minutes or so.

slauter

  • PGP
  • Posts: 2
Similar Problem
« Reply #3 on: April 04, 2007, 08:02:42 PM »
I was playing today and in the middle of a game I was booted and notified that I was banned. I have never used a cheat so I think it might have been a similar problem. Is it is possible to get this problem resolved because I would like to go back to playing soon thank you.

Kaos

  • VM-68
  • Posts: 201
Re: Not again...
« Reply #4 on: April 04, 2007, 08:05:16 PM »
yes it will once jitspoe sees this thread again he will try to solve ur ban issue

XtremeBain

  • Developer
  • Autococker
  • Posts: 1470
Re: Not again...
« Reply #5 on: April 04, 2007, 08:07:03 PM »
Enegizer is getting everyone in Hamilton banned while he changes his IP to evade bans.

Br55HiT

  • 68 Carbine
  • Posts: 351
Re: Not again...
« Reply #6 on: April 04, 2007, 08:08:37 PM »
Um...Jitspoe you did fix it earlier but now it's about 10 PM here and it says i'm banned again.

jitspoe

  • Administrator
  • Autococker
  • Posts: 18802
Re: Not again...
« Reply #7 on: April 04, 2007, 08:22:54 PM »
The cause for this is that the buffer used to download the global ban list was only large enough to hold 1024 bytes when it was supposed to have held 1024 bans.  As a result, sometimes the list gets truncated mid-ip.  In this case, it looks like it got truncated at "65", effectively banning 65.*.*.*.  I have adjusted the ban list to print out fewer IP's to prevent mid-ip truncation.  I did this earlier today, but I guess the list cut off sooner than I thought and it was another ip that began with "65" causing the issue.  Hopefully this fixes it.  Sorry for the inconvenience.

slauter

  • PGP
  • Posts: 2
Re: Not again...
« Reply #8 on: April 08, 2007, 10:24:31 AM »
Thank you for fixing it.