Made a flow chart for Phase 1 at work yesterday during the course of the day, got quite busy though.
Think I'll finish it today and share it here but I did print it and complete a few steps such as the server<>client handshake.
* Server stores socket IDs and IPs in a 2D array since a DS_List seems completely silly to me
*Client enters username and password, client side prevents the following [no username below 3 characters or above 20 characters, no password below 6 characters or above 20 characters, no blank username/password]
*Client sends username/password to server, server does the exact same checks but needs to check to see if the username already exists, which is where I stopped.
So the next thing I think is to figure out where I'll store the player username and password.. I'm thinking of creating an ini file, but here's the catch, there aren't any registered users yet, so I sort of need to predict what I will do..
Can I even search a directory for an ini file name ?
This is a difficult one because I don't want too many links back and forth. I really feel that I need higher dimensions though,
so maybe what I'll do is I'll create ini files with the username, then link that username to the open 2D array that stores the Socket ID and IP as [x,2] = usn,
and then within that ini file for the player I'll store precious relative to players state variables.. like last x/y pos, character appearance, and then from there have a link to other INI files which will have the players inventory, their skills, their dough, etc.
Xer0botXer0.ini - Stores some variables as well as reference links to other ini files.
Xer0botXer0_Inventory.ini
Xer0botXer0_Skills.ini
and so forth.
But those reference links may then not be necessary considering how easy it is to guess what the other ini file names will be!
Now if someone is following this, is there a better way at handling such a variety of information in an organized manner per user ?
Well I'm off to work.
