Zandronum Chat @
Get the latest version: 3.0
Source Code

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0003383Zandronum[All Projects] Bugpublic2018-02-23 07:442018-02-23 07:44
Assigned To 
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: [^]
Attached Files

- Relationships

-  Notes
There are no notes attached to this issue.

Issue Community Support
Only registered users can voice their support. Click here to register, or here to log in.
Supporters: No one explicitly supports this issue yet.
Opponents: No one explicitly opposes this issue yet.

- Issue History
Date Modified Username Field Change
2018-02-23 07:44 Zalewa New Issue

Questions or other issues? Contact Us.


Copyright © 2000 - 2019 MantisBT Team
Powered by Mantis Bugtracker