Limit Tilesets per Pack

[MightyMic]

I've been thinking that we could add something in the xml to limit the tileset that a pack (i.e. Megapack, Annex, Vbros. etc.) would be able to use. That way Annex and Megapack could be in the same executable but Annex would only be able to be played with Toxic High/Low Wasteland High/Low. Then Annex wouldn't have to package it's self as a separate game.

I was thinking something like:

Code: [Select]

<limit-tilesets value="true">
     <tileset name="toxic_high"/>
     <tileset name="toxic_low"/>
     <tileset name="wasteland_high"/>
     <tileset name="wasteland_low"/>
</limit-tilesets>

And you could also have an option to exclude tilesets. Like for Megapack:

Code: [Select]

<exclude-tilesets value="true">
     <tileset name="toxic_high"/>
     <tileset name="toxic_low"/>
     <tileset name="wasteland_high"/>
     <tileset name="wasteland_low"/>
</exclude-tilesets>


[John.d.h]

It seems like a better way would be something a bit higher-level, like separating the content into different blocks/suites, so that they can cordon off the tilesets, maps, scenarios, and whatever other content only fits with that tech tree.  This way you could have, say, Megapack, Annex, and Glest In Space each with their own tilesets, maps, scenarios, etc., and they wouldn't overlap.

[Ishmaru]

Megaglest allready supports standalone mods using a commandline function, which only includes content that the modder includes.