I was thinking of implementing something of this sort a while back, but, due to life events, I have pretty much stopped coding for the mud I work on.
My plans were to implement something along the lines of an account system. A user would log on under his/her account, then choose what character to play from there. I was looking at something along the lines of creating an account file that consisted of nothing but the user's account logon info (name and pword), email address, and a list of the characters that he/she owned. During gameplay, when a person logged out, they would go to their account screen, listing account options (delete a char, log in as another char, etc). I don't know how much this helps you, but that was the process I thought of. As far as coding it, that's another story. Greg Petty -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Gries Sent: Monday, August 12, 2002 9:10 PM To: [email protected] Subject: Embracing But Controlling Multiplay Greetings. I am looking for a code snippet that instead of prevent multiplay, actually embraces it, but in a controlled form. I am ideally looking for something similar to the retail form of choosing a character (login, pass, list of character associated to that account), but I am willing to consider other solutions as well. In addition, in case there is not exactly the code snippet I am looking for, is there an explanation of the player authentication somewhere on the web? If so, I can put a snippet together for all to enjoy. Take care and thank you. -- ROM mailing list [email protected] http://www.rom.org/cgi-bin/mailman/listinfo/rom
