You're welcome, I try to give as much relevant info on bugs as I can when reporting.
Speaking of, I think the choice between where to start route is borked right now. It worked fine the first time after update, but after some time - I think it might be connected to me reloading the page, so the game loaded an already post-update save instead of migrating from an old save - it just stopped doing anything; I can change the desired route in the settings, but it doesn't affect gameplay, I still get reincarnated in Willowbrook. The option to reincarnate in Harmony village doesn't appear, either, when doing manual reincarnation - and I'm fairly sure I had that at some point.
EDIT: My bad! The option to reincarnate in Harmony on death does appear - it's just unavailable when doing a force reincarnation, but that's likely intended.
Automated testing is certainly good with the breadth of what you're doing here, but I'm not sure if you're doing actual manual testing, because there have been several UI issues with elements being un-interactable.
The bound beast's name input is one such case, with the name input soft-locking the game until you realise you can right-click it (or probably tab to it) to interact. Travel after the Qi Core is another case - the dropdowns and the wilderness button aren't interactable via LMB either. You can solve it with the dropdowns by, again, right-clicking them or tabbing to focus on them then pressing space to interact, but no such luck with wilderness (since space is pause instead).
Condensation button doesn't work, but I'm not sure if it's because of some cryptic extra requirements or what. It's pressable, but nothing results from pressing it.
The toggle for automating choices in the settings doesn't seem to work - I press it, it acknowledges the press via animation, but it doesn't check.
I'm enjoying this so far, a lot, but currently it's been very frustrating being unable to interact with the content due to UI bugs.
Maxed out my body (at 190.5, currently), reloaded the page and suddenly it's back down to 140.5. I assume it's because the clamping to max on load happens before the extra +50 from Tempering the Meridian Frame or whatever the routine was called is applied.
I'd probably suggest keeping something like a "real body" value that doesn't ever get clamped and only clamping it for effective body, calculating that on changes to minimise the impact of further errors like these.
On that note, there probably should be a way to see your max body and its sources.
Hey there! Thanks for your feedback; tbh, I personally ran out of steam somewhere mid-jam so where there could be some polish applied (like said restart button) instead was just a void of, well, no polish. Still, though, it's useful for further developments :D
