Hold Fire Needs Stop Command

Dragon45 · Post by **Dragon45** » 28 Sep 2006, 23:44

Apologies; i havent checked the Mantis tracker if this has been psoted or whatnot already.

What I've noticed for a long time is that assault units that are targetting something and are set to Hold Fire need to be manually STOP'ed to actually stop aiming. Otherwise they hunt/kill their target before actually going to Hold Fire mode. Its a bit annoying, for example, this is a bit of a pain for cloaking units and adds unncecessary micro.

Anyone want to agree/disagree/neuter me?

I decided to post this now because we more or less have a new ver incoming - and i figured heck, why not? ^_^

Peet · Post by **Peet** » 28 Sep 2006, 23:51

Thing is, that would prevent a unit from firing at all when it's on hold fire.
I often keep my berthas on hold, then tell them to target specific things. If your feature were implemented, that wouldn't work.

Caydr · Post by **Caydr** » 29 Sep 2006, 00:01

No, not like that. What he means is that when set to hold fire it'll stop attacking something it's attacking as a result of being on fire at will. Not things manually targetted.

While we're on the subject, a unit should automatically know to stop firing on something it's trying to capture, too.

Dragon45 · Post by **Dragon45** » 29 Sep 2006, 00:13

Caydr wrote: While we're on the subject, a unit should automatically know to stop firing on something it's trying to capture, too.

I disagree with that last point. There's too many variables factored in into a solid capture attempt; distance, weapon firing range, speed, etc. There's no way any unit AI could guage al lthat according to what a player thinks would be best. What's really needed in regardting to capturing is a shortcut key for capture.

Caydr · Post by **Caydr** » 29 Sep 2006, 00:16

You can define hotkeys easily.

I don't mean to derail, let me just add this and I'll shut up: I don't mean that it should stop firing the instant the capture order is given, I just mean that a unit should not fire on something that it is actively capturing, like with the nanolathe and all that, actually performing the deed of capturing.

malric · Post by **malric** » 29 Sep 2006, 01:24

Dragon45 wrote: Anyone want to agree/disagree/neuter me?

Agree.

esteroth12 · Post by **esteroth12** » 29 Sep 2006, 01:32

e: nvm, im stupid

KDR_11k · Post by **KDR_11k** » 29 Sep 2006, 08:50

Caydr wrote:You can define hotkeys easily.

I don't mean to derail, let me just add this and I'll shut up: I don't mean that it should stop firing the instant the capture order is given, I just mean that a unit should not fire on something that it is actively capturing, like with the nanolathe and all that, actually performing the deed of capturing.

Make the weapon jam when the nanolathe is active.

Caydr · Post by **Caydr** » 29 Sep 2006, 17:15

And then your unit can't build and defend itself at the same time.

PauloMorfeo · Post by **PauloMorfeo** » 29 Sep 2006, 19:15

I honestly don't know. It kind of makes sense.
Hold Fire = Do not engage enemies != Do not fire at already engaged enemies.

But i am cool with either way because, most of the times, that change is intended to means to also stop firing.

KDR_11k · Post by **KDR_11k** » 29 Sep 2006, 21:34

I usually hammer on stop after setting a unit to hold fire to make sure it really doesn't fire. That should not be necessary.

Spring RTS Engine

Hold Fire Needs Stop Command

Hold Fire Needs Stop Command

Re: Hold Fire Needs Stop Command