Actually that would not work. MM treats those as two different units and would not allow you to put quirks on the scorpion tank that way. I think scjazz if more or less saying that if you create a tank called Locust then the quirks between the Locust mech and the Locust tank clash. I really don't see a way of fixing something like this though w/o adding a new entry for unit type.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a fix for this, which is in the GitHub repo in the branch bug#4578.quirks.unit.type. However, I need to update the quirks XML file first before I push this. If no unit type is specified, it defaults to 'mech, but there are quite a few non-mech entries in the canon quirks file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
and even after editing Quirks in MHQ it can not be fixed.
Have you tried using the full name of the tank?
For example, use 'Scorpion Light Tank', instead of just 'Scorpion'.
Actually that would not work. MM treats those as two different units and would not allow you to put quirks on the scorpion tank that way. I think scjazz if more or less saying that if you create a tank called Locust then the quirks between the Locust mech and the Locust tank clash. I really don't see a way of fixing something like this though w/o adding a new entry for unit type.
I'd rather suggest to put the quirks into the MTF/BLK files. Both are extensible enough to accomodate them.
I have a fix for this, which is in the GitHub repo in the branch bug#4578.quirks.unit.type. However, I need to update the quirks XML file first before I push this. If no unit type is specified, it defaults to 'mech, but there are quite a few non-mech entries in the canon quirks file.
The fix for this has been merged in [d3f8f].