Quick Start

This guide gets you from "plugin installed" to "level using the override game mode" in under a minute.

1. Install the plugin

1. Drop the QuickGameModeOverride folder into <Project>/Plugins/.
2. Regenerate project files and build.
3. Launch the editor. Confirm the plugin is enabled under Edit → Plugins → Other → Quick Game Mode Override.

2. Find the toolbar widget

The plugin adds a widget to the level editor toolbar's User section — the right-hand portion of the toolbar where editor extensions live. The widget contains:

• An Override Game Mode checkbox.
• A class picker filtered to GameModeBase subclasses.

If you don't see it, restart the editor — the widget is registered during editor subsystem initialization.

3. Override a level's game mode

1. Tick Override Game Mode.
2. Click the class picker and choose any GameModeBase subclass (engine, project, or plugin classes all show up — the picker uses the same filter as the World Settings field).
3. Press Play.

The level's WorldSettings.DefaultGameMode is swapped for the chosen class while the editor session runs. When you stop PIE, the original game mode is restored automatically.

The toolbar widget collapses while PIE is running and reappears when PIE ends — don't worry about losing it during play.

4. Turn it off

Untick the checkbox. The override stops applying immediately for any new PIE session.

You can also clear the class — set the picker to None — which disables the override even if the checkbox is still ticked.

What the override actually does

On every world initialization the plugin reaches into the world's AWorldSettings and replaces DefaultGameMode with your chosen class. This is the same field you'd be editing in World Settings → GameMode Override, except it's a single project-wide value applied to every level instead of a per-level edit.

That means:

• Your authored World Settings are not modified — only the live world is patched.
• The override applies to every level. There's no per-level allowlist.
• The override is editor-only. It runs in PIE and editor sessions only — packaged / standalone builds always use the level's authored game mode regardless of what's in the config file. You don't need to remember to "turn it off before shipping."

Where next

• Toolbar — full reference for the toolbar widget and what it controls.
• Settings — the config file, where values persist, and how to edit them outside the toolbar.
• C++ API — for projects that want to read or modify the override from code.