Again, please opt into the "Future" branch if you're brave enough to test out what we're working on (see HERE for how to opt-in). When it's had some time in there and you guys have deemed it "stable" I'll move it to the default branch (which everyone is on by default).
So the main reason for this version was to try yet another approach to upgrade breaking (we weren't happy with v0.23 for a variety of reason, the latest design thoughts are HERE, so I'd love people to play around with it and add feedback to that design thread or even below.
If you do find bugs that you believe might be specific to this version please post them in the Support/Issues/Bugs Sub-forum with "[v0.24]" at the beginning of the title.
(edit: also note that this includes all the updates/fixes from v0.23)
please let us know your thoughts/feedback on any of these things below!
- Reworked upgrade breaking for a second time: now mission based, visible “failure probability”, no increase if not used, will change states in diagnostic report after mission.
- Change: ‘destruct’ command requires confirmation
- Minor Change: Reworked mission summary window to be a little clearer
- Added: New option to enable running the game in the background (possible unstable)
- Added: Difficulty option to turn off drones being placed in very small/narrow rooms
- Added: Option to reset the previous Best Days Survived back to 0 (goes hand-in-hand with fix, so that previous Best Days values can be reset by player if they want clean data)
- Fix: Removed exploit where player could teleport into game and bypass the mission start logic
- Fix: Multiple issues with the Reroute Ship Upgrade to make more stable/reliable
- Fix: prevent SOME cases where the boarding ship doesn’t show after re-docking
- Fix: Previous Best Days Survived was an inflated number. This fixes FUTURE best plays, but is unable to correct the bad previous best days info currently stored in players’ data.
- Fix: Grey Goo objective step that requires all rooms in a Space Station to be scanned was mistakenly also requiring that the boarding ship be scanned, as well.
- Fix: Multiple “Internal Processing Errors”. These errors can happen in many ways, and this is not a comprehensive fix of all possible errors. Continue to report these along with the output log and command used.
- Minor Fix: Various typos, particularly in the tutorial
- Minor: New probe overlay more of a programmer smiley face :)
Thanks!
-Tim (Duskers creator guy)