At first I was about to entitle this thread "transportcapacity is halved!" and put it into "Help & Bugs" , but now I'm not sure of anything.
If I make a transport unit with:
transportcapacity=20;
Then it can only load 10 units and no more.
Then if I take the same transport and change the line in its FBI to:
transportcapacity=40;
It can transport 20 units.
And I'm talking about ground transport with regular loading script.
Just try with the XTA ArmTHovr.... oh wait, what's that?
canload=1;
transportsize=3;
transportcapacity=15;
transportmaxunits=16;
If there is a new transportmaxunits tag, then what is transportcapacity? Is it the max sum of the footprint max dimesnions of units in? There is nothing in the Changelog about that! What thread have I missed?
In TA the transportcapacity was the maxnumber of unit, why change it to something else and then add a new tag that fullfill the role previously attribued to transportcapacity?
Oh my bad, transportmaxunits is also indeed an old TA tag, apparently in old TA Transport ships use .... grah it changes between Totala1.hpi and rev31.gp3!!!
Maybe after all transportcapacity is the same in Spring and TA3.1c and I just got tricked into believing otherwise by loading 1x1 unit in TA and 2x2 unit in Spring?
Ok, I'm totally confused now, sorry for everything, I'll come back once I have a clue.
Meanwhile, if someone knows exactly and for sure what these two tags, transportcapacity and transportmaxunits, do, in TA3.1c and in Spring 0.67b3, please enlighten me.
Oh, I just rechecked, in SWTA droideka have a 2x2 footprint, and with TotalA.exe 3.1c (well, SWTA.exe technically...) I can load 20 droideka with a transport that can only load 10 Arm Peewees in Spring62b2. So there do is a difference between TA and Spring with the interpretation of that tag. However, maybe it's TA that's silly and Spring that makes sense by giving different meaning to those two tags?
Anyone knows?
