#Newly resurrected units should be set by default at holding position

1 messages · Page 1 of 1 (latest)

shell sentinel
#

Because they manœuvre like in vacation in enemy lines and it’s hard to manage them.

flat halo
flat zinc
#

stateprefs.

or set your rezbots to Hold Position
since they transfer that state into whatever they resurrect.

dusky mantle
#

I'm one of the few players who uses movement states extensively and I agree the problem exists, I just don't like the offered solutions.

The resurrected units should probably have the same state as they had before being destroyed. But this wouldn't be a complete solution either, because even though I use roam on units a lot, I don't want a newly resurrected unit to immediately start roaming again without my input.

The same problem exists with stateprefs, so that's not a complete solution either.

And the rez bot's movement state should not affect the resurrected unit's state, because some of us use that as well - rez bot with roam will act in a bigger area with fight command and patrol than it would with hold position.

Luckily there's an easy solution to this problem that in my opinion works perfectly for all cases: wait

Most players don't know, but wait on mobile units pretty much doesn't do anything but make them hold position. I use wait all the time to essentially toggle between roam and hold position.

So if resurrected units are waiting, then they're effectively have the hold position state. But unlike the position states, wait has an obvious visual indicator as well and it's even possible to filter waiting units with the select command. So to me this seems like a logical, simple and even intuitive solution to the problem.

I haven't looked at the code, but because resurrected units get the halo, I'm assuming the same exact logic can be used to apply wait state to them as well (only if the resurrected unit is mobile and has a weapon though).

brittle flower
fierce dagger
# dusky mantle I'm one of the few players who uses movement states extensively and I agree the ...

I already looked into it and it is not trivial as it's engine level thing

https://github.com/beyond-all-reason/RecoilEngine/issues/2547

It could be fixed on the game side but state prefs already do that. You just have to have it set for every unit.

GitHub
Resurrected unit inherits its move and fire states from resurrectin...

The issue Resurrection Setup: In BuilderCAI.cpp, the ExecuteResurrect() method calls ResurrectObject(), which eventually calls ownerBuilder->SetResurrectTarget(feature) Unit Creation: In Builder...