Add Hardcore Mode with Save/Load Restrictions

[chaserli]

Description

Adds a Hardcore Mode for campaign missions.

When enabled, Hardcore Mode prevents the player from saving or loading the game during a mission, and changes the mission flow to better fit a no-save challenge.

Features

• Disables Save, Load, and Delete Game during the mission.

• Replaces the normal mission failure prompt with a Hardcore-specific Retry / Leave prompt.

• Displays a Hardcore indicator on the loading screen.

  • Uses hardcorelogo.shp when available.
  • Falls back to the TXT_HARDCORE_MODE CSF string.

• Updates the mission end dialog to use an appropriate exit option.

• Forces campaign scenarios using Hardcore Mode to end the game normally instead of allowing them to continue through the regular save/load flow.

Configuration

Enable Hardcore Mode with:

[Settings]
DisableSaveLoad=true

in spawn.ini

Additional CSF strings can be provided for localization:

TXT_HARDCORE_MODE
TXT_HARDCORE_FAILURE
GUI:CantSave
GUI:CantLoad

[github-actions]

Nightly build for this pull request:

• spawner-CnCNetYR-bf8cbeb504b718ecca723451fcf3183a8b56478b.zip
• spawner-bf8cbeb504b718ecca723451fcf3183a8b56478b.zip
  These artifacts will expire in 90 days and will not be available for download after that time.

This comment is automatic and is meant to allow guests to get latest nightly builds for this pull request without registering. It is updated on every successful build.

[Belonit]

I'm not sure that spawner should introduce such features. Perhaps this should be in Phobos?
@Metadorius Any thoughts?

[chaserli]

I'm not sure that spawner should introduce such features. Perhaps this should be in Phobos?

This is similar to the existing “Custom Mission” feature. It is originally designed around one game session launching one mission, then the mission ends and the session ends.

This also comes with the same constraints. For example, implementing it requires hard-patching certain addresses, which can break if the game proceeds to another mission. Putting the UI toggles in the vanilla launcher is both difficult, inappropriate, and unnecessary. RA2MD.ini is not the right place for this either, etc.

In Spawner, however, it fits naturally through spawn.ini, works seamlessly with the DTA client. The spawner skips the cumbersome procedures before starting the mission, which could avoid those shitty ass problems.

It also complements the " Custom Mission " feature a bit.

FYI original PR in Phobos Phobos-developers/Phobos#1402