Re: The BNLS Protocol Spec (http://www.valhallalegends.com/yoni/BNLSProtocolSpec.txt).
Where it has "Message Id's",
Quote...
#define BNLS_SERVERLOGONPROOF (0x14)
#define BNLS_RESERVED0 (0x15)
#define BNLS_RESERVED1 (0x16)
#define BNLS_RESERVED2 (0x17)
#define BNLS_VERSIONCHECKEX (0x18)
I was just wondering about the Reserved spots. I understand you want them incase for future upgrades you implement for packets in. But why not just have it like,
Quote...
#define BNLS_SERVERLOGONPROOF (0x14)
#define BNLS_VERSIONCHECKEX (0x15)
... if more needed then...
#define BNLS_RESERVED0 (0x16)
#define BNLS_RESERVED1 (0x17)
#define BNLS_RESERVED2 (0x18)
Is there a particular reason for having BNLS_VERSIONCHECKEX as (0x18)?
They're probably super secret ones, but you can think they are reserved ;)
They're probably intended to use as some sort of in-between functionality, but hasn't been done yet or notified of to the public.
They're probably something not available to the public, however, working yet outdated since the alpha stage of it's main purpose. Setting BNLS_VERSIONCHECKEX to be an already existant message ID would cause massive confusion since your bot most likely won't support both protocols.
So in the end, don't worry about them.