MantisBT - Zandronum
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0003383Zandronum[All Projects] Bugpublic2018-02-23 07:442025-10-12 03:39
ReporterZalewa 
Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformMicrosoftOSWindowsOS VersionXP/Vista/7
Product Version3.1 
Target VersionFixed in Version 
Summary0003383: +compatflags[2] command line options broken in 3.1-alpha
DescriptionCompatflags cannot be any longer set from command line when starting the server if game's config exists. This happens when either the main Zandronum config is used or when a custom config is specified with "-config" argument.
Steps To Reproduce1. Compile commit from "Additional Information" or a newer one like c11f78a.

Variant A:

1. Game config must pre-exist.
2. "zandronum.exe -host -iwad doom2.wad +compatflags 5 +compatflags2 10"
3. Use the server console to check both compatflags and they'll both be zero.

Variant B:

1. "server.cfg" cannot exist.
2. "zandronum.exe -host -config server.cfg -iwad doom2.wad +compatflags 5 +compatflags2 10"
3. Both compatflags will be set correctly.
4. Close the server.
5. Restart the server with the same command line.
6. Both compatflags will be zero now.

Variant C:

Do either A or B but put compatflags options in a what.cfg file and in the command line do "+exec what.cfg".
Additional InformationBroken in this commit:'https://bitbucket.org/Torr_Samaho/zandronum/commits/60c3414752768543616e3b35e804776e28839c18 [^]'
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2018-02-23 07:44ZalewaNew Issue
2025-10-12 03:39Ru5tK1ngNote Added: 0024579
2025-10-12 03:39Ru5tK1ngStatusnew => resolved
2025-10-12 03:39Ru5tK1ngResolutionopen => fixed

Notes
(0024579)
Ru5tK1ng   
2025-10-12 03:39   
Doesn't seem to be an issue in 3.2.1. You should be using -exec and not -config for custom server setting cfg files.