Notes from a Small Island

[Lokasenna]

ORIGINAL: Canoerebel

If reaction were limited to no more than a hex, I wouldn't even consider the strategy I'm proposing. As you suggested, I'd set CVE fighters to a range of one, thus ensuring that they'd be within range to provide CAP to reacting CV TFs.

But in two of my last three carrier clashes, I've seen reactions of three or four hexes. This includes the most recent battle in this game (less than three months ago game time, a bit more real time), and a late carrier action in my game with John III (sometime in late '44 or early '45, when John was raiding SoPac and I tried for an intercept just east of Luganville).

Are you not running the most recent version? Because multiple-hex reactions were fixed.

ORIGINAL: Canoerebel

If carriers can react multiple hexes, you can see that it eliminates the strategy of "keeping the CVEs within close range for mutual air support).

Addressing one of your concerns, my CVEs wouldn't "take the place of AA platforms." They'd supplement. Usually, my carrier TFs have about 15-18 ships. What if I just fill them up to 25 total with the additional CVEs (or, possibly, pull out a few CV/CVL and add in as many CVE and a few DDs to make up 25)?

As for the surface combat threat, the Allies vastly outnumber the Japanese in combat ships. Death Star should have about eight to ten dedicated combat TFs. In the last battle, Erik didn't try for a surface combat engagement. That doesn't mean that he won't this time, but I think the odds are low, and that even if he does he's likely to come out on the short end.

I agree I probably can't win without CVs or if I lose a carrier clash decisively. That's the reason I'm turning over ever stick and leaf trying to figure out a way to maximize the chances that CVEs are there to enhance CAP. The additional 900 fighters (plus some TBM squadrons for ASW support or follow-up naval strikes) offers a tremendous amount of security.

With all of that information, I'd be going for the battle.

Check your version...

[Bullwinkle58]

ORIGINAL: Lokasenna

ORIGINAL: Canoerebel

If reaction were limited to no more than a hex, I wouldn't even consider the strategy I'm proposing. As you suggested, I'd set CVE fighters to a range of one, thus ensuring that they'd be within range to provide CAP to reacting CV TFs.

But in two of my last three carrier clashes, I've seen reactions of three or four hexes. This includes the most recent battle in this game (less than three months ago game time, a bit more real time), and a late carrier action in my game with John III (sometime in late '44 or early '45, when John was raiding SoPac and I tried for an intercept just east of Luganville).

Are you not running the most recent version? Because multiple-hex reactions were fixed.

ORIGINAL: Canoerebel

If carriers can react multiple hexes, you can see that it eliminates the strategy of "keeping the CVEs within close range for mutual air support).

Addressing one of your concerns, my CVEs wouldn't "take the place of AA platforms." They'd supplement. Usually, my carrier TFs have about 15-18 ships. What if I just fill them up to 25 total with the additional CVEs (or, possibly, pull out a few CV/CVL and add in as many CVE and a few DDs to make up 25)?

As for the surface combat threat, the Allies vastly outnumber the Japanese in combat ships. Death Star should have about eight to ten dedicated combat TFs. In the last battle, Erik didn't try for a surface combat engagement. That doesn't mean that he won't this time, but I think the odds are low, and that even if he does he's likely to come out on the short end.

I agree I probably can't win without CVs or if I lose a carrier clash decisively. That's the reason I'm turning over ever stick and leaf trying to figure out a way to maximize the chances that CVEs are there to enhance CAP. The additional 900 fighters (plus some TBM squadrons for ASW support or follow-up naval strikes) offers a tremendous amount of security.

With all of that information, I'd be going for the battle.

Check your version...

This. In the John game you were playing a very old EXE version. Loka is right that the reaction mechanism was fixed by Michael after Loka brought it up and provided a lot of evidence. If this game is using an old EXE your decision is different than if it's current.

[Canoerebel]

This game must be using an old EXE, because my carriers reacted three or four hexes in the previous carrier battle. (I'm computer illiterate, so I don't actually know how to check, but I do know the reaction covered multiple hexes.)

