Good point about the ordering ^^' D2896

The reason it has become a separate component is because there is much logic different in how to handle a garrisoned entity vs a turreted entity and them being together became quite awkward.

So is it now possible to have an entity with <TurretPoints> but not a <GarrisonHolder> node?

Yes, but we don't have the possibility to occupy that point yet ^^
I'm going to work on the turrets patch first (that needs this). Then we can look further into the split.

Good to know.
Also, why <TurretHolder> and not simply <Turrets>?

Because the component defines the ability to hold turrets not only the turret points. It may well be that in the future it has more template data than just the turret points and renaming the component then is (also for modders) more work (it can obviously be scripted) than just adding a template value.

Yes, I understand the node levels, I just meant the name:

<Turrets>
  <TurretPoints>
    <One>
      <X>0</X>
      <Y>9.3</Y>
      <Z>0</Z>
    </One>
  </TurretPoints>
</Turrets>

Anyway, it's not important, I was just curious.

Yeah, I understand what you meant :) That was what I tried to explain. To me, turrets looks like it is only a list of (possible) turret points, although it can define more than just that.

Anyway, it's not important, I was just curious.

Yeah, fine :)

D2896