Tutorial: Killing z-fighting in a stock Quake engine

[szo]

Why are you hardcoding the thing in the engine while you have the ability of loading an external ent file?

[Baker]

[frag.machine]

[mankrip]

Which is why Makaqu includes a PAK file with lots of content fixes plus some improvements. I don't want to make its code a whole mess by adding content hacks.

How about a patch file format for Quake? Essentially, get the map_patches_t map_patches[] struct from Baker's code and load its contents from a file instead of hardcoding.

Such a format could even be expanded to support textures, UV mapping, 3D meshes and everything else. This would allow for modified content to also receive the fixes, and would allow users to create new content fixes without recompiling the engine.

I see no need for installation instructions if such a patch file is to be loaded from the executable dir. Many engines are bundled with DLL files, and the users doesn't complain about that.

[Baker]