Slitherine

• How could a HQ provide support to a unit in the same hex it is in ("in ... the target hex") without having its own hex being attacked ?

• Does it mean that 1 division = 2 divisions = 1 corps or army = 1 unit ?

• How could a carrier plane be out of range if the port is adjacent to any hexdot in the sea area ?

quote:

ORIGINAL: Caquineur

Hello everyone,

Could you help to become by answering those questions ?

11.16.3 HQ support (option 13)
Support
After all land attacks are declared, the inactive side announces HQ support for target hexes. You can only allocate 1 face-up HQ to support each hex. It must be in, or adjacent to, the target hex. It can’t provide support to a unit it does not co-operate with, to an adjacent hex if it is separated from it by an impassable hexside, or if its own hex is also being attacked.

• How could a HQ provide support to a unit in the same hex it is in ("in ... the target hex") without having its own hex being attacked ?

11.16.5 Resolving attacks
AsA/MiF/PoliF option 2: Divisions count as 1/2 a unit (rounding up).

• Does it mean that 1 division = 2 divisions = 1 corps or army = 1 unit ?

14.4 CV units
A carrier plane can fly a mission to any hex in range. Measure the range from any hex-dot in the CV’s sea area (it’s usually best to pick the hex-dot closest to your target). A carrier plane can fly, and return from, a port attack mission that is out of range, if the port is adjacent to any hexdot in the sea area.

• How could a carrier plane be out of range if the port is adjacent to any hexdot in the sea area ?

Thanks for your help, gentlemen - of course, should there be a member of the gentler gender here, do not hesitate to speak

Alain

quote:

Alain, my interpretation:

A HQ can give HQ support to the hex where it is or any adjacent hex. Exception: If the HQ hex is being attacked at the same time, then it cannot give HQ support to the adjacent ( I think it could give to it`s own hex however).

quote:

2- A division counts like 1/2 corps. It means:

2 corps = 2 units.
2 corps + 1 div = 2,5 units=3 units.
2 corps + 2 div = 3 units.

quote:

ORIGINAL: Caquineur

quote:

Alain, my interpretation:

A HQ can give HQ support to the hex where it is or any adjacent hex. Exception: If the HQ hex is being attacked at the same time, then it cannot give HQ support to the adjacent ( I think it could give to it`s own hex however).

Muchas gracias, José Ignacio.

Now that I've read your answer, it seems quite obvious. I really should stop seeing problems where there aren't any...

Alain

quote:

2- A division counts like 1/2 corps. It means:

2 corps = 2 units.
2 corps + 1 div = 2,5 units=3 units.
2 corps + 2 div = 3 units.

quote:

