Modding

Quake Live modding is primarily server-side. The client is a fixed Steam binary. Server customization is done through factories (gametype rule files), minqlx plugins (Python), and server cvars.

minqlx

minqlx is the primary server-side plugin framework. It hooks into the Quake Live dedicated server and exposes a Python API for game events, player management, commands, and external integrations.

Source: minqlx on GitHub

Plugin capabilities

• Hook game events: player connect, disconnect, kill, round start/end, map change
• Add server commands prefixed with ! (configurable via qlx_commandPrefix)
• Integrate Redis for persistent player data (stats, permissions, preferences)
• Modify game state: force balance teams, set scores, change maps, kick players
• Build external integrations: Discord bots, stat trackers, Elo systems

Setup

minqlx is included in the quakelive-server-standards Docker images. For manual setup:

# Install to server root
python3 minqlx_setup.py
# Configure in server.cfg
qlx_pluginsPath "minqlx-plugins"
qlx_database    "Redis"
qlx_redisAddress "localhost"

Factories

Factories define gametype rules as JSON. Each .factories file contains one or more factory definitions. Placed in baseq3/scripts/.

Fields:

Factories control: timelimit, fraglimit, physics mode (VQL/PQL), item availability, spawn loadouts, and custom rules.

Map Pools

Map pools are defined in mappool.txt in the server root. One map name per line. The server rotates through this list. Standard competitive pools are maintained by quakelive-server-standards per gametype.

Physics Mode

Physics mode is set per-factory via the pmove_BunnyHop and related cvars:

VQL is standard for most competitive gametypes. PQL servers are available but less common.

Related

• Server Hosting: Docker setup, ports, RCON
• Console: server cvar reference