Linux builds CRASH due to specific maps.

Some maps contain filepath references that are at odds with the standard that Linux expects, while Windows is more flexible. These map's sources must be changed to fix all problematic filepath references. This can include wrong-way slashes ( / vs \ ) and incorrect capital letters. Affected entities are ANY entity that can reference a filepath, which can be through various key/value pairs as well.

E.G. 2 types of crashing errors in an ambient_generic entity filepath from the Kroush source:

I do not run a Linux build myself so I am not aware of all the crashing maps. Due to the tedious nature of combing through map's many many entities, I think that a scripted solution could be a good avenue to fix this. .map and .rmf files are saved directly as plaintext, and could be trivial to parse through for these errors. Any .jmf source that we do have should be re-saved as .map or .rmf .

Start by inspecting the repository's .map and .rmf sources, along with any available .jmf files, for filepath references in entity key/value pairs. Compare slash direction and capitalization against Linux expectations, then verify that affected maps no longer trigger filepath-related crashes in a Linux build.