Map specific templates

[elexis]

Some maps might want to use templates that can only be used with that map feasibly, mostly inheriting public mod templates and changing just some properties in there.

Examples:

• Polar Sea has a special snow wolf template that is most likely never going to be used anywhere else.

• Danubius could use some special templates too, walls that don't convert to the player.

• Scenario/Campaign maps would be able to create individuals with some traits that inherit from public mod templates. For example they can have a custom balancing or name. (Not a custom actor, because if we have that in the public mod, then we should also have a template in the public mod using the visual actor for map authors).

(Since maps should also be able to specifc gamesetup settings with actual JS code, we can often have more than 3 files (pmp, xml, triggers js, gamesetup js, templates xml), it might be an idea to put every map into a single directory. But the downside (a lot of directory traversal overhead when working with the files) seems to outweigh the benefit of doing so.

[elexis]

New templates should be as generic and widely usable as possible and thus preferably be not made map-specific.

The three given examples order-following ANIMALS, unconvertable walls and final boss could all become more versatile and not solved on a directory-per-map basis.

However if that is truly ever needed to have a template that only works on one map, we have the ability to create a subfolder in the templates directory for new maps, and a subfolder in the art directories for map-specific art and so forth.

Creating one directory for the map and then art, textures, music, templates folder within that has the disadvantage of requiring that subfolder directory structure to be kept in sync with the public directory structure. Thus should be avoided. Thus nothing to do here.