~nromdotcom/gemif

3c15f37a33f4fe7f755f04f6ce3add230b8266ea — Norm MacLennan 1 year, 2 days ago 4235f61
update api docs
1 files changed, 1 insertions(+), 3 deletions(-)

M static/docs/api.gmi
M static/docs/api.gmi => static/docs/api.gmi +1 -3
@@ 5,6 5,4 @@ So how does this work in the confines of the Gemini protocol?

Making a call to `/start` creates you a new instance of the game, serializes it, and encodes it to base64. This is your `state token`. You are redirected to `/game/[state token]`.

`/game/[state token]` renders your current scene and renders each exit as a link to `/game/[state token]/action/[exit_id]`

Making a request to one of the exits makes the necessary changes to your state token and redirects you back to `/game/[new state token]` which will show you your new scene.
`/game/[state token]` renders your current scene. A "speculative state" is calculated for each exit in the current scene and each exit link is rendered as a link to `/game/[speculative state token]`.