Anonymous | Login | Signup for a new account | 2025-10-15 19:02 UTC | ![]() |
My View | View Issues | Change Log | Roadmap | Zandronum Issue Support Ranking | Rules | My Account |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0003383 | Zandronum | [All Projects] Bug | public | 2018-02-23 07:44 | 2025-10-12 03:39 | ||||
Reporter | Zalewa | ||||||||
Assigned To | |||||||||
Priority | normal | Severity | major | Reproducibility | always | ||||
Status | resolved | Resolution | fixed | ||||||
Platform | Microsoft | OS | Windows | OS Version | XP/Vista/7 | ||||
Product Version | 3.1 | ||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0003383: +compatflags[2] command line options broken in 3.1-alpha | ||||||||
Description | Compatflags 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 Reproduce | 1. 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 Information | Broken in this commit:'https://bitbucket.org/Torr_Samaho/zandronum/commits/60c3414752768543616e3b35e804776e28839c18 [^]' | ||||||||
Attached Files | |||||||||
![]() |
|
Ru5tK1ng (updater) 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. |
This issue is already marked as resolved. If you feel that is not the case, please reopen it and explain why. |
|
Supporters: | No one explicitly supports this issue yet. |
Opponents: | No one explicitly opposes this issue yet. |
![]() |
|||
Date Modified | Username | Field | Change |
2018-02-23 07:44 | Zalewa | New Issue | |
2025-10-12 03:39 | Ru5tK1ng | Note Added: 0024579 | |
2025-10-12 03:39 | Ru5tK1ng | Status | new => resolved |
2025-10-12 03:39 | Ru5tK1ng | Resolution | open => fixed |
Copyright © 2000 - 2025 MantisBT Team |