EquipmentSets aren't sets. Any way to get around this?

[Will Greaves]

So if you have a code like:

    <equipmentSet>
      <equipment slot="Item0"
                 id="Item.sword" />
      <equipment slot="Item1"
                 id="Item.javelin" />
    </equipmentSet>

    <equipmentSet>
      <equipment slot="Item0"
                 id="Item.spear" />
    </equipmentSet>

Logically, I'd assume that a troop with these two 'sets' would either spawn with a sword and javelin, or else a spear. But that isn't how it works; in addition to other combinations, the troop can spawn with a spear and a javelin, even though there's no 'set' with that combination.

So, apparently the 'sets' aren't actually sets, as it mixes & matches from the various 'sets', making them pointless. Is there any way to get around this, so that, in the example I provided, you either get a sword & javelin, or else a spear and nothing else?

In that specific case, I think a workaround might be to have both the spear and the javelin in their respective Item1 slots. But in other, more complex cases, such as when shields and other items are present, it isn't going to be possible to separate the entire sets with that method.

Anyone know more about this subject?

 

[bıind]

I think the only way to get that kind of variation is to make different items compete for the same item slot, as you mentioned. There are a few opportunities to get some big differences though. I have troops that mix bow and crossbows, the weapons compete for the Item1 slot but every troop carries arrows and bolts, this way they won't be left without ammo by randomisation. The most noticeable items compete for slots, and the troops carry some redundant items. E.G. if you wanted some troops with a high tier glaive but some with lower tier swords and shields, make the glaive and the shield compete for Item1. Then give every item set a sword in Item2. The shieldless troops will prioritise the glaive and you'd hardly notice their sheathed sword.

If you want to do it perfectly just make entirely separate units. I think you can even give them identical names. Their character IDs would have to be distinct - they wouldn't work well in troop trees.