Plan to add state machine section
This commit is contained in:
parent
ea43ff89c2
commit
d95e7bd031
@ -21,9 +21,15 @@ This is a game design document template, ready to be forked by you.
|
||||
## Features
|
||||
* Open to be forked by anyone, really.
|
||||
* Wiki-friendly hierarchical structure.
|
||||
* [Mermaid](http://mermaid.js.org/) used/recommended for flowcharts and diagrams.
|
||||
* [Mermaid](http://mermaid.js.org/) used/recommended for flowchartsm, and diagrams (sequence, state, etc.).
|
||||
* Team-friendly, assuming your team can use Git and Markdown.
|
||||
|
||||
## TODO
|
||||
* Document game object states/state machines.
|
||||
* Needed by (or can be used by) players, NPCs, and tetrominoes alike.
|
||||
* Mermaid can diagram them. Put mermaid to work.
|
||||
* Roadmaps and asset lists can be beneficial. Maybe more project management than design doc turf though.
|
||||
|
||||
## How To Fork
|
||||
I don't personally use Github. I don't want to make it easy for code to become training data, though in truth I know that's a losing battle since [intellectual property law is likely only applied one-way from wealthy to unwealthy individuals](https://arstechnica.com/tech-policy/2025/02/meta-defends-its-vast-book-torrenting-were-just-a-leech-no-proof-of-seeding/). Either way, I fight in my own way.
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user