OpFire? (Full Version)

All Forums >> [Current Games From Matrix.] >> [World War II] >> Steel Panthers World At War & Mega Campaigns



Message

Adamo -> OpFire? (3/30/2002 9:21:21 PM)

Is there ever a situation when I should not choose to fire back at an enemy unit during OpFire? When the enemy is firing at me and I'm asked whether I want to return fire should I always choose 'yes'? If I don't select either yes or no is it considered that I did not want to fire back? just asking adamo



peter hellman -> (3/30/2002 9:53:20 PM)

If you select either "yes" or "no" then it is considered a "no". If the unit that is having the opportunity to use opfire is moving, your hit percentage is reduced according to how fast the movement rate is.

When you fire at an entrenched enemy unit, you might have noticed that the hit percentage is sometimes very low. As soon as the unit fires back, your hit percentage usually goes way up. I'm not sure if that goes the other way around, but with this in mind, I sometimes do not return fire if some of my entrenched units are fired upon.



Supervisor -> (3/30/2002 10:11:54 PM)

Another thing to consider is, you weapon your about to use and your chance of success. Its pointless to use a rifle against a tank at 10 hexes away, especially if you haven't been seen yet, no sense in giving your position away and bring more fire upon yourself if there is no chance of success. A little trick, instead of selecting no, hit the escape key this will allow you to cycle through available op-fires without wasting and unwise oportunity.:D



Charles2222 -> (3/30/2002 11:39:23 PM)

quote:

A little trick, instead of selecting no, hit the escape key this will allow you to cycle through available op-fires without wasting and unwise oportunity.


About a year ago somebody brought up that same notion, and I've never seen it work. From what I've seen the esc. is "the worst" option. I just reloaded one of my old battles and it works like this.

1. Enemy unit moves.
2. Opfire for first elgible unit.
3. User hits esc.
4. Next unit for a very brief moment pauses as though to ask you if you wish to fire, but instead reacts as though a 'no' were given.
5. End of opfire opportunities for that first unit.
6. Onto the next unit. Esc. used again, and it proceeds once more to answer no twice.

Conclusion: Esc. does not scroll you through every possible opfire unit (or else why only two chances as normal?). The only thing it's good for is if you see a unit which you know you don't want to opfire at, as it will scroll to the next opfire unit, and answer no again, hence a keystroke is saved, but the reach to the far corner of the keyboard as opposed to sitting on 'n' and preparing for 'space' may negate said advantage.



Mojo -> (3/30/2002 11:52:14 PM)

It's also important to conserve your op fire opportunities. A fact driven home the first time I played Wild Bill's scenario "A Wounded Tiger". There you have one Tiger to defend another, immobilized Tiger, against 13 (or is it 15) T 34s. A few turns in you do pick up another Tiger. If you last that long;)

Anyway, you have to use your op fire very carefully because if you use it when a T 34 comes into sight at 20+ hexes you'll only have MGs left for the T 34s at 6 hexes and brother that is a helpless feeling.

WB does comment in the scenario description that you should conserve your ammo because you'll need it. Always listen to Bill:D



Kanon Fodder -> (3/31/2002 12:12:51 AM)

Another problem I came across, much to my dismay, is that OP fire will use any and all firepower available to be fired.

I was playing the Desert Rats scenario and had finally got my SAS units adjacent to the ammo dump. From past experience I have always found it best to wait for the next turn to use satchel charges or demo packs.

In the AI's turn I was given the opportunity to use OP fire against an Italian sentry unit from 1 hex away.

No brainer (I thought).

My SAS unit then proceeeded to use [COLOR=orangered]all[/COLOR] of it's weaponry, [COLOR=crimson]including[/COLOR] the demolition charge against this small infantry target.

Not only did I not have the demo charge to use against the ammo dump, the IT sentry unit was [COLOR=blue]not [/COLOR] destroyed.
:mad:



Leto II -> (3/31/2002 12:17:06 AM)

