Automate game state

[alexrutar]

This WIP is to automate the creation of all the game state files.

[alexrutar]

TODO:

• [ ] Convert sites to a table, and render them in a more robust way. Maybe worth adding the site images, as well?
• [ ] Render the #player-profiles table automatically. This will require deciding on a data format, adding the data to assets/js/game_data.js, and then generating the table with this information along with the info pulled from the savestring.
• [ ] Restructure site data output from oath_parser.js into the form {cradle: [site, ...], ...} rather than an index-sensitive array.
• [x] Change suit order to alphabetical, or match board order, etc. (just modify suits array).

Basically, the required data should be something like a dict with keys that are the house colors, e.g.

"yellow": {
  "player": "Andreas",
  "name": "House of Dawn"
}

[alexrutar]

Also, it would be nice if the table of player images were responsive: i.e. display the images in a single column if the page is sufficiently narrow, and in 2 columns otherwise.

[alexrutar]

The suit order can now be changed. Is there a "canonical order"? Perhaps alphabetical, or perhaps the order presented on the board itself.

[AndBM]

The suit order can now be changed. Is there a "canonical order"? Perhaps alphabetical, or perhaps the order presented on the board itself.

There is a canonical order in the LUA files, but it doesn't really mean anything. I would actually prefer to change the order to the order on the board: Discord, Arcane, Order, Hearth, Beast, Nomad.

[alexrutar]

Also, what does the save.name variable mean? In the parser output.

[AndBM]

The save.name string is the chronicle name, in this case "The Helichrysum Chronicle"

[alexrutar]

Cool, I can render this into the state as well automatically.

[AndBM]

It already is, in default.html, the element with id "name".

[alexrutar]

That element no longer seems to exist? I must have deleted it somewhere, and I cannot remember when. It's missing already in the main branch.

Anyway I added it back now. Also, I realized it's possible to access site variables directly from the JS at render-time! This means all the configuration files don't need to be in game_state.js and can instead be put directly into _config.yml. This is really convenient from a packaging / organizational perspective.

Edit: I've realized this is a bad idea - see #11 for the proper way to do this.

[alexrutar]

Alright all done now! The code is fully running - just the calls to render the player table is hard-coded. I'll leave it to you to edit this to get the correct calls out of the savestring.