Today I took a little time and added that conditional logic I was talking about in the last post. I also made the output on the page a series of forms pointing to an endpoint that will do the resolution parsing.
I felt a little overwhelmed when I made that list, but doing a few hours a day is making the slow steady progress I need. I'm not too worried about resolution parsing (it should be similar to decision parsing), aesthetics can wait a while at least until beta, authoring tools should just be a different combination of existing functionality, and I can bust out unit testing in a week. My goal is to have a playable version by July.
Decision parsing based on traits
Decision submission, resolution parsing from XML, modifying traits <-- IN PROGRESS
Authoring tools for rooms, including an XML validator and a test feature
Game invites, declines.
General game rules, like death and pants shitter. Email functionality
Unit testing, code cleanup, documentation
Aesthetics
1 Hour
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Today I took a little time and added that conditional logic I was talking about in the last post. I also made the output on the page a series of forms pointing to an endpoint that will do the resolution parsing.
I felt a little overwhelmed when I made that list, but doing a few hours a day is making the slow steady progress I need. I'm not too worried about resolution parsing (it should be similar to decision parsing), aesthetics can wait a while at least until beta, authoring tools should just be a different combination of existing functionality, and I can bust out unit testing in a week. My goal is to have a playable version by July.
Decision parsing based on traits1 Hour