by frag.machine » Thu Apr 25, 2013 2:03 pm
IMHO a more sane way to do that would be to have an external file where you store info about known maps where Z-fighting occurs and what's required to fix it (for example, the entity classname, its targetname, origin offsets, etc). This way, you not only gives a solution for existing problems but you also create a way to fix less known community maps where this happens. You can even use existing file parse functions to implement this. Shoving hardcoded data into your engine always make it less flexible (besides, you always have the remote chance of CRC collision screwing something in other maps for no apparent reasons).
I know FrikaC made a cgi-bin version of the quakec interpreter once and wrote part of his website in QuakeC 
(LordHavoc)