Lee, here's what I've currently going on the data model:
Crewmember (This is where we store characters, not players)
First_Name
Last_Name
Rank
Faction
Experience_Captain
Experience_Helm
Experience_Weapons
Experience_Communications
Experience_Engineering
Experience_Science
Biography
Image
Profile_ID*
Username
Password
*Profile ID is tied to a different table that stores the actual user's (real world) info, not the character's info.
Session (This is where we store what happened in the mission)
Session_Name
Mission_Name
Session_Init
Mission_Start
Mission_End
Bridge_Instances**
Status
**List of bridges involved in the session
Bridge Instance (This is where we store where the characters work during a particular session)
Bridge_Number***
Host_Comp_ID
Ship_Name
Team_Name
Faction
Captain****
Helm****
Weapons****
Communications****
Engineering****
Science****
Log****
Auxiliary_Log****
Bridge_Init
*** The bridge ID; each bridge should be assigned a unique number
****Selectable from Crewmember table, delimited by faction
All of these sessions would have unique IDs, so a specific mission would be tied to a Session, which would be tied one or more bridges, each of which would be a bridge instance containing several crewmembers.
There should be a larger Universe table as well; these will be instanced versions globalized mods/game universes that keep track of overall victories/defeats among multiple bridges against preset victory conditions (E.G.: Universe 48 is stock Artemis, and the first faction to make it to 20 victories/accumulate 20 victory points wins). This enables a "league" type ongoing war situation.
I'm still building it out, but I'd love to hear any feedback or suggestions!
[Last edited Oct 19, 2012 09:40:21]