Dedicated server guide

Medal of Honor: Allied Assault

Manage mohaaserver with AlphaGSM. Choose a runtime supported by the recorded module capabilities.

Operator-provided prerequisites required · Support evidence: 2026-10-16.

Build setup commands

Runtime familyquake-linux

Declared runtimes: Docker or a Linux host process.

Network bindings

12203/UDP. Named port values remain unknown; review the game guide and configuration for additional requirements.

Mods and plugins

No mod support is declared in this snapshot; review the game guide before adding mods.

Backup hook

A module-specific backup hook is declared. Review the game guide for its scope, restore procedure and shutdown requirements.

Choose a supported runtime

Linux and Docker quickstart

Operator-provided game files, runtime or other prerequisites are required; follow the game guide before setup.

Docker

Complete interactive setup and review game-specific configuration before starting the server. Operator-provided game files, runtime or other prerequisites are required; follow the game guide before setup.

Start the Docker manager ./alphagsm-docker start
Create the game instance ./alphagsm-docker my-mohaaserver create mohaaserver
Complete interactive setup ./alphagsm-docker my-mohaaserver setup
Start the game server ./alphagsm-docker my-mohaaserver start
Check the instance status ./alphagsm-docker my-mohaaserver status

./alphagsm-docker start
./alphagsm-docker my-mohaaserver create mohaaserver
./alphagsm-docker my-mohaaserver setup
./alphagsm-docker my-mohaaserver start
./alphagsm-docker my-mohaaserver status

Host process

Create the game instance ./alphagsm my-mohaaserver create mohaaserver
Complete interactive setup ./alphagsm my-mohaaserver setup
Check the host prerequisites ./alphagsm my-mohaaserver doctor
Start the game server ./alphagsm my-mohaaserver start
Check the instance status ./alphagsm my-mohaaserver status

./alphagsm my-mohaaserver create mohaaserver
./alphagsm my-mohaaserver setup
./alphagsm my-mohaaserver doctor
./alphagsm my-mohaaserver start
./alphagsm my-mohaaserver status

This guide covers the mohaaserver module in AlphaGSM.

mohaaserver is currently ENABLED (BYO) on the documented Ubuntu 24.04 Linux baseline. The current GitHub integration lane still exercises both process and Docker runtime selection around that owned-dedicated-tree prerequisite, while local runs remain process-backed by default unless you opt into the Docker backend.

Requirements

screen
an owned Medal of Honor: Allied Assault dedicated-server tree
32-bit runtime compatibility for the original server binary

Quick Start

alphagsm mymohaa create mohaaserver
alphagsm mymohaa setup
alphagsm mymohaa start
alphagsm mymohaa status
alphagsm mymohaa stop

mohaaserver is supported in ENABLED (BYO) mode. Before setup or start, copy an owned MOHAA dedicated server tree into your chosen <install_dir>/ so <install_dir>/mohaa_lnxded exists.

Suggested flow:

alphagsm mymohaa create mohaaserver
alphagsm mymohaa setup -n 12203 /path/to/mohaaserver
## copy the owned MOHAA dedicated server files into /path/to/mohaaserver/
alphagsm mymohaa start

Notes

Module name: mohaaserver
Install mode: ENABLED (BYO) server files
Default port: 12203
Query/info protocol: Quake III UDP getstatus (quake) on the game port.
Executable: ./mohaa_lnxded

Server variables

After create mohaaserver, inspect or change these with set:

alphagsm myserver set --list
alphagsm myserver set KEY --describe
alphagsm myserver set KEY VALUE

This module does not declare schema-backed keys. set --list after create is still the live source of truth.

Developer Notes

AlphaGSM follows LinuxGSM's launch defaults for mohaa_lnxded, including fs_basepath, fs_outputpath, dedicated 2, net_ip, net_port, the default map dm/mohdm1, and +exec main/<server-name>.cfg.
OpenMoHAA and the retail mohaa_lnxded binary answer Quake III UDP getstatus with statusResponse on net_port, so query and info use protocol quake.
Automated install is not provided because no authoritative LinuxGSM-backed download path was identified for this legacy server.

BYO file helper

Inspect this game's required files, source instructions and destinations with alphagsm <server-name> assets requirements; check the declared files with alphagsm <server-name> assets check. File checks do not establish game readiness. This helper checks known sentinels only and directs you to stage the complete compatible distribution manually; managed import is unavailable for this recipe. See BYO files and private SteamCMD acquisition.

Share your server

Sector Alpha server directory

When your server is ready, you can publish its connection details and community information on Sector Alpha. Review your listing and keep the information current.

Find a community

Browse the directory for game servers and their published connection details.

Browse server directory

Publish your server

Prepare a name, address and description for your listing.

Publish a server

Manual server sharing instructions

Frequently asked questions

What support evidence is recorded for Medal of Honor: Allied Assault?

Operator-provided prerequisites required. Operator-provided game files, runtime or other prerequisites are required; follow the game guide before setup.

Which runtimes can run Medal of Honor: Allied Assault?

Declared runtimes: Docker or a Linux host process.

Which ports does Medal of Honor: Allied Assault use?

12203/UDP. Named port values remain unknown; review the game guide and configuration for additional requirements.

Can I add mods to Medal of Honor: Allied Assault?

No mod support is declared in this snapshot; review the game guide before adding mods.

How should I back up Medal of Honor: Allied Assault?

A module-specific backup hook is declared. Review the game guide for its scope, restore procedure and shutdown requirements.

Source and support evidence

This guide mirrors AlphaGSM’s upstream documentation at 32cef5ba9e03053c8e461fffa0ba133b160b528d. Commands and prerequisites can change. Check current support notes before installation.

All game guides