Skip to content

a few parsing and infrastructure upgrades - #7734

Draft
Goober5000 wants to merge 2 commits into
scp-fs2open:masterfrom
Goober5000:fix/ship_registry_rename
Draft

a few parsing and infrastructure upgrades#7734
Goober5000 wants to merge 2 commits into
scp-fs2open:masterfrom
Goober5000:fix/ship_registry_rename

Conversation

@Goober5000

Copy link
Copy Markdown
Contributor
  • A parse flag to indicate when the mission is being parsed, and a new ship_class_index() accessor in the ship registry, both currently unused
  • Make the ship registry more robust, especially in FRED: properly update it when ships are renamed or deleted

In draft as it depends on #7732

@Goober5000 Goober5000 added this to the Release 26.2 milestone Aug 23, 2026
@Goober5000 Goober5000 added fix A fix for bugs, not-a-bugs, and/or regressions. qtfred A feature or issue related to qtFred. fred A feature or issue related to the FReespace EDitor (FRED) labels Aug 23, 2026
@github-project-automation github-project-automation Bot moved this to Work In Progress (PRs) in qtFRED2 Aug 23, 2026
@Goober5000
Goober5000 force-pushed the fix/ship_registry_rename branch 2 times, most recently from bf4457d to 195cce8 Compare August 23, 2026 19:16
Following PR scp-fs2open#7429, ships belonging to wings were hashed the same way as every other ship, instead of the original hackish format where the hash was juggled around the number.  This was a mostly transparent upgrade, and ship names were automatically converted from the legacy format to the new format.  However, missions that referenced ships *in subsequent waves* broke; the converter only handled ships in the first wave.

This PR adds compatibility checks to `eval_ship` and `ship_registry_get` to accommodate legacy names.
- A parse flag to indicate when the mission is being parsed, and a new `ship_class_index()` accessor in the ship registry, both currently unused
- Make the ship registry more robust, especially in FRED: properly update it when ships are renamed or deleted
@Goober5000
Goober5000 force-pushed the fix/ship_registry_rename branch from 195cce8 to 7b99921 Compare August 23, 2026 20:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fix A fix for bugs, not-a-bugs, and/or regressions. 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.

1 participant