Carrier Reaction Problem

[NAVMAN]

Hi all. This is my first post. I have encountered the following situation a couple of times in the same scenario:I have set my carrier force to "d/n retire" and "d/n react".Yet, the force still says it is reacting and promptly gets destroyed. It is my understanding that setting to "d/n react" should prevent this from happening.
Any ideas?Thx.

[Grotius]

Well, I'm a relative newb too, but I thought I'd mention rule 8.23, which says that CV TFs "may automatically move one hex towards an enemy air combat TF after each air search phase" -- even if set to Patrol/Do Not React to Enemy.

There have been threads here complaining about this one-hex movement, and possible workarounds, such as ordering your Air Combat TF to follow a small Surface Combat or Transport TF. (Only Air Combat TFs do that 1-hex movement.) Or just be careful about moving your CV TFs anywhere near the enemy CVs unless you mean business.

[NAVMAN]

Grotius,
Thx for the info. Seems contradictory that you can set for d/n react
and it still reacts one hex. Oh,well. I think this aspect of the game
needs to be re-examined by Matrix.

[mogami]

Hi, Aircombat TF's that react 1 hex do so because they are in enemy air range but outside their strike range.
USN TF's are trying to launch a strike. The enemy TF's are already launching. You will not be involved in a carrier battle because of the 1 hex reaction. (But you might get to fight back)

[NAVMAN]

Mogami,
That's a feasible and interesting idea.