Packet Parser|Tokenizer (unknown/unsupported packets)

[Raider]

Private server
kRO_RagexeRE_2009_11_04a
r8390
Packet Parser: Unknown switch: 07FA

[Raider]

Private server
kRO_RagexeRE_2009_01_21a
r8390
Packet Parser: Unknown switch: 07D9
Packet Parser: Unknown switch: 07F9

[Raider]

Private server
kRO_RagexeRE_2009_09_22a
r8390
Packet Parser: Unknown switch: 07F9

[Raider]

Private server
kRO_RagexeRE_2009_01_21a
r8390
Packet Tokenizer: Unknown switch: 08B9
Packet Tokenizer: Unknown switch: 0856
Packet Tokenizer: Unknown switch: 0857

[Raider]

Private server
kRO_RagexeRE_2009_11_04a
r8390
Packet Parser: Unhandled Packet: 0440 Handler: millenium_shield

[Raider]

Private server
kRO_RagexeRE_2010_11_24a
r8390
Packet Parser: Unknown switch: 08B9

[Raider]

Private server
kRO_RagexeRE_2010_11_04a
r8390
Packet Parser: Unknown switch: 07FB

[Kaspy]

If you can contextualize the moment you receive these packages will help.

[Raider]

If you can contextualize the moment you receive these packages will help.

Ah I see, maybe it's better to just forget these posts because I have the feeling it's most of the time caused by a wrong serverType.
@KeplerBR, just a question: Is it possible to detect the serverType while extracting recvpackets?

[Kaspy]

@KeplerBR, just a question: Is it possible to detect the serverType while extracting recvpackets?

I could not say that... Try to see this.
You can get an idea of ​​using ServerType ideal as the base charBlockSize and how the server is updated. Typically, you use the latest version of kRO.