Limiting reaction to just one hex is a most outstanding modification. I look forward to playing an up-to-date game one of these days. It'll be nice not to have to worry about carriers suddenly steaming 200 miles in the wrong direction, against orders, leaving critical combat ships and amphibious TFs unguarded and much-needed CVEs out of position.

Like most players, I hate the old reaction modeling.

[BillBrown]

Here is where you can see the version #
You need to be using version 1126a or above for the different reaction.
This game is using version 1126b

[Canoerebel]

Odd, my info screen shows the right date but no version number.

[BillBrown]

Interesting, I guess it has something to do with the screen resolution.
How about here instead?

[Canoerebel]

Nope. In that place, my screen gives the date (September 17, 2016) but nothing about a version of the game.

[BillBrown]

So strange, I wonder if others see what you do or what I do? Anyway, on with the notes. [:)]

[Mike McCreery]

ORIGINAL: Canoerebel

Nope. In that place, my screen gives the date (September 17, 2016) but nothing about a version of the game.

Your game is so old they hadnt invented versions yet ;]

[Lokasenna]

September 17, 2016, should be the absolute latest beta...

Another place you can check is right-click on the .exe and go to the following (note that I'm in Win7 and it may be slightly different in Win8 or Win10, but you should still be able to find this tab):



If you're not updated, ask Erik to update. Non-negotiable, IMO - besides, he should want it as well. And he's running the latest for my game with him anyway, at his request [;)].

[Lokasenna]

ORIGINAL: Canoerebel

This game must be using an old EXE, because my carriers reacted three or four hexes in the previous carrier battle. (I'm computer illiterate, so I don't actually know how to check, but I do know the reaction covered multiple hexes.)

Limiting reaction to just one hex is a most outstanding modification. I look forward to playing an up-to-date game one of these days. It'll be nice not to have to worry about carriers suddenly steaming 200 miles in the wrong direction, against orders, leaving critical combat ships and amphibious TFs unguarded and much-needed CVEs out of position.

Like most players, I hate the old reaction modeling.

If you were running this game version when the multiple hex reaction happened, I want to see it... I'm pretty certain Michael put a hard stop on limiting the special CV reactions to 1 hex per TF.

As mentioned, I still think reactions only occur at 5-6 hexes (maybe 4 but I don't think so). I've never had them occur at 7 hexes (as either side). Again, I think this is an artifact of legacy coding from WITP with more miles per hex. My multiple reactions occurred because the first reaction put the CV TF within reaction range of a second detected enemy CV TF (I slowed it down and watched the messages individually IIRC; it's been a while. I did put it all on YouTube).

I want to note also that that was the only time I ever had the much-maligned reactions occur (and it worked out for me, really). My advice on that is simply to do what I always did: don't be coy about CV battles. You're either all-in, ensuring it happens, or all-out. Never be a 'tweener.

[BBfanboy]

ORIGINAL: Lokasenna

ORIGINAL: Canoerebel

This game must be using an old EXE, because my carriers reacted three or four hexes in the previous carrier battle. (I'm computer illiterate, so I don't actually know how to check, but I do know the reaction covered multiple hexes.)

Limiting reaction to just one hex is a most outstanding modification. I look forward to playing an up-to-date game one of these days. It'll be nice not to have to worry about carriers suddenly steaming 200 miles in the wrong direction, against orders, leaving critical combat ships and amphibious TFs unguarded and much-needed CVEs out of position.

Like most players, I hate the old reaction modeling.

If you were running this game version when the multiple hex reaction happened, I want to see it... I'm pretty certain Michael put a hard stop on limiting the special CV reactions to 1 hex per TF.

As mentioned, I still think reactions only occur at 5-6 hexes (maybe 4 but I don't think so). I've never had them occur at 7 hexes (as either side). Again, I think this is an artifact of legacy coding from WITP with more miles per hex. My multiple reactions occurred because the first reaction put the CV TF within reaction range of a second detected enemy CV TF (I slowed it down and watched the messages individually IIRC; it's been a while. I did put it all on YouTube).

I want to note also that that was the only time I ever had the much-maligned reactions occur (and it worked out for me, really). My advice on that is simply to do what I always did: don't be coy about CV battles. You're either all-in, ensuring it happens, or all-out. Never be a 'tweener.

My understanding of what Alfred said was that it is one hex per reaction check, up to the available movement range of the TF or a failed react roll, whichever comes first. I thought previously the issue was that only one react check was made which, if passed, allowed full available movement on the react.

[Squamry]

I think I'm just about in the "don't do it" camp. I always run CV/CVLs and CVE seperately but all as air combat TF. I like the fact that some TFs will react and some won't. The key reasons being:

1) Can still co-ordiante strikes across hexes (but at some risk of not).
2) "Leaky CAP" can still cover both hexes
3) Can split enemy strikes across multiple targets so you get benefit of two lots of CAP because of 2.
4) If it does not split then some of yout carriers will survive as they are not tagetted.

