AD map detection rethink?

[neogeographica]

To best solve the issue of not detecting that a map depends on AD (when it does), or thinking that it does (when it doesn't), recently I changed the detection criterion to just look for bsp names that start with "ad_" since that worked for every existing map.

Apparently tho the recent release "dfl_evilwizard.bsp" breaks this since it is an AD map. (It also misspells Arcane Dimensions in its readme file, so even my old detection method would not have worked.)

Not sure what to do here.

We could just ignore this exception -- if someone checks the readme then they could fix the AD dependence in the preview of the quakelaunch config.

I coooould start baking a list of exceptions into quakelaunch or the main quakelaunch.conf, but that feels bleh.

[neogeographica]

One generalized way to deal with this would be to support a directory of prebaked mod-specific quakelaunch.conf files that could be used in place of the usually initially-generated file. Not sure when/if I want to tackle this though as long as there's not a bunch of other users for this project.

[neogeographica]

A simpler thing to do would be to keep the current heuristics, but if Arcane Dimensions is mentioned in the readme, then add a comment into the generated quakelaunch.conf for the gamedir that says "HEY the readme mentions AD, maybe this is an AD map?"