Clean up dedicated transports

[nstephenh]

• Make all dedicated transports a unit with a model in them. This will make new recruit display much better.
• Ensure that all units that can take a dedicated transport don't have any "number of models" that checks "and all child selections"
• Consider moving common dedicated transports to a shared selection entry group? But might not be able to then count number of models in parent easily

Units that are having issues with dedicated transports:

• Mortus Poisoners

[Mayegelt]

I think the 3rd option has been talked over before, but an issue of some RoW or inconsistencies in who gets what, when was to much of an issue to code it out without it looking like a horrible mess, while still keeping it compatible with BSData Editor (and as such could stop it working with other programmes that use the data).

[nstephenh]

Does anyone remember why we set some of the dedicated transport hides are set both on the link and on the entry itself? I'm assuming this was just an oversight

[Mayegelt]

Does anyone remember why we set some of the dedicated transport hides are set both on the link and on the entry itself? I'm assuming this was just an oversight

I assume that was the case that some were done twice. It might be because some were done when we were doing it one way, then they were done a different way later on.
If you can make a file check or whatever to find all the dedicated transports that have hidden links in them as well as hidden links in the linked entry, then we can probably filter that better.
We could as suggested above make an omni entry for dedicated transports as a link, but just put the ones that hide for X but not for Y unit with the same restrictions into the link with a "Ancestor is XXX unit" thing now my crusader to get BSEditor compatibility is over.