I think one of the big differences in the upcoming battle is that you will be gunning for him rather than on the defensive. If you pursuede Erik to upgade the version then definitely don't use mixed TFs and use the reaction to your advantage.

[Canoerebel]

Looks like I am playing the up-to-date version.

The significance of this is that I had a multi-hex carrier reaction, which is contrary to Loka's experience/understsanding of the one-hex limit (supposedly) added via the latest updage (but possibly consistent with BBfanboy's understanding that the change was to create a die-roll check for each hex, meaning a reaction could take place over multiple hexes).

Reaction doesn't happen often, mainly (IMO) because carrier battles are rare. But contrary to some of the posts above, there will come times when, despite your best efforts, seriously adverse reactions will take place that will confound you.

In the carrier battle in this game, Death Star was shepherding empties home from Sikhalin to the Aleutians. I knew Obvert might attack or might not. I was willing to accept battle and had my carriers seriously connfigured for defense (very heavy on fighters, with strike aircraft mainly set for ASW duties). I think Eric used full-speed to close on Death Star. Death Star then fragmented, the CVs reacting mutliple hexes and the CVEs remaining with the Herd. The resulting battle was chaotic, with Erik losing more than 500 strike aircraft while I suffered mortal damage to a CV, the loss of a CVL, and moderate damage to a bunch of other carriers. I came very close to suffering a major loss, so I felt fortunate under all the circumstances.

Reaction is usally bad and sometimes catastrophic.

[Canoerebel]

On 6/7/44, my carriers reacted two hexes from a starting distance of 10 hexes from KB.

This report is found on page 10 of my AAR.

[Canoerebel]

The big carrier battle happened on 6/16/44 (page 12 of this AAR).

As best I can tell from this screenshot, my carriers again reacted two hexes, beginning at a range of 5 hexes from KB. My CVEs didn't react.

[Canoerebel]

If we were using 26b at the time of these two battles (I'm sure we were, as I installed this at start and haven't done any upgrades since then), then these two clashes suggest that two things offered as "certain" aren't:

1. Reaction Takes Place When Carriers are 5 to 6 Hexes Apart. Incorrect: reaction can take place at a variety of separation, including 5 to 10 hexes, as shown in these two examples.
2. Reaction Is Limited to a Single Hex. Incorrect: reaction can take place over multiple hexes, in both of these instances being two hexes.

[HansBolter]

I still think reaction is limited to one hex PER reaction and you had TFs that reacted twice.

I have seen this quite a bit and had it happen recently in my Mariana's operation.

You will be get two separate flash messages that a reaction is occurring, one for each instance of reaction.

Just a nuance as the practical result is two hexes of reaction no matter how it shakes out.

I have had two hexes of reaction in the morning and another two in the afternoon leaving a four hex spread on my TFs by day's end.

[Lokasenna]

ORIGINAL: BBfanboy

ORIGINAL: Lokasenna

ORIGINAL: Canoerebel

This game must be using an old EXE, because my carriers reacted three or four hexes in the previous carrier battle. (I'm computer illiterate, so I don't actually know how to check, but I do know the reaction covered multiple hexes.)

