[Galkons refactored]T2 when connecting

**~~kopjekoffiee~~** · 02-01-2011, 10:47 PM

fixed

**~~kopjekoffiee~~** · 02-02-2011, 05:22 PM

bump

**funkE** · 02-02-2011, 05:27 PM

I'm going to go ahead and say the server you're trying to connect to:

Those are the only reasons it would throw a T2.

**Purple** · 02-02-2011, 05:28 PM

Error: T2 - 126,134,249

There's a packet server-sided that has an ID way too high for your client to handle.

**funkE** · 02-02-2011, 05:31 PM

Originally Posted by Ghost++

Error: T2 - 126,134,249

There's a packet server-sided that has an ID way too high for your client to handle.

It sends the packet ids as unsigned byte right? Then it would be up to 255, not 125 like a signed byte.

**~~kopjekoffiee~~** · 02-02-2011, 05:44 PM

Source is impact.

**sigex** · 02-02-2011, 06:45 PM

You need to remove the line of code in the server it's meant to make the client cache but it has be patched and results in a T2 error.

**WH:II:DOW** · 02-02-2011, 06:51 PM

Originally Posted by sigex

You need to remove the line of code in the server it's meant to make the client cache but it has be patched and results in a T2 error.

Wat? A T2 error is caused by an exception in handling the packet while a T1 error relates to wrong packetsizes...

Thread: [Galkons refactored]T2 when connecting