Skip to content

Presets And Default Config

A preset is a reusable bundle of config files, plugin selections, and factory file selections. Use presets to spin up new instances with a consistent starting point, or to save a working setup so you can replicate it later.

What A Preset Contains

  • server.cfg
  • mappool.txt
  • access.txt
  • workshop.txt
  • Any custom flat .cfg or .txt config files you add
  • Plugin files under the preset's plugin tree, including .py, .txt, and .so
  • Factory files under the preset's factory set
  • A set of selected minqlx plugins (checkboxes, not a raw qlx_plugins string)
  • A set of selected factory files

Built-in Presets

QLSM ships a set of built-in presets that provide ready-to-use baselines. Built-in presets cannot be modified, renamed, or deleted — they are read-only. The Update Preset button is hidden when a built-in preset is loaded, and the Load Preset picker does not show a delete option for them.

The default preset is always available as the standard baseline. Additional built-in presets may appear in the list depending on your QLSM version.

To customize a built-in preset, load it and use Save As New to create your own editable copy.

Use Save as Preset or Save As New when you want to turn the current draft into a reusable preset.

Use Load Preset any time you want to replace the default draft with one of your saved configurations.

Plugin and Factory Selection

Instead of editing qlx_plugins manually, presets use checkboxes. Check the plugins you want; uncheck the ones you don't.

The same applies to factory files — select the factories that should be included when this preset is deployed.

This means you can have completely different plugin and factory sets per instance. Two instances on the same host can each have their own independent selection.

The saved preset keeps both the files and the selection state. A plugin or factory file can exist in the preset without being selected for deployment. When you deploy from that preset, only selected plugins and selected factories are applied.

Load A Saved Preset

Use Load Preset in the deploy form or in Edit Config to open the preset picker.

Loading a preset overwrites the current draft with the saved config files, plugin file tree, plugin selections, factory files, and factory selections.

  • Built-in presets (e.g., default) are always available and cannot be deleted.
  • User-created presets can be deleted from this modal.

Custom Preset Workflow

  1. Open Deploy New Instance (or Edit Config on an existing instance).
  2. Adjust config files, plugin files, plugin selections, factory files, and factory selections for your gamemode.
  3. Click Save as Preset or Save As New and give it a name.
  4. On future deployments, click Load Preset and select your saved preset.

Update A Loaded Preset

If you load a user-created preset and then change the draft, the form exposes an Update Preset button.

Use Update Preset to overwrite the saved preset with your current draft.

  • The button stays disabled (greyed out) until the loaded preset has unsaved changes.
  • The Update Preset button is not shown at all for built-in presets — they cannot be modified.
  • Use Save As New to create your own editable copy of any preset, including built-ins.

Instance-Specific Ownership

A preset is only input at deploy time. After the instance is created, it keeps its own independent file set.

  • Editing an instance's config later affects only that instance.
  • Editing an instance's plugin or factory files later affects only that instance.
  • Other instances are not affected.
  • The original preset files are not modified.