Server Help :: View topic - AS3 Bug, or bot core bug? YOU DECIDE!

Server Help

ASSS Questions - AS3 Bug, or bot core bug? YOU DECIDE!

Cerium - Thu Apr 14, 2005 10:17 pm
Post subject: AS3 Bug, or bot core bug? YOU DECIDE!

d1st0rt brought an interesting bug to my attention... Im not entirely sure which side the problems on (probably mine), so I decided to throw this in trash talk and let MGB move it if he feels the need to do so.

Anyway...
I cant seem to get hybrid to connect to an AS3 server. As far as Ive been able to determine, the server seems to not be responding to the client key (0x00, 0x01). I dont know if its just not getting the packet, if the packet is being constructed incorrectly and ignored or whats going on.

Ive mentioned this to grel both in game (in team and ?message) and email, and he seems to be perma AFK. If anyone else wants to help me figure this out let me know either here, in game, or email (Cerium@gmail.com)

-C

----------
Update:
Packet 'trace'... if you can call it that:

Code: Show/Hide

$> AS.Update Attempting to connect to ss://216.34.65.183:5000
Key: -637195156
SEND: 0x00 0x01 0x6C 0x2C 0x05 0xDA 0x01 0x00
$> Hybrid.Warning Connection timed out. [Spawn: TestBot, ID: 0]
SEND: 0x00 0x07
$> AS.Update Disconnected. Waiting 5000ms...
hybrid.core.events.Disconnected@1f4689e
$> AS.Update Attempting to connect to ss://216.34.65.183:5000
Key: -792992747
SEND: 0x00 0x01 0x15 0xE4 0xBB 0xD0 0x01 0x00
$> Hybrid.Warning Connection timed out. [Spawn: TestBot, ID: 0]
$> AS.Update Disconnected. Waiting 5000ms...
hybrid.core.events.Disconnected@f7f540
$> AS.Update Attempting to connect to ss://216.34.65.183:5000
Key: -1971167499
SEND: 0x00 0x01 0xF5 0x5E 0x82 0x8A 0x01 0x00
$> Hybrid.Warning Connection timed out. [Spawn: TestBot, ID: 0]

CypherJF - Thu Apr 14, 2005 10:19 pm
Post subject:

Probably its own issue because AFAIK asss is able to be connected to with both VIE enc and Continuum enc w/o issues... :/

Cerium - Thu Apr 14, 2005 10:20 pm
Post subject:

Jesus christ that was fast.

Yeah, I had no problems connecting to asss previously so I assumed everything worked. I didnt even know it was broken until dist mentioned it to me. Thing is, it connects to subgame servers no problem...

Dr Brain - Thu Apr 14, 2005 10:52 pm
Post subject:

Do other bots (esp MERV) connect? I ask not in the general case, but in your specific case.

There are numerous settings issues that could stop a bot from connecting, and I'd like to have it stated early on in the thread that you've tested a MERVBot in your asss zone with the same username and password.

Cerium - Thu Apr 14, 2005 11:01 pm
Post subject:

Well MERV connects fine... so its safe to assume its something I screwed up... but im not seeing it.

Cerium - Fri Apr 15, 2005 2:23 pm
Post subject:

Ok, so weve determined without a doubt that its the core. Theres something im overlooking thats causing this issue.

What I dont understand, is what kind of bug could cause this behavior? When connecting to a subgame server, theres no problems. However, when attempting to connect to an ASSS server, either the server isnt getting the intial packet, or its ignoring it.

Someone clue me in... im busting my head against a wall...

Cerium - Sat Apr 16, 2005 3:01 pm
Post subject:

Ok, so anyone whos curious... Ive figured out the problem. I feel like a dumbass for missing this, so feel free to flame.

1) The core was attempting to encrypt packets prior to receiving the server key. This didnt really encrypt anything, it was just changing the last two bytes in the client key to something OTHER than 0x01 0x00.

2) ASSS seems to ignore connections if the client protocol version isnt 'subspace' or 'continuum'.

3) Subgame on the other hand, seems to only check for 'continuum' and assumes anything else is 'subspace'. This explains why the bug was still allowing the core to function on subgame servers, while ASSS servers were silently giving my bots the finger.

The only thing Id like to see change, is perhaps have ASSS print a warning to the console when such a packet is ignored, or maybe even have it send the disconnect packet as a response, rather than simply ignoring it.

I know its my own fault, but this would have taken me all of 30 seconds to find/fix had there been some kind of notification.

-C

Cyan~Fire - Sun Apr 17, 2005 10:52 am
Post subject:

Hybrid connects with a different protocol than 'subspace'?

Edit: Fixed, thanks Brain. I get these new fangled Java things mixed up.

Dr Brain - Sun Apr 17, 2005 11:11 am
Post subject:

Uh? No one has been talking about TWCore in this thread.

D1st0rt - Sun Apr 17, 2005 9:33 pm
Post subject:

When TWCore tries to log in, it says the login packet is the wrong size (117)

Cerium - Sun Apr 17, 2005 11:09 pm
Post subject:

Cyan~Fire wrote:

Hybrid connects with a different protocol than 'subspace'?

Edit: Fixed, thanks Brain. I get these new fangled Java things mixed up.

When the encryption is broken, yes =)