Quick Game Mode Override

Quick Game Mode Override lets you swap the active game mode for any level without modifying the level asset on disk. You toggle it from a small widget in the level editor toolbar and pick a GameModeBase class to use instead. The override applies in PIE and editor sessions only — it never runs in packaged or standalone builds, by design.

Why this plugin exists

The traditional workflow for testing a different game mode is to open World Settings → GameMode Override on a level and change it. That edit modifies the level asset — and is trivially easy to commit to source control by accident.

Quick Game Mode Override sidesteps that entirely. The override lives in Config/DefaultQuickGameModeOverride.ini, not in the level asset, so nothing on disk inside your Content/ folder ever changes. Two practical wins:

• No accidental commits. You can't ship a level with the wrong default game mode because you forgot to revert World Settings.
• Cross-platform development. Different developers (or platforms, or branches) can run with different debug/test game modes by swapping a config file. The level asset stays canonical.

It's also faster — the override is one click in the toolbar — but that's the secondary benefit. The primary one is keeping the level asset clean.

Where to start

• Quick Start — install the plugin, find the toolbar widget, and override a level's game mode in under a minute.
• Toolbar — full reference for the toolbar widget and what each control does. The toolbar is the plugin's primary surface; this is the page most users want.
• API Reference — for projects that want to read or extend the override from code:
  • Editor API — the settings file format.
  • C++ API — internal subsystems and the settings UCLASS.

Compatibility

• Engine: Unreal Engine 5.7
• Platforms: Win64, Mac, Linux
• No required engine plugins.

Modules

What gets stored where

The override toggle and the chosen class persist in Config/DefaultQuickGameModeOverride.ini. The level asset is never touched. Add the config file to .gitignore to keep the override strictly per-developer, or commit it to share a baseline. Either way, your level files stay clean.