Skip to content

v0.10a

Choose a tag to compare

@github-actions github-actions released this 25 Jul 23:40

Feature Changes

  • NEW hull damage tracker. This panel shows a graph of how much hull damage from various sources was taken in each sector.
    • NOTE: If you are upgrading from a previous release, the Hull Damage panel may not be part of your saved window layout. You can right-click on an existing tab and choose Hull Damage from the "Add tab" menu to add it.
  • Sector names in the Game Info panel now use translations loaded from the FTL data instead of showing the internal name.
  • Ship names in the Game Info panel now use friendly names rather than the internal name.
  • The Scrap per Sector graph now shows shortened sector names on the X-axis once the sectors have been visited.

UI Enhancements

  • Added a button on the sidebar for the run tracker to give visual feedback if data is being recorded, and also to easily toggle it on or off before starting a run.
  • Added a confirmation dialog for trying to exit Subspace while a tracked run is in progress.
  • Added an in-game warning if a tracked run is in progress and communication is somehow lost with the main Subspace process. If you see red text in the corner, it's advisable to save and quit at the earliest safe place to avoid missing data.
  • Increased default window size to accommodate the hull damage graph and its legend.
  • Show a lock icon on the Run Tracker feature while a run is in progress to make it explicit that it can't be turned on or off while the game is running and a session is active.

Technical Updates

  • Fixed "Partial" compatibility with FTL 1.6.8 and 1.6.9; all known 1.6.x FTL versions should once again be "Full" compatibility.
  • Automatically re-check feature compatibility with FTL when Subspace is updated to a new version. This fixes issues with new features that are added not being available without re-picking the EXE.
  • Some FTL game data is now loaded in the background; currently just the translations for sector names but the frameworks is in place to load blueprints.
  • The database now also records elapsed unpaused game time at the current beacon for each event. This will be useful for future combat log analysis for weapon timing, etc.
  • Extensive internal changes to the way game events are handled.

This is still a work in progress!

The Run Summary and Sector Detail panels are not yet functional.
Configuration options for the run tracker are not yet implemented.