Change Details

Currently, when an entity leaves a moving state, it tells UM to stop. One could also argue that UnitAI should inform UM to stop when the reached state requests stopping. This is a prove of concept for that behaviour. This means that, when e.g. acceleration is implemented subsequent move orders don't stop and reaccelerate, if I am nto mistaken :)

Currently, when an entity leaves a moving state, it tells UM to stop. One could also argue that UnitAI should inform UM to stop when the reached state requests stopping. This is a prove of concept for that behaviour. This means that, when e.g. acceleration is implemented subsequent move orders don't stop and reaccelerate, if I am not mistaken :)

Currently, when an entity leaves a moving state, it tells UM to stop. One could also argue that UnitAI should inform UM to stop when the reached state requests stopping. This is a prove of concept for that behaviour. This means that, when e.g. acceleration is implemented subsequent move orders don't stop and reaccelerate, if I am ntoot mistaken :)