Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make CampaignID default to -1, with an optional override #538

Merged
merged 1 commit into from
Mar 20, 2024

Conversation

Rampastring
Copy link
Member

Different parsing of duplicate entries in Battle.ini between the client and the game (Tiberian Sun) has led to the game crashing as the game sees duplicate entries as one entry, while the client sees them as separate entries. Separate entries are often used by modders to add separators to the mission list.

The game is not known to really use the campaign ID for much (only the "do you need GDI/Nod/Firestorm CD" check is known), so setting it to -1 by default should do little harm. In case it does, there is now the possibility to manually override the campaign ID.

-1 is interpreted by the game as CAMPAIGN_NONE, which allows playing with any CD.

This would also affect the game's "final campaign movie" logic (FinalMovie= in Battle.ini), but as far as I know, no distribution of TS, vanilla or modded, makes use of that logic.

Different parsing of duplicate entries in Battle.ini between the client and the game has led to the game crashing
as the game sees duplicate entries as one entry, while the client sees them as separate entries.
Separate entries are often used by modders to add separators to the mission list.

The game is not known to really use the campaign ID for much (only the "do you need GDI/Nod/Firestorm CD" check is known),
so setting it to -1 by default should do little harm.
In case it does, there is now the possibility to manually override the campaign ID.
Copy link

Nightly build for this pull request:

@Rampastring Rampastring merged commit 918a397 into develop Mar 20, 2024
3 checks passed
@SadPencil SadPencil deleted the campaignid-default-minusone branch March 22, 2024 10:11
SadPencil pushed a commit to SadPencil/xna-cncnet-client that referenced this pull request Oct 4, 2024
Different parsing of duplicate entries in Battle.ini between the client and the game has led to the game crashing
as the game sees duplicate entries as one entry, while the client sees them as separate entries.
Separate entries are often used by modders to add separators to the mission list.

The game is not known to really use the campaign ID for much (only the "do you need GDI/Nod/Firestorm CD" check is known),
so setting it to -1 by default should do little harm.
In case it does, there is now the possibility to manually override the campaign ID.
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.

1 participant