[airtalking]

I'm working on a new tool to replace the magelo clone, and incorporate several more parts of server management. One of these parts is allowing users to create some accounts and do some proof of ownership of a game account. From there they can have a pre-validated character move, and character transfer and a few other things.... When I started this I was working off of remove login server, and/or minilogin server.

From what I understand EQEmu's server would allow you to create a login acct, then when logging in to a play server the accounts login is passed to the play server and added to the "accounts" table. The password field remains empty. This is all correct?


For Mini login, it also uses the "accounts" table. A tool of some sort would have to be used to create new "minilogin" accounts, which would add an entry to this accounts table, and save their password in plain text. Is that all correct?


With the issues PEQ is dealing with, from what I understand it is possible for a server to be running the full login server, but locally... i.e. not rellying on EQEmu to pass to username. In this scenario, the new accounts would be created in this NEW login server accounts table. Then when a person logs into the play server, the account would also get plugged into the accounts table. The password in this login server accounts table is SHA1 hashed. My plan for local login server was to create their account in the login server table, AND in the account table.


Do I have a proper understanding of this situation... or am I way off on this?

My plan was to just have an admin option of "local login server", "remote login server", "minilogin" and then have these things happen automatically in the background. For instance, if they select remote login, then it would deactivate the "create account" portions since that would be handled by another site...