betaWorld

Whether the client is connecting to this world under the beta world flag of 65536, or 0x10000. If this is the case, the login block that the client transmits differs from the usual one, as it ends up splitting CRCs up into two incomplete sections. This was intended to prevent people from downloading most of the beta cache without the access to the beta server, however the implementation is done incorrectly and all it ends up preventing is people who use the client to download the cache. The JS5 server is not notified of these constraints and will server every cache group as requested regardless of the status. Because of this, the implementation for the beta worlds is simplified to just support logging in via a beta world, which is accomplished by immediately requesting the remaining beta CRCs before passing the login request on to the server. By the time the server receives information about the request, all the CRCs have been obtained. It is worth noting that if the client flag status differs from the server, one of two possible scenarios will occur - either you will get an exception as the server tries to read more bytes than what the client wrote via the CRC block, or the server never receives enough bytes to consider the login block complete, which means the login request will hang and eventually time out.