Skip to content

preserve custom player wing arrival cues - #7716

Draft
Goober5000 wants to merge 1 commit into
scp-fs2open:masterfrom
Goober5000:enhancement/player_wing_waves
Draft

preserve custom player wing arrival cues#7716
Goober5000 wants to merge 1 commit into
scp-fs2open:masterfrom
Goober5000:enhancement/player_wing_waves

Conversation

@Goober5000

Copy link
Copy Markdown
Contributor

FRED and qtFRED no longer overwrite a hand-edited arrival cue on the wing containing the player start. The cue is editable when the wing has multiple waves (where it governs the arrival of subsequent waves) and read-only otherwise. Waves and threshold are now editable for the single-player player wing, while the arrival delay remains locked; the arrival location is editable in both editors.

Both error checkers flag a single-wave player wing with a custom cue as a potential issue, and the engine now warns and aborts the mission load, rather than tripping an Assert, if the player start ship was not created at mission start.

Also fix an unguarded read of Ships[Player_start_shipnum] in both editors.

Fixes #7160. In draft pending testing.

@Goober5000 Goober5000 added this to the Release 26.2 milestone Aug 17, 2026
@Goober5000 Goober5000 added enhancement A new feature or upgrade of an existing feature to add additional functionality. qtfred A feature or issue related to qtFred. fred A feature or issue related to the FReespace EDitor (FRED) labels Aug 17, 2026
@github-project-automation github-project-automation Bot moved this to Work In Progress (PRs) in qtFRED2 Aug 17, 2026
@Goober5000
Goober5000 force-pushed the enhancement/player_wing_waves branch from 94e5990 to 9c1c7dd Compare August 17, 2026 02:22
FRED and qtFRED no longer overwrite a hand-edited arrival cue on the wing
containing the player start.  The cue is editable when the wing has multiple
waves (where it governs the arrival of subsequent waves) and read-only
otherwise.  Waves and threshold are now editable for the single-player
player wing, while the arrival delay remains locked; the arrival location
is editable in both editors.

Both error checkers flag a single-wave player wing with a custom cue as a
potential issue, and the engine now warns and aborts the mission load,
rather than tripping an Assert, if the player start ship was not created
at mission start.

Also fix an unguarded read of Ships[Player_start_shipnum] in both editors.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@Goober5000
Goober5000 force-pushed the enhancement/player_wing_waves branch from 9c1c7dd to b774d9b Compare August 17, 2026 02:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement A new feature or upgrade of an existing feature to add additional functionality. fred A feature or issue related to the FReespace EDitor (FRED) qtfred A feature or issue related to qtFred.

Projects

Status: Work In Progress (PRs)

Development

Successfully merging this pull request may close these issues.

Bug? FR? Don't reset player wing arrival data on FRED save

1 participant