Got Connect challenge Request from 68.8.159.84:21203Got connect request from 68.8.159.84:21203 net name = ZorakiAUTHCHECK: Zoraki = internet client -> internet server, regular authAuth Init Successfull: ZorakiCADD: 223974 68.8.159.84:21203 +- bl_id = 4654346543 Zoraki +- no auto admin*** Sending mission load to client: Slayer (Server): Sending Handshake: ZorakiError: NetStringTable::incStringRef() - id "163743" out of range (size = 1024)Error: NetStringTable::lookupString() - id "163743" out of range (size = 1024)Error: NetStringTable::removeString() - id "163743" out of range (size = 1024)
inb4 revoke of Zoraki
Got Connect challenge Request from 68.8.159.84:21203Got connect request from 68.8.159.84:21203 net name = Brian Hyland
Is it possible to have your server protected somehow?
$LoggedIP16235 = "68.8.159.84";$LoggedIP44947 = "68.8.159.84";$LoggedIP45391 = "68.8.159.84";$LoggedIP18114 = "68.8.159.84";$LoggedIP43160 = "68.8.159.84";
Would just IP banning work?
I've tried traditional banning and IP banning and if I recall correctly, a user named 'cca' could still attempt to join, while banned, and trigger the crash anyways.
If someone is banned and they try to join, it's literally impossible to trigger the crash in time before they're booted from the server.
I wouldn't be so sure. I remember kalphiter would join when banned and manage to get a chat message into the server before it kicked in. I suspect there's a very small window of time for something to happen from when a player joins and when they are rejected from the server.
Zoraki is Hair, just for the record guys.