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.