A solid pre-launch sweep across systems, especially around status effects, death states, and UI feedback.
Fixes like poison resetting, HP not hitting zero, and “no energy” prompts misfiring are the kind of issues that can quietly break player trust in a system-heavy game.
With the balance changes and added content, launch will be the real test once more players start pushing edge cases in combat.
Looking forward to hearing how it holds up live.
All the best :)
Yeah, that kind of “no impact” feedback is one of the fastest ways to lose player trust.
I was commenting from a QA perspective based on your devlog, but it’s good to see the core issue was prioritised and fixed quickly.
Will be interesting to see what shows up once your players start pushing those scaling edges in real runs!
Nice to see this get a full revision. Simplifying how checks and modifiers work sounds like a strong move, especially if it speeds things up and makes it easier to follow. Pulling together feedback from play sessions and reworking the flow is always a big step, looking forward to seeing how it plays.
Nice update. Fixing softlocks in those late scenes is a big one, especially when they happen close to the end. The cutscene skipping from unused devices is a great catch too, that’s the kind of issue that can feel really confusing from a player side. The extra resolution options are a nice touch as well.
Nice update, there’s a lot packed into this one. The new enemies look like they’ll add some fun movement and interaction, especially with how they push or boost the player. Fixing a game-breaking pause bug is a big one too. With all the new elements and systems, it’ll be interesting to see how clearly everything reads during play.
Nice update. Removing the hidden hotspot in the prologue is a solid fix, loops like that can quietly trap players early on. Might be worth double-checking that section so interactions are clearly visible and players always know what they can click or do. The translation overhaul looks strong too, especially exposing tooltips, those are easy to miss.
Appreciate that, and yeah totally fair on the time constraints as a solo dev, that’s always the trade-off.
I’ll give the demo a proper pass when I get a chance and focus on those risk areas, especially cloud saves and leaderboard consistency since those tend to break in less obvious ways.
If I find anything reproducible I’ll send it over on your discord, properly structured rather than just “it feels off” reports.
Nice update, especially the settings and combat tweaks.
If I was testing this build, I’d focus on:
Changes like these can shift balance and behaviour quite a bit, so I’d be checking both normal runs and edge cases.
Solid patch, this is the kind of stability work that really improves the overall experience.
I’d recommend testing:
This feels very state-driven, so I’d focus more on transitions and odd scenarios rather than just straightforward playthroughs.
Nice update, especially the level of detail in the fixes.
If I was testing this build, I’d focus on:
The save/load and speed-related physics changes feel like the highest risk areas, since they can introduce issues that only show up after longer play sessions.
Nice update, this touches a lot of core systems at once.
If I was testing this build, I’d focus on:
The fluid simulation and multiplayer changes feel like the highest-risk areas, since they tend to introduce subtle issues that don’t show up immediately.
Nice update, especially this close to release.
If I was testing this build, I’d focus on:
The cloud saves and optimisation changes feel like the highest risk areas, since they can look fine at first but break under normal use.
Nice update, especially the onboarding and system changes.
If I was testing this, I’d focus on:
The login and caching changes feel like the kind of thing that can look fine at first but break in edge cases.
This is a strong regression-risk update, especially because it touches combat behaviour, UI clarity, save reliability, and selection logic at the same time.
The areas I’d be most interested in re-checking are:
The save fixes are the big one for me. Anything involving persistence usually needs direct checks plus side-effect checks, because “fixed save issue” can quietly break something nearby if the state handling changed.
Big update. The hotfix chain alone shows how much surface area changed here.
From a QA point of view, the highest-risk areas look like:
This is exactly the kind of update where I’d want a regression matrix split into direct checks and side-effect checks, rather than trying to retest everything blindly.
Nice optimisation gains, especially on load times.
When changes like this touch memory and loading, it’s usually worth re-checking things like:
These kinds of improvements can sometimes introduce subtle issues even when the main metrics look solid.
