Spring RTS Engine

In this day and age, footprint, maxslope, maxwaterdepth and crushstrength (and etc) should be in unit's individual unitdef, not based on silly arbitrary "classes" defined somewhere else entirely. Would it be entirely too hard to make units read and apply these values from their own unitdef???

SpikedHelmet wrote:In this day and age, footprint, maxslope, maxwaterdepth and crushstrength (and etc) should be in unit's individual unitdef, not based on silly arbitrary "classes" defined somewhere else entirely. Would it be entirely too hard to make units read and apply these values from their own unitdef???

More movedefs = longer time required to calculate pathing info

Then at least I'd like an option not to use them, for instance if no movementClass tag is found in the unitdef it uses the god damned unitdef's defs.

I could make you a couple lines of lua to do that, if you like.