Spring RTS Engine

myself @ http://springrts.com/phpbb/viewtopic.php?p=513980#p513980 wrote:It is just a function of relative mass (and speed and impact angle). So, give heavy tanks appropriately large mass-values in their UnitDefs compared to the light squishy peons.

There are a few other tweaks you can make (and some I'm working on) which will mostly let you get pretty close to SupComII's flowfield-style movement. Mostly.

Are you using vanilla XTA or a special dev version? (Would like to compare mass values)

Kloot wrote:

myself @ http://springrts.com/phpbb/viewtopic.php?p=513980#p513980 wrote:It is just a function of relative mass (and speed and impact angle). So, give heavy tanks appropriately large mass-values in their UnitDefs compared to the light squishy peons.

There are a few other tweaks you can make (and some I'm working on) which will mostly let you get pretty close to SupComII's flowfield-style movement. Mostly.

Im impressed oO amazing job...
As zrwsg said, what i need to enable them?, what i need or fix to enable the new pathing system?

luckywaldo7 wrote:Are you using vanilla XTA or a special dev version? (Would like to compare mass values)

+1

Kloot, tell me what to do and I'll implement it in evo.

Mass already has at least one function and is balanced for impulse in ZK. Could you use a new tag such as pathingMass?

mass is used by transports too. (to decide what/how much they can pick up)

transport mass should be extracted too.

I think each unit/weapon/feature tag should do one and only one thing. If a tag affects behaviours that are not directly related it should be split into multiple tags. Games should get to decide upon the correlations between technically unrelated mechanics.

Well it's not really that big a deal in this case since all three mass values should be reasonably correlated. But yes, separation would be nice.