The API can already toggle smart supply on/off, but can't manage the
related controls for whether smart supply will draw from the existing
materials in the warehouse. Without it, we can't keep some resources in
storage to boost the production multiplier without disabling smart
supply entirely.
This includes a tool to update the various files in the repo that need
to change when a version increments.
It also includes a workflow to trigger the action manually, passing it a
version & a changelog url. It'll update the values, build the app, build
the doc, make a commit in a branch, and create a pull request to merge
this stuff back into dev.
Rewrote the changelog script to use primarily merged pull requests
between "commit A" and "commit B".
It uses the GitHub rest api. The resulting data is pushed to a draft gist.
Manual usage is in the README.
Also adds a GitHub workflow action to run the tool on demand, through
the GitHub action's interface.
Segments the table into multiple expandable parts using the raw RST directive to add HTML directly to the page. Not really a great practice, but would at least quell any arguments as to how spoiler heavy the page is in the meantime.
I'm not sure that the proposed change is up to standard, but will open the PR based on initial feedback to screenshots and leave for others to decide.
https://discord.com/channels/415207508303544321/924108882551386133/935278973154361434 - Screenshots of what it looks like when generated locally with sphinx
Copy the terminal commands into the player object so that they are saved
between game reloads.
Adds a 'history' command to display history, and a 'history -c' command
to clear it from both the current terminal & the player's save.
Code example comment represented passing '10' as an arg to the script, when actually it's the number of threads so a `-t 10` flag. Fixed the comment to show this.
It may be intentional to use hack for all 3 (ie, assume the player makes the connection that can't hack, also means can't grow or weaken), in which case, disregard.
On the other hand, it could've easily been a copy/paste artifact, and this would be more explicitly clear, so thought it was worth bringing up.
