[GH-ISSUE #3749] [BUG] q3server does not cycle maps by default #2468

New issue

Closed

opened 2026-02-27 03:03:10 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 03:03:10 +03:00

Owner

Originally created by @kvnvallis on GitHub (Jan 14, 2022).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3749

User Story

I installed the quake 3 server and found that it does not cycle through maps at the end of each round. Instead it loads the same map over and over again.

Basic info

Distro: Ubuntu 20.04.3 LTS
Game: Quake 3 Arena
LinuxGSM version: v21.5.0

Further Information

I was able to fix this by:

adding vstr m1 at the end of q3server.cfg
moving the +map option before the +exec option in startparameters

The map cycle is already defined in q3server.cfg but the vstr m1 line is needed to actually run it. Modifying the startparameters is also required, otherwise +map ${defaultmap} will override the map cycle from q3server.cfg. It looks like these files exist in two different repositories.

serverfiles/baseq3/q3server.cfg
lgsm/config-default/config-lgsm/q3server/_default.cfg

I ran the server with the following startparameters and I can confirm that servercfg takes precedence over defaultmap. The map cycle will begin if it is configured correctly in q3server.cfg, but if not then the defaultmap will still load as specified.

startparameters="+set sv_punkbuster 0 +set fs_basepath ${serverfiles} +set dedicated 2 +set com_hunkMegs 32 +set net_ip ${ip} +set net_port ${port} +map ${defaultmap} +exec ${servercfg}"

Last two lines of my q3server.cfg:

//Begin the map cycle at m1
vstr m1

To Reproduce

Install q3server and start it with the default settings, or set timelimit 1 in the config so the round ends quickly

Expected behaviour

The server should load a new map at the end of each round.

Originally created by @kvnvallis on GitHub (Jan 14, 2022). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3749 ## User Story I installed the quake 3 server and found that it does not cycle through maps at the end of each round. Instead it loads the same map over and over again. ## Basic info * **Distro:** Ubuntu 20.04.3 LTS * **Game:** Quake 3 Arena * **LinuxGSM version:** v21.5.0 ## Further Information I was able to fix this by: - adding `vstr m1` at the end of _q3server.cfg_ - moving the _+map_ option before the _+exec_ option in _startparameters_ The map cycle is already defined in _q3server.cfg_ but the _vstr m1_ line is needed to actually run it. Modifying the startparameters is also required, otherwise _+map ${defaultmap}_ will override the map cycle from _q3server.cfg_. It looks like these files exist in two different repositories. - serverfiles/baseq3/q3server.cfg - lgsm/config-default/config-lgsm/q3server/_default.cfg I ran the server with the following _startparameters_ and I can confirm that _servercfg_ takes precedence over _defaultmap_. The map cycle will begin if it is configured correctly in _q3server.cfg_, but if not then the _defaultmap_ will still load as specified. startparameters="+set sv_punkbuster 0 +set fs_basepath ${serverfiles} +set dedicated 2 +set com_hunkMegs 32 +set net_ip ${ip} +set net_port ${port} +map ${defaultmap} +exec ${servercfg}" Last two lines of my _q3server.cfg_: //Begin the map cycle at m1 vstr m1 ## To Reproduce Install q3server and start it with the default settings, or `set timelimit 1` in the config so the round ends quickly ## Expected behaviour The server should load a new map at the end of each round.

kerem

2026-02-27 03:03:10 +03:00

closed this issue
added the
distro: Ubuntu

command: install

command: start
labels

kerem commented

2026-02-27 03:03:11 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Nov 26, 2023):

Already added the maprotation fix. Will update the parameters for next release

@dgibbs64 commented on GitHub (Nov 26, 2023): Already added the maprotation fix. Will update the parameters for next release

kerem commented

2026-02-27 03:03:11 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 16, 2024):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Dec 16, 2024): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

kerem referenced this issue

2026-02-27 03:55:21 +03:00

[PR #2468] [MERGED] fix(doiserver): now requires maxplayers to be set to 32 #3663

kerem referenced this issue

2026-02-27 03:55:22 +03:00

[PR #2491] [MERGED] Release/v19.10.0 #3670