Page MenuHomeFeedback Tracker

server.cfg missionWhiteList doesn't work properly if a mission has a description.ext error
New, WishlistPublic


Sometime ago I wrote a script that automatically fill the missionWhiteList in our server.cfg . This works great!

Until we put a mission in there that has a description.ext. Then it seems like server's whitelist turns empty as no missions appear in the mission list after using the command #missions (after logging in as admin). Sample rpt output:

2015/07/04, 12:32:40 File description.ext, line 116: Config: ';' used as a separator in the array

What is really frustrating here is that there is no indication in the rpt which mission has the error. So it is really frustrating for us to fix.

I also think the default behaviour should be regardless of if there is an error in the description.ext for the missionWhiteList to keep working.


Legacy ID
Steps To Reproduce
  • This was on the linux server binary (64bit Ubuntu server)

Snippet from server.cfg (all mission files are present)

missionWhiteList[] = {

Event Timeline

Snippers edited Steps To Reproduce. (Show Details)Jul 4 2015, 1:10 PM
Snippers set Category to Server.
Snippers set Reproducibility to Always.
Snippers set Severity to None.
Snippers set Resolution to Open.
Snippers set Legacy ID to 1891210249.May 8 2016, 12:19 PM

Sorry but this is like saying, "my car has a flat tyre, it doesn't drive too well, this is extremely annoying".

I dunno try -autotest if you dont want to check missions for errors manually?