As for the thid one, I have been trying to see a map online but I guess it is about one fleet, for example close to the notrh pole that sends a plane from a carrier to a hexdot adjacent to a port like Arkhangelsk (I cannot see the map so I don't know if thi is possible), the bomber would not need to be able to reach arkhangelsk, but only the hexdot adjacent. It needs only to reach the hexdot to be able to attack any of the ports that are adjacent to it.

quote:

quote:

OK, so I guess the formula "1 division = 2 divisions = 1 corps or army = 1 unit" is OK.

Alain

It depends. Is ok as far as there are no more divisions involved. If any, then you need to sum them all as 0,5 corps and the round the result up.

1 division= 2 divisions= 1 corps
2divisions= 1 corps
3 divisions= 4 divisions= 2 corps

...

quote:

I think the rule means that the plane would be out of range to reach the port

quote:

ORIGINAL: Greywolf

For a CvP to be out of range is fairly easy, some old CvP have very small ranges, and a hexagone in the outside Box is 4 hex away in range (IIRC), Pacific/Asia map is 2 hex, so the CvP could be out of range of the adjacent hexes without the rule clarification.

quote:

ORIGINAL: Caquineur

OK thanks, I think I understand now : the range is reduced as specified in "11.3 Naval air missions" : "...Reduce its range by the same number it would have cost to enter the section it came from (i.e. 10 from the 4 section, 6 from the 3 section, and so on)".

I had completely forgotten that.

Thank you both for your help !

quote:

ORIGINAL: lavisj

This does not apply to CVP, but to planes moving from a Sea Box back to land during naval air missions.
CVP start at the hex dot, and do not have to count from their sea box. (14.4).

You were correct previsouly in the fact that a CVP will always be in range of a hex bordered by a hex dot in the sea zone the CVP is in.

Jerome

quote:

ORIGINAL: Greywolf

It is NOT useless in WiF, it is useless in MWiF wich have a one size all hexagone.

In boardgame WiF certain hexes on certain map count for more than one hex of range...

quote:

ORIGINAL: Greywolf

For a CvP to be out of range is fairly easy, some old CvP have very small ranges, and a hexagone in the outside Box is 4 hex away in range (IIRC), Pacific/Asia map is 2 hex, so the CvP could be out of range of the adjacent hexes without the rule clarification.

quote:

ORIGINAL: Greywolf

It is NOT useless in WiF, it is useless in MWiF wich have a one size all hexagone.

In boardgame WiF certain hexes on certain map count for more than one hex of range...

quote:

ORIGINAL: Caquineur

quote:

ORIGINAL: lavisj

This does not apply to CVP, but to planes moving from a Sea Box back to land during naval air missions.
CVP start at the hex dot, and do not have to count from their sea box. (14.4).

You were correct previsouly in the fact that a CVP will always be in range of a hex bordered by a hex dot in the sea zone the CVP is in.

Jerome

Thanks, Jerome !

So, if I understand you correctly, the sentence "A carrier plane can fly, and return from, a port attack mission that is out of range, if the port is adjacent to any hexdot in the sea area." is useless, and could be left out in RAW future editions and RAC ?

quote:

Unlike other wargames, the hexes stop at the coastlines. Hexes at sea are replaced by hex-dots - each hex-dot is at the centre of what would otherwise be a hex. When moving an aircraft unit across hex-dots, or when counting hexes, just imagine you are moving from hex to hex.
Example:

The use of hex-dots is partly aesthetic but also serves to show that the presence of land units is not permitted.

Some hex-dots are “large” hex-dots. Only large hex-dots are adjacent to off-map hexes. So, you can only move between a hex-dot and an off-map hex if the hex-dot is large. Large hex-dots can also be adjacent to normal hexes or normal hex-dots.

quote:

ORIGINAL: Joseignacio
A fleet is blocked in a port where all his exits to sea/s are blocked by enemy ships, outside his home country. Thus, it's unsupplied. A new ship of the same nationality of that fleet appears from another port and gets in one of these seas. Now the fleet in prot is supplied.

Could the fleet inside the port move normally? We have been playing like it can, however, I think maybe it's not correct since all the naval movements need to be done in the naval phase, and so they would be simultaneous. If they are simultaneous, the new ship cannot supply the fleet before they move.

quote:

ORIGINAL: Shannon V. OKeets

No.

First of all, for an air unit at sea to fly an air mission to a land hex (e.g., ground strike) it must be either: (1) an organized carrier air unit on-board a carrier or (2) an organized carrier when you are playing without the optional rule Carrier Air Units. In the latter case, MWIF generates a 'temporary' carrier air unit to fly the mission. What we are talking about here are carrier air units at sea flying missions to land hexes.

The sea box section the carrier is in has no effect on determining the range of the air unit.

Some land hexes are considered 'adjacent' to a sea area even though the land hex is not adjacent to an all sea hex dot. For example, London, Hamburg, ... If you count the number of hexes from the closest all sea hex dot to the target hex it can be 2, 3, 4 or more(?). In those situations, even air units without sufficient range (counting from the closest all sea hex dot) are permitted to fly the air mission (to and from) if the target hex is 'adjacent'.

quote:

ORIGINAL: paulderynck

quote:

ORIGINAL: Shannon V. OKeets

No.

First of all, for an air unit at sea to fly an air mission to a land hex (e.g., ground strike) it must be either: (1) an organized carrier air unit on-board a carrier or (2) an organized carrier when you are playing without the optional rule Carrier Air Units. In the latter case, MWIF generates a 'temporary' carrier air unit to fly the mission. What we are talking about here are carrier air units at sea flying missions to land hexes.

The sea box section the carrier is in has no effect on determining the range of the air unit.

Some land hexes are considered 'adjacent' to a sea area even though the land hex is not adjacent to an all sea hex dot. For example, London, Hamburg, ... If you count the number of hexes from the closest all sea hex dot to the target hex it can be 2, 3, 4 or more(?). In those situations, even air units without sufficient range (counting from the closest all sea hex dot) are permitted to fly the air mission (to and from) if the target hex is 'adjacent'.

Steve, this is not correct for RAW and I hope not implemented the way you say in MWIF. The rule was only for port strikes on maps where the first hex adjacent to a hexdot cost more than 2 movement points for planes if playing with CVPs or cost more than the CV's nominal air component range if playing without CVPs. Since MWIF is universal one-hex scale, then ranges are what they are and many air missions cannot be flown farther than the range of the aircraft - except port strikes.

Edit: upon further reflection the original rule in RAW was to always allow a port strike if the target hex was adjacent to a sea dot. But if it was more than a hex away then you counted range. So a CVP or a 'nominal' CVP could make a port strike on a port adjacent to its sea area even if on the America mini-map where you'd normally count 6 to a ground strike target for example. But in MWIF, all adjacent ports to a sea dot will automatically be a range of one from the carrier, so this rule is not needed at all in MWIF. Any port that is more than one hex away from a sea dot should require a range check if a port strike is attempted.

quote:

ORIGINAL: Shannon V. OKeets
The adjacent to the sea area check is only for port attacks. It is just 3 lines of code, so if Patrice agrees, I'll remove them.

quote:

ORIGINAL: Froonp

quote:

ORIGINAL: Shannon V. OKeets
The adjacent to the sea area check is only for port attacks. It is just 3 lines of code, so if Patrice agrees, I'll remove them.

RAW 14.4 :
******************************
A carrier plane can fly a mission to any hex in range. Measure the range from any hex-dot in the CV’s sea area (it’s usually best to pick the hex-dot closest to your target). A carrier plane can fly, and return from, a port attack mission that is out of range, if the port is adjacent to any hexdot in the sea area.
******************************

But for sure, if the port is adjacent to a sea dot, it is in range of any CVP with the use of the MWiF map.
So I think I agree.

quote:

ORIGINAL: gogol1st

Hi guys.

i have a question about the rules too.
my question is simple :

if i attack a stack of 2 units in which one is face up and the other is face down, do i still have a +1 DRM to my attack roll ?


thank you