Vazelos Posted June 15, 2011 Posted June 15, 2011 Any exploit share is useless if l2j developers hang around on these forums... A quick fix for this exploit is inevitable. So true.
Xanderॐ Posted June 15, 2011 Author Posted June 15, 2011 Anyway, the reason that you got NPE is probably because somehow the account wasnt inside _loginServerClients Come on nick ,thats not an explanation. If somehow the account was not in loginServerClients then it can happen again. And possibly can be triggered by players. I would come discuss that in your forums, but im not welcome there. There's something bigger behind this im sure. Probably some race condition ? As a programmer you can just go and put : if(client == null) return; It fixes it sure, but the cause of the npe is not investigated.
Nik Posted June 15, 2011 Posted June 15, 2011 This is fucking ridiculous... i've investigated for no more than 1 min and this is what i see: case AUTH_SUCCESS: client.setAccount(_user); lc.getCharactersOnAccount(_user); client.setState(LoginClientState.AUTHED_LOGIN); client.setSessionKey(lc.assignSessionKeyToClient(_user, client)); public SessionKey aassignSessionKeyToClient(String account, L2LoginClient client) { SessionKey key; key = new SessionKey(Rnd.nextInt(), Rnd.nextInt(), Rnd.nextInt(), Rnd.nextInt()); _loginServerClients.put(account, client); return key; }
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now