Skip to content

Fix standalone startup handling on macOS and add build instructions doc#873

Merged
TomWerner merged 1 commit intoC7-Game:Developmentfrom
mizuirorivi:mizuirorivi/fix/standalone-mode-screen-not-advancing
Feb 12, 2026
Merged

Fix standalone startup handling on macOS and add build instructions doc#873
TomWerner merged 1 commit intoC7-Game:Developmentfrom
mizuirorivi:mizuirorivi/fix/standalone-mode-screen-not-advancing

Conversation

@mizuirorivi
Copy link
Contributor

@mizuirorivi mizuirorivi commented Feb 11, 2026

basis

Fixes a standalone startup issue on macOS exports where the app could skip the mode-selection flow or fail to resolve C7-packaged assets correctly. This updates main menu initialization to avoid creating classic-only buttons before Civ3 assets are available, resolves C7 asset lookups relative to the export base directory, and adds a concise macOS build guide in doc/build.md.

@TomWerner
Copy link
Contributor

This is great, thank you for the contribution!

If you download the mac export from the CI run does that work? Or do we need to integrate some of the things from your mac build instructions into our CI?

@mizuirorivi
Copy link
Contributor Author

Thanks!
I tested this locally from a clean build and the standalone flow now works as expected on macOS (the mode-selection screen appears, and “Play in standalone mode” proceeds correctly).

For CI, I don’t think additional workflow changes are needed for this fix.
The macOS workflow already checks out submodules and appends Assets/Text/Lua into the zip artifact, which are the key requirements for this path fix.
I’ll also download the mac artifact from this PR run and confirm behavior there, then report back.

@TomWerner TomWerner merged commit a679b8b into C7-Game:Development Feb 12, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants