Wiki updates are coming... I promise, but I need to go over all the new additions with a fine toothed combed, and it is taking a while.
Ok, ok... we forgive you...
Thanks for all the infos on the water units.
Using the all/deep water tags on a unit which is also a land unit will crash Glest.
The <fields> tag is I believe a relic from an earlier era of Glest, where it was perhaps also used as attack field, it never allowed multiple fields, and was never meant to. It has caused me much grief, and I think for 0.3 I'm just going to go ahead and break XML compatibility.
[/quote]@ wciow
Erm... isn't using any other tag with the
all tag kinda redundant anyways? Also... a unit that is both a
land unit and a
deep_water unit (but not
amphibious nor
any_water) is kinda strange too... But I'll grant people with better imagination than myself the "right" to need it...
@ silnarm
Erm... isn't a unit'
field value in say vanilla Glest used to determine whether another unit's attack can be used against the former dependent on the later
attack-fields values?...
By "break XML compatibility" do you mean units for GAE 0.3 may hold multiple fields in their XML's, NOT breaking GAE 0.3 but still breaking vanilla Glest (and I think MG)?
Well... is there that much need for engines not supporting water units to support multiple fields? Granted, a unit being both
land and
air might be useful but... I dunno... I guess it won't be such a major hassle also because other GAE features (e.g. some new particles' trajectories) will likely crash vanilla anyways...
So IMHO do go ahead and break the XML compatibility!