Hold Fire button on 95mm Cromm and stuh.

[Guest]

Welcome, Guest. Please login or register.
Did you miss your activation email?

1 Hour 1 Day 1 Week 1 Month Forever

Login with username, password and session length

[TheIcelandicManiac]

Yea yea i might get some shit flung at me but i was just wondering about adding an hold fire button to those things for i know that i am not the only one that looses units due to the stuh sees an engie squad in the middle of nowhere and fires but misses so badly it hits your own squad and instant gibbes it.

[8thRifleRegiment]

+1 ?

[MittinsKittens]

Can't see a reason why anyone would a problem with this to be honest, so a +1 from me too dude

[RikiRude]

imo all tanks/vehicles should have a hold fire, but in this case it's even more important.

+1

[Tymathee]

imo all tanks/vehicles should have a hold fire, but in this case it's even more important.

+1

agree. i hate when my m10 fires at infantry just before i can get in range of firing at a tank.

would also love to see if coh could be edited so that you don't fire at things you can't hope damage. i.e. bar rifle firing at tank, puma firing at tank, etc. I think I've seen it in another mod, anybody know? Has to be either BK or BotB.

Hmm, maybe all units can be like medics and the only way you can fire at it is if given an order to fire, or they're fired at.

[LeoPhone]

Yes we could make perfect target priorities for all units and remove any micro the player has to do himself.

but I don't know if we should. personally I don't like it.
also, the idea behind EIR is we change vcoh mechanics as few as possible right?

[Hicks58]

Tbf, I'd be more than happy for target priorities to stay as they are. The single difference that I'd make, is that whatever YOU manually attack, your unit continues to attack until ordered otherwise.

It's hellishly annoying micro'ing a tank, trying to circle-strafe like a pro, only to get sack kicked by priorities every time you give the tank a fresh move command to keep the circle-strafe going. T_T

[LeoPhone]

@hicks

if you do this the following will happen as well:
atg spots infantry, atg starts shooting infantry.
tank shows up
atg keeps shooting infantry.

this is just a simple example but it will happen with every single vehicle you have.

[TheIcelandicManiac]

But it gets quite annoying to get this

Tank meets atgun
enemy drops glider
tank attacks glider and bounces 4 times
tank wont attack atgun
enemy bring his own tank
you lose.

[Hicks58]

Leo... You didn't quite fully understand what I said.

I said, what the PLAYER targets. If a player targets a squad of infantry with his ATG, then it's his own dumbarse fault tbh.

[LeoPhone]

Hicks... You didn't quite fully understand what I said.

I said, when the CODER codes that in. the result is units keep shooting the 1st target they ever saw until told otherwise.

[Tymathee]

how about this then Leo phone. Only dual purpose units get their priorities even'd but specialty units like atgs and hmg have priorities set towards what they're good at.

Specifically speaking of tanks

[Hicks58]

Leo your referring to setting all the unit priorities equal, I'm referring to something different.

I'm referring to keeping all of the priorities as they are, BUT having player intervention override the priorities.

[MittinsKittens]

Is that even something they can code in? Seems like you're stretching the game engine/code a little too much there.

[LeoPhone]

for the 3rd time hicks, if you do what you suggest my response is the result.

you are free to look at the rgds yourself and see if there is a different way though.

[TheVolskinator]

To simplify what I think I understand:

You MANUALLY order your M10 to attack a StuG and proceed to go 12azor on his ass, circle strafe and all, pr0 style. One of two things does/could happen:
A) In the current coding, your M10 sees a squad of KCH, which by it's target table are lolnoms towards the top. It starts shooting retardedly at them, while the stug kicks it into reverse and proceeds to rape your M10.
B) In what I think is being proposed, you manually order your M10 to target the same stug. You do the 12azor and all, circle and rape, and 2-4 shots later your M10 shouts some lame shit about getting to Vet1, and then runs the aforementioned KCH over. Three seconds later it hits a mine and a PaK wipes it off the face of the earth.

I like the idea of it, but if it was coded into the game that whatever that unit attacks first would be the only thing it shot at, we'd have shit like:

ATG sees a line of Tommies approaching. ATG shoots at them for teh' lolz. Cromwell runs up and beelines it towards your PaK. Being mentally retarded, your PaK crew keeps shooting the tommies with no effect (aside from the luger dude crit'ing fucking everything cuz' he's been rape since...ever), the Cromwell lolrapes the pak etc.

Engineer squad has a shitty run-in with a KT. KT focuses on a nearby form of armor, but your engies sit there rat-tat-tat-tating at it even though a sniper, mortar, other other easy kill waltzes right up and past them.

And so on. It might work but I think its more then the engine can handle.

[DarkSoldierX]

KCH don't ever get near the top of a m10's target tables. A stug has 200 priority. A KCH has like a fourth of that.

I don't think we need to be changing this line of code anyway. Less micro = less fun.

Let ATGs and marders shoot retardedly at infantry unless you holdfire them, it adds micro, so u actualy gotta pay attention.

Which reminds me.

Marder and 50mm need holdfire too.

[Spartan_Marine88]

Marder and 50mm need holdfire too.

Oh yes, hes so right.

so tired of someone using an infantry squad to get my marder to fire at it, then fly in with an m10 and circle troll it

[TheVolskinator]

^Now I know how to troll your PE coys (marder-based)! Sweet...

[Hicks58]

Leo, what I'm referring to would likely need more than RGD coding.

Though just straightening out all the unit priorities would probably be faster.