Yeah, I had something like that happen to me a couple of times in the past. Now I disable satchel charges and other such weapons if I know that I'm going to use them for demolitions. Of course then I usually am given an opportunity to close assault some tank during opfire when I have them disabled.

Go figure.



chief -> (3/31/2002 1:19:45 AM)

Leto II: Ah yes...the best laid plans of mice and men oft go astray....doesn't it always happen?!:D :D :rolleyes: :cool:



Capt. Pixel -> (3/31/2002 2:12:14 AM)

If I have specialized units, like the SAS mentioned above, with a specific task requiring a specific weapon, ie. the satchel charge, I'll turn off that weapon on the unit info screen until it's needed.

This keeps the unit from expending ineffective or precious weaponry in an oppfire situation.

Setting response range ('Y' key) is also very useful in controlling oppfire. For instance, who wants their Inf AT teams firing all their shots at long range? Set their range to 0 or 1.

I personally play with the option OFF. My units oppfire according to their needs given the conditions I described above.

This works pretty well for me, but I still get shots suckered off at inappropriate targets or ridiculous ranges.

Fortunes of war, eh? :rolleyes:



ZoomBoy27 -> (3/31/2002 6:22:28 AM)

Also watch for this with recon teams
Keep their ranges down to 1 or 0


ZoomBoy
Developing a iso-tile 2D RPG with skills, weapons, and adventure. See my old Hex-Tile RPG GAME, character editor, diary, 3D Art resources at [URL=http://www.geocities.com/jzoomiethomas/]Check out my Web-Site[/URL]



Kanon Fodder -> (3/31/2002 6:24:04 AM)

I didn't realize I could turn off the specialized weapons.

I'll definitely check that out before I play the next portion of the Desert Rats campaign.

Thanks, guys.



tracer -> (3/31/2002 10:48:46 AM)

[QUOTE]Originally posted by Charles_22
[B]

{snip} but the reach to the far corner of the keyboard as opposed to sitting on 'n' and preparing for 'space' may negate said advantage. [/B][/QUOTE]

C22,

Here's a trick I picked up here last year: during op-fire left-click mouse answers 'yes' and right-click answers 'no'.



badinfo -> (3/31/2002 1:18:44 PM)

Woohoo! Thanks for that little gem Tracer! :)
Hehe, I didnt even know you could answer no, I have just been sitting there watching the timer till now lol.



Charles2222 -> (4/1/2002 12:22:36 AM)

tracer: Well that's good to know, for when those times it seems that using the mouse is less tiresome than the keyboard, and in my book that's very close. Variety lets you rest a portion of the body.

Does anyone get what gmenfan was talking about? To me he's talking about the ideallic paradise of being able to effectively scroll through every elgible unit to make the choicest selection for each enemy trigger that comes up, and to my knowledge that's pure fiction. Esc. key answers 'no' twice, to both the original opfire unit and the second opfire unit; there is no scrolling through opfire elgible units. You get two chances, and then it's onto the next enemy trigger which will give you two chances again.



tracer -> (4/1/2002 10:52:04 AM)

[QUOTE]Originally posted by Charles_22
[B]tracer: Well that's good to know, for when those times it seems that using the mouse is less tiresome than the keyboard, and in my book that's very close. Variety lets you rest a portion of the body.
[/B][/QUOTE]

Actually, until reading this thread I didn't know you could hit the spacebar for 'yes'. Before learning about the mouse, during the AI's turn I would rotate my keyboard a little so I could comfortably hit the Y and N keys! We're talking 'carpal tunnel waiting to happen' :eek:



Charles2222 -> (4/1/2002 6:13:14 PM)

tracer: Actually I don't know how I got started on the spacebar. I suppose it was because it was more logical that the two keys useable in that instance, were both together that I found it. Perhaps I attributed the spacebar to 'fire' instead of 'yes' and that's how started that. In fact, I can recall that for the longest time, I wasn't thinking in terms of 'no' when I hit 'n', but 'next' instead.



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
7.078125