ql-lg-server: Quake Live LG vampiric practice server in Docker
One-command setup (SteamCMD + minqlx build), .env settings with a listed/unlisted switch, three factories (lgvamp, lgvamp_nolag, lgvamp100), warmup-text and welcome minqlx plugins, watchdog/backup/daily-restart, docs for admins and players. Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
commit
bc5bd09c15
25 files changed
+1009
No files matched your search
@@ -0,0 +1,35 @@
|
||||
# ql-lg-server settings. setup.sh copies this to .env (and asks for the important ones).
|
||||
# After editing .env: docker compose up -d (recreates the container with the new values)
|
||||
# No double quotes inside values.
|
||||
|
||||
# Name shown in the server browser and the scoreboard (^1..^7 = Quake colors)
|
||||
QL_HOSTNAME=LG Vampiric FFA
|
||||
|
||||
# yes = listed in the in-game server browser (forward UDP QL_PORT on your router/firewall)
|
||||
# no = unlisted, people join by address (LAN, VPN like Tailscale, or a known IP)
|
||||
QL_LISTED=yes
|
||||
|
||||
# Join password (empty = open server)
|
||||
QL_PASSWORD=
|
||||
|
||||
QL_MAXCLIENTS=16
|
||||
|
||||
# lgvamp LG only, 1:1 vampiric, no knockback, antilag (like x76 "Antilag LG Duel")
|
||||
# lgvamp_nolag same without antilag (like x76 "LG Duel EU #3")
|
||||
# lgvamp100 spawn with flat 100 HP instead of 200 (no health decay above 100)
|
||||
QL_FACTORY=lgvamp
|
||||
QL_MAP=thunderstruck
|
||||
|
||||
# Shown to every player when they join. Empty = no message.
|
||||
QL_WELCOME=^7Welcome! LG only, vampiric, no knockback. Pair up and duel, there is no match to ready up for.
|
||||
|
||||
# Game port (UDP) and RCON port (TCP, bound to 127.0.0.1 only). Change both to run a second server.
|
||||
QL_PORT=27960
|
||||
QL_RCON_PORT=28960
|
||||
|
||||
# Docker container name (unique per server on this machine)
|
||||
QL_NAME=ql-lg
|
||||
|
||||
# User/group the server runs as (owner of this folder). setup.sh fills these in.
|
||||
QL_UID=1000
|
||||
QL_GID=1000
|
||||
Reference in new issue
Block a user