Currently the template tree includes a template_unit_mechanical.xml, which has only two children, *_ship.xml and *_siege.xml. However:
- it does very little
- it implies ships and siege engines are closer related than, say, cavalry and infantry
- there are no *_organic_* or *_soldier_* templates either
Therefore it makes sense to simplify the templates a bit by deprecating the mechanical one (similar to D1734).
- deletes template_unit_mechanical.xml and inserts its relevant values into its descendants
- renames template_unit_mechanical_ship* to template_unit_ship*
- renames template_unit_mechanical_siege.xml to template_unit_siege.xml
- renames template_unit_mechanical_siege_ballista.xml to template_unit_siege_boltshooter.xml
- renames template_unit_mechanical_siege_onager.xml to template_unit_siege_stonethrower.xml
- renames template_unit_mechanical_siege_ram.xml to template_unit_siege_ram.xml
- renames template_unit_mechanical_siege_tower.xml to template_unit_siege_tower.xml
- adjusts all entity parent paths
The ballista→boltshooter and onager→stonethrower moves are to avoid unnecessary misunderstandings: ballist(r)a, catapult, and onager are words that could be applied to various torsion engines, both dart and rock weapons. E.g. 0 A.D.'s cart and rome “ballistas” have the “onager”, not the “ballista”, as their parent. Contrary to the current AoE terminology, “boltshooter” and “stonethrower” make immediately clear what kind of artillery these templates represent.