Limiting reaction to just one hex is a most outstanding modification. I look forward to playing an up-to-date game one of these days. It'll be nice not to have to worry about carriers suddenly steaming 200 miles in the wrong direction, against orders, leaving critical combat ships and amphibious TFs unguarded and much-needed CVEs out of position.

Like most players, I hate the old reaction modeling.

If you were running this game version when the multiple hex reaction happened, I want to see it... I'm pretty certain Michael put a hard stop on limiting the special CV reactions to 1 hex per TF.

As mentioned, I still think reactions only occur at 5-6 hexes (maybe 4 but I don't think so). I've never had them occur at 7 hexes (as either side). Again, I think this is an artifact of legacy coding from WITP with more miles per hex. My multiple reactions occurred because the first reaction put the CV TF within reaction range of a second detected enemy CV TF (I slowed it down and watched the messages individually IIRC; it's been a while. I did put it all on YouTube).

I want to note also that that was the only time I ever had the much-maligned reactions occur (and it worked out for me, really). My advice on that is simply to do what I always did: don't be coy about CV battles. You're either all-in, ensuring it happens, or all-out. Never be a 'tweener.

My understanding of what Alfred said was that it is one hex per reaction check, up to the available movement range of the TF or a failed react roll, whichever comes first. I thought previously the issue was that only one react check was made which, if passed, allowed full available movement on the react.

No, it was 1 hex per special CV TF reaction. I don't know if this was limited by total movement at all (i.e., if you moved at full speed and full distance for 2 phases, I think you could still react).

I'm also not entirely sure what Alfred said applies pre-fix. I think what he said (without looking it up) reflects what the intent was, but there was a clear bug that was causing TFs to react multiple times. Here's my thread: www.matrixgames.com/forums/tm.asp?m=3981268&mpage=1

Here are Michael's notes on what he changed:

19/12/2015 [1125.7]
tweak exclude CVTF with no attack groups from closing with enemy CVTF
tweak DL on enemy CVTF to be 3+ to trigger CV reaction; was non-zero DL
fix CVTF reported reacting to enemy CVTF more than once per phase

10/01/2016 [1125.9]
Tweak to use number of attack planes rather than groups for CV closure

That pretty clearly says reactions of only once per phase, as well as 2 other new restrictions based on DL and bombers available. Presumably, you could react in both AM and PM phases - maybe that is what you saw, CR?

To really tell, you would need to re-watch the replays and pay close attention to the messages.

ORIGINAL: HansBolter

I still think reaction is limited to one hex PER reaction and you had TFs that reacted twice.

I have seen this quite a bit and had it happen recently in my Mariana's operation.

You will be get two separate flash messages that a reaction is occurring, one for each instance of reaction.

Just a nuance as the practical result is two hexes of reaction no matter how it shakes out.

I have had two hexes of reaction in the morning and another two in the afternoon leaving a four hex spread on my TFs by day's end.

It should be 1 hex per phase, per TF, full stop. If you can document otherwise, that's a bug (which will unfortunately probably go unfixed at this point).

[Lokasenna]

ORIGINAL: Canoerebel

If we were using 26b at the time of these two battles (I'm sure we were, as I installed this at start and haven't done any upgrades since then), then these two clashes suggest that two things offered as "certain" aren't:

1. Reaction Takes Place When Carriers are 5 to 6 Hexes Apart. Incorrect: reaction can take place at a variety of separation, including 5 to 10 hexes, as shown in these two examples.
2. Reaction Is Limited to a Single Hex. Incorrect: reaction can take place over multiple hexes, in both of these instances being two hexes.

Again, wondering if you saw reaction in AM and then in PM. It's possible that the times my CVs didn't react at 7 hexes were flukes (or that your reactions at >6 hexes were flukes).

Either way, I've been saying the whole time that you need to be getting close (under 6 hexes) or avoiding battle. You can't predict exactly where he's going to end up 99 times out of 100, so if you're looking for a battle you need to be sure. Hence, plan for being about 5 hexes away.