Ya all know I broke the login process, so I am trying to fix it...
Next step in programming is fixing the mysqldatabase class to do the
same the XML database does, which I already fixed for the most part.
Anarki is working on that, but I bet he can use help. (its a lot of
functions to rewrite)
After that is done the playerlogin class needs more work, and the
adminmanager... I gonna do that myself cause its damn complicated. I
already created two new network packages to make login possible.
The login process is supposed to work like this:
Connection from client -> Server responds with server version and MOTD
and sets connection ID
PLAYERLOGIN package from client, contains everything thats in class
LoginInfoPlayer. RSA, SHA1 or MD5.
Server gets the exact same info from the mysql or XML database and
compares those two.
Server answers with: 'Login incorrect' or sends a list of characters
that player has on the server.
(I got to write a new network package for that, not done yet)
CHARACTERLOGIN package from client. Client sends a character name and a
Server gets the exact same info from the database again and compares. If
its ok he sets the selected character into the world and notifies the
client with a 'login ok, your objectid and zone is blablabla...'
This causes the characters object to deserialize from some storage we
got to think of, cause its not written yet.
Get latest updates about Open Source Projects, Conferences and News.