Thank you for all the reports and feedback since the Diplomacy Expansion launched. This hotfix addresses the most important issues you reported in the first days: older saves, getting stuck, ship and camera problems. It also brings a few requested options and clearer explanations.
FIXES & IMPROVEMENTS
Saves & factions
- Fixed older saves losing the player's capital and captured systems when loaded in 3.0.0. Saves that were already affected recover those systems, where possible, the first time they are loaded.
- Fixed Houses in older saves staying in wars that had already ended and building up war exhaustion while at peace.
- When a war with you ends, that house's relation with you now starts at -50 at most and recovers over 10 in-game days. Your trade agreements with them stay in place during this time.
- Fixed house rows on the Operations page not responding after the list was sorted.
- Fixed renamed structures showing their old name in the Lords list.
Ships & combat
- Fixed large ships such as the Swarm Carrier clipping into the landing pad when summoned with Call Ship. They now arrive at the station's capital dock, or in open space nearby when the station has none.
- Fixed the camera leaving the cockpit or first-person view during warp. The camera now stays in the view you chose.
- Fixed your power distribution resetting when Squad Boost or Offensive ends.
- Fixed the thruster bar sometimes not updating.
- Fixed the old launcher or Misactor tool disappearing when a new one was equipped in its place. It now goes back to your inventory.
- Fixed the Add Level button in the faction hangar showing the wrong level count.
- The base price of the Mother Earth is now locked the first time it is offered in a ship market, so it no longer rises as you level up. It is also 5% cheaper.
- "I Got Stuck" now also helps while you are piloting a ship: it moves your ship to the nearest open space. It does not apply while landed or docked.
Stations & interface
- Fixed the Ship Manager terminal not opening again after its first use until the save was reloaded.
- Fixed the Explorer search finding the wrong system when searching by system number. An exact number match now comes first.
- Fixed loading a save on Falron Station sometimes placing your character inside the station's walls.
- Fixed the news ticker getting stuck on screen after a news item.
- The Dungeon Records page now shows "No Dungeon Records Found" when it is empty.
Quests
- Fixed story missions after the Council, and some side missions, not awarding XP. A mission already in progress in an older save awards XP when you complete it.
- Fixed the Clean-Up tutorial mission getting stuck at some steps with saving and warping disabled.
Options
- New setting: Head Bobbing (Settings → Interface). Turn it off for a steadier on-foot camera. It is on by default.
New explanations
- How much Dominance the next castle needs, and how to raise it.
- System policies stay in effect while they are active (they are not one-time).
- Your faction builds one station at a time.
- Clearer stargate route messages.
- The Treasury cannot be withdrawn to your own money.
Texts & translations
- Shortened some texts on the Relations page so they fit on screen.
- Fixed crew perk descriptions appearing in English in other languages.
- Fixed typos: "Set As Operation Target" and "OX-11 Mining Station".
- Translations for all 13 languages have been updated, including the new explanations and corrected texts.
IMPORTANT NOTE: TITAN
The Titan was made available in 3.0.0 by mistake, through ship markets and the Ship Manager console. It was never meant to be obtainable and does not work correctly in the game.
With 3.0.1, the Titan has been removed from ship markets and the Ship Manager console. Any Titan already in your fleet is removed when you load your save. We're sorry for the confusion, and thank you to everyone who reported it.
Thank you for your reports and your patience. Please keep them coming on Discord and the Steam forums.
See you in space.
Note: The version under the main menu still shows 3.0.0. This is only a display error, and we'll fix it in the next update. Sorry for the confusion.
