Leeg Posted June 2, 2017 Group: Members Topic Count: 12 Topics Per Day: 0.00 Content Count: 120 Reputation: 44 Joined: 11/13/11 Last Seen: March 13 Share Posted June 2, 2017 (edited) In older clients, you could login through command line using this: -t: 123456 Leeg server -1rag1 However, in clients from 2017, this is not working because apparently the encoding has changed and you get this result: [Notice]: Unknown account (account: ▓XÛ╚│┴®öïçRú▀;¬┼P$T·úy, ip: 127.0.0.1) Does anyone know anything about this enconding change? Thanks. Edited June 2, 2017 by Leeg Quote Link to comment Share on other sites More sharing options...
0 Leeg Posted June 2, 2017 Group: Members Topic Count: 12 Topics Per Day: 0.00 Content Count: 120 Reputation: 44 Joined: 11/13/11 Last Seen: March 13 Author Share Posted June 2, 2017 (edited) After testing with other clients, I believe this is more a server issue than a client one. The enconding of the login has changed, but I don't know when or how exactly, and now this login procedure is broken. Anyone knows why? I'm stupid. Forgot to diff with Use SSO Login packet. Problem solved. Edited June 2, 2017 by Leeg 1 Quote Link to comment Share on other sites More sharing options...
Question
Leeg
In older clients, you could login through command line using this:
However, in clients from 2017, this is not working because apparently the encoding has changed and you get this result:
[Notice]: Unknown account (account: ▓XÛ╚│┴®öïçRú▀;¬┼P$T·úy, ip: 127.0.0.1)
Does anyone know anything about this enconding change?
Thanks.
Edited by LeegLink to comment
Share on other sites
1 answer to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.