Started game invites. Definitely feel like I have a process for creating modules classes for interfacing with database objects. I think every module acts pretty consistently with its use of static methods for creating, constructors for building objects from ids, and various methods handling functionality. One thing I wish I would have done is organized the objects with load() and save() methods from the db. GamePlayer has save, but its the only one. I guess its ok because it changes the most from outside forces (GameRoom) wheras other classes generally handle their updates/SQL themselves.
So I have the data model and the ability to invite players, but I don't have anything to display them on the player's home dashboard. That'll be next, then responding to invites, deleting invitations, and starting the game. I think I can knock all of that out next session, its a breeze compared to room authorship tools.
As far as getting into/out of games, I'll have into games pretty easily; click a button from an invite, pull all players that responded yes to invite, and then create dungeon. Ending the game I haven't really thought about too much, but it'll probably be a method in the Dungeon module.
Decision parsing based on traits
Decision submission, resolution parsing from XML, modifying traits
Authoring tools for rooms
XML validator and a test feature
Enter game and exit game (merge traits back to player) <--- IN PROGRESS
Game invites, declines. <--- IN PROGRESS
General game rules, like death and pants shitter.
Email functionality, day timer
Unit testing, code cleanup, documentation, minor aesthetic fixes
3 Hours
Last edit: dungeonsoffear 2015-11-22
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Started game invites. Definitely feel like I have a process for creating modules classes for interfacing with database objects. I think every module acts pretty consistently with its use of static methods for creating, constructors for building objects from ids, and various methods handling functionality. One thing I wish I would have done is organized the objects with load() and save() methods from the db. GamePlayer has save, but its the only one. I guess its ok because it changes the most from outside forces (GameRoom) wheras other classes generally handle their updates/SQL themselves.
So I have the data model and the ability to invite players, but I don't have anything to display them on the player's home dashboard. That'll be next, then responding to invites, deleting invitations, and starting the game. I think I can knock all of that out next session, its a breeze compared to room authorship tools.
As far as getting into/out of games, I'll have into games pretty easily; click a button from an invite, pull all players that responded yes to invite, and then create dungeon. Ending the game I haven't really thought about too much, but it'll probably be a method in the Dungeon module.
3 Hours
Last edit: dungeonsoffear 2015-11-22