Quote:
Originally Posted by Angelox
I'm thinking, since Minilogin looks for IP address, have a script that converts the incoming username into a unique number, and insert it into the account table/ip.
|
If Minilogin could use the encrypted username/password string as a unique identifier (think of it as an account ID rather than a username & password), that might work. In other words, allow everyone to login with whatever username/password they want to, but if you enter the wrong one, you won't see your characters. On the plus side, it would be
relatively easy to engineer, and you wouldn't have to worry about registering user accounts. On the downside, it could create a lot of confusion if you enter in the wrong username or password, not to mention server admins tracking down a specific account. At the very least, this might make a good idea for a Minilogin2.
However, I agree, something needs to be done sooner rather than later. Ideally, the underlying issue for the downtime can be resolved now, and we can look toward a better way to handle the inherent negatives of having a central loginserver (limited ability to make enhancements, single point of failure) in the long run.
Threaded Mode
