At the moment Reflect.Login.GetClientState is used to see if we're logged in. When the client is loading up a new map area we won't get the same result as we want, typically we want 30, as that's the state of us being logged in. When the client loads up a new map area we get 45, and therefor we won't be "Logged in" in terms of Reflect.Login.GetClientState.
Discussion, how do we handle this in the best possible way? I want a stable and safe include that can handle the major network problems that OSRS is having.
Should we just put all the client states into a TIntarray and declare it a win?