You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The escorts given to the player in FWC Checkmate Escorts stop being hostile to the Pug after the Pug stop attacking them after FWC Pug 1, but do not then become hostile to the Pug again when the player attacks a Pug ship in FWC Pug 2D, meaning they do not attack Pug ships during FWC Pug 3A.
Steps to Reproduce
Complete FWC Pug 1 with some of the escorts from that mission alive (this is difficult)
Continue the missions until you are sent back to Pug space
Observe that your FW escort fleet is not hostile to the Pug, and instead sits around watching as you die.
This could be easily fixed by changing the government of the fleet in "FWC Checkmate Escorts" to Escort rather than Free Worlds, and the swizzle would still be correct.
The text was updated successfully, but these errors were encountered:
Amazinite
added
content
A suggestion for new content that doesn't require code changes
and removed
bug
Something in the game is not behaving as intended
labels
Jan 28, 2024
It was noted in #4303 that it's actually intentional that the Free Worlds become non-hostile to the Pug. An event runs in FWC Pug 1B is finished, "fwc pug peaceful", which makes it clear that the intention is for the Free Worlds to not attack the Pug at this point. The Free Worlds then become hostile again once the next big battle with the Pug starts in FWC Pug 3B. Between these two points, your task is to get a jump drive from the Pug to inform the Free Worlds about what is going on.
Given that your task is to get a jump drive, which requires you to disable a ship and board it, having the FW fleet attack Pug ships alongside you could actually make it more difficult to get your hands on a jump drive, as the weaponry on the FW fleet is more prone to accidentally destroying a disabled ship. So that begs the question of whether we actually want the FW fleet that is with you to attack the Pug with you.
meaning they do not attack Pug ships during FWC Pug 3A.
For what reason would they attack the Pug at that point? FWC Pug 3B is a battle with the Pug. If the limited fleet that you have started attacking the Pug before that point, you could just be shooting yourself in the foot for the big battle to come.
Is there an existing issue for this?
Describe the bug
The escorts given to the player in FWC Checkmate Escorts stop being hostile to the Pug after the Pug stop attacking them after FWC Pug 1, but do not then become hostile to the Pug again when the player attacks a Pug ship in FWC Pug 2D, meaning they do not attack Pug ships during FWC Pug 3A.
Steps to Reproduce
Complete FWC Pug 1 with some of the escorts from that mission alive (this is difficult)
Continue the missions until you are sent back to Pug space
Observe that your FW escort fleet is not hostile to the Pug, and instead sits around watching as you die.
Expected Behavior
The FW fleet should attack the Pug.
Screenshots
No response
Link to save file
William Nucleararmament.txt
Operating System
Windows 10
Game Source
Other (please describe)
Game Version
PR #8670
Additional Information
This could be easily fixed by changing the government of the fleet in "FWC Checkmate Escorts" to Escort rather than Free Worlds, and the swizzle would still be correct.
The text was updated successfully, but these errors were encountered: