Skip to content

Manage source ports

Jump to bottom
Mikkel Rask edited this page May 13, 2026 · 3 revisions

As of vE1M0.3.1, you can configure multiple source ports (different engines or different versions of the same engine) and pick which one to use per game instance.

Accessing source ports

Click the cog icon in the top navigation → core_settings → Paths tab. The Source Ports section is at the top under CORE INFRASTRUCTURE.

Adding a source port

  1. Click + Add Port.

  2. A file picker opens — select your source port executable (binary, AppImage, or .exe).

  3. An inline form appears where you can set:

    Field Description
    Name Human-readable label, auto-filled from filename.
    Version Optional version string (e.g. 4.12.2).
    Executable Path Full path to the binary — can be typed or browsed with the folder icon.
    Family Engine variant used for modpack import matching (see below).

  4. Click Save.

Families

Family is auto-detected from the filename but can be changed manually. Used when importing modpacks to match the old sourcePort string against your configured ports.

Family Typical engines
uzdoom UZDoom (default/recommended)
gzdoom GZDoom
zdoom ZDoom (legacy)
zandronum Zandronum (multiplayer)
lzdoom LZDoom (legacy hardware)
other PrBoom+, Odamex, Eternity Engine, DSDA-Doom, etc.

Setting a default

Each port has a radio dot on the left — click it to set that port as the default. The default is used when a game instance has no specific port assigned, or when an imported modpack can't be matched to any port.

Ignoring (hiding) ports

Click the eye icon to toggle visibility in game instance selectors. Hidden ports remain in your config but won't appear in the combobox dropdown.

Editing and deleting

  • Pencil icon — opens the inline form pre-filled with current values.
  • Trash icon — removes the port. If you delete the default, the first remaining non-ignored port becomes the new default. Game instances referencing a deleted port fall back to the default.

Using ports in game instances

When installing or editing a game instance, the Source Port field is a filterable combobox showing only non-ignored ports (name, family badge, version). No free-text entry — you must pick from the list.

Importing modpacks

When importing a .uac-modpack file, the app matches the old sourcePort string against your configured ports by:

  1. Exact name match (case-insensitive)
  2. Partial match against name/family
  3. Falls back to the default port

Migration from vE1M0.3.0 and earlier

On first launch after updating, the old single sourcePortPath is automatically converted into a port entry named "Default (migrated)" with family auto-detected and set as default. Old mod files using the legacy sourcePort string are backfilled to sourcePortId. Your original path is preserved throughout.

Fallback chain

When launching a game, the executable is resolved in this order:

  1. The port referenced by the game instance (sourcePortId)
  2. The default port (defaultSourcePortId)
  3. The first non-ignored port in the list
  4. Error — if no ports are configured, you'll be prompted to add one.

Troubleshooting

Problem Likely cause Solution
"No source ports configured" on launch No ports in the list Add at least one source port in Settings → Paths
Game launches with the wrong engine Game instance has a different port selected Edit the instance and check the Source Port selector
Combobox is empty All ports hidden or none configured Check eye icons in Settings → Paths
Can't find old port after updating Migration only runs once Look for a port named "Default (migrated)" in Settings → Paths

Clone this wiki locally