F&E Q&A Discussions

Star Fleet Universe Discussion Board: Federation & Empire: F&E QUESTIONS: F&E Q&A Discussions
  Subtopic Posts   Updated
Archive through February 18, 2013  25   02/18 09:36pm
Archive through March 06, 2013  25   03/06 10:14pm
Archive through March 15, 2013  25   03/15 06:46pm
Archive through March 19, 2013  25   03/19 08:33pm
Archive through March 28, 2013  25   03/28 03:56pm
Archive through April 04, 2013  25   04/04 07:49am
Archive through April 04, 2013  25   04/04 07:49pm
Archive through April 09, 2013  25   04/09 09:00pm
Archive through April 17, 2013  25   04/17 01:37pm
Archive through May 05, 2013  25   05/05 10:53pm
Archive through May 27, 2013  25   05/27 10:28am
Archive through June 18, 2013  25   06/18 11:58pm
Archive through June 19, 2013  25   06/19 02:04pm
Archive through June 20, 2013  25   06/20 02:24pm
Archive through June 28, 2013  25   06/28 10:57pm
Archive through August 18, 2013  25   08/18 06:54pm
Archive through September 10, 2013  25   09/10 08:41pm
Archive through September 20, 2013  25   09/20 03:39pm
Archive through October 06, 2013  25   10/06 09:37pm
Archive through November 12, 2013  16   11/12 08:30am
Archive through November 15, 2013  25   11/15 05:45pm
Archive through December 20, 2013  24   12/20 05:24pm
Archive through December 29, 2013  25   12/29 12:31pm
Archive through January 06, 2014  25   01/06 09:56am
Archive through January 13, 2014  25   01/13 10:40pm
Archive through February 03, 2014  25   02/03 03:53pm
Archive through March 05, 2014  25   03/05 07:58pm
Archive through March 19, 2014  25   03/19 11:51am
Archive through April 11, 2014  25   04/11 09:00pm
Archive through April 24, 2014  25   04/24 12:18pm
Archive through May 16, 2014  25   05/16 10:38am
Archive through May 26, 2014  25   05/26 10:30am
Archive through July 03, 2014  25   07/03 04:41pm
Archive through July 20, 2014  25   07/20 02:15pm
Archive through July 25, 2014  25   07/25 09:03pm
Archive through July 29, 2014  25   07/29 06:26am
Archive through August 11, 2014  25   08/11 12:40am
Archive through September 03, 2014  25   09/03 02:14pm
Archive through September 15, 2014  25   09/15 06:06pm
Archive through September 24, 2014  25   09/24 11:47pm
Archive through October 29, 2014  25   10/29 09:55am
Archive through November 05, 2014  25   11/05 01:07pm
Archive through November 22, 2014  25   11/22 02:45am
Archive through December 11, 2014  25   12/11 03:48pm
Archive through December 15, 2014  25   12/15 04:20am
Archive through January 02, 2015  25   01/02 03:43am
Archive through February 04, 2015  25   02/04 07:26pm
Archive through February 11, 2015  25   02/11 08:27pm
Archive through March 09, 2015  25   03/09 08:38pm
Archive through March 25, 2015  25   03/25 12:31pm
Archive through April 07, 2015  25   04/07 09:01am
Archive through April 17, 2015  25   04/17 08:19pm
Archive through April 23, 2015  25   04/23 09:10am
Archive through May 11, 2015  25   05/11 03:12pm
Archive through June 19, 2015  25   06/19 06:28am
Archive through July 05, 2015  25   07/05 11:43pm
Archive through July 22, 2015  25   07/22 07:26pm
Archive through November 02, 2015  25   11/02 03:53pm
Archive through May 31, 2016  25   05/31 06:23pm
Archive through June 20, 2016  25   06/20 07:04pm
Archive through August 26, 2016  31   08/26 03:26pm
Archive through December 06, 2016  25   12/06 10:25am
Archive through April 15, 2017  25   04/15 11:10am
Archive through June 08, 2017  25   06/08 07:30am
Archive through June 23, 2017  25   06/23 11:41pm
Archive through July 11, 2017  25   07/11 08:43pm
Archive through July 27, 2017  25   07/27 11:09am
Archive through July 29, 2017  25   07/29 01:52pm
Archive through August 21, 2017  25   08/21 11:44am
Archive through September 05, 2017  27   09/05 01:27pm
Archive through October 14, 2017  25   10/14 01:28pm
Archive through October 16, 2017  25   10/16 05:03pm
Archive through December 01, 2017  25   12/01 10:49pm
Archive through July 05, 2018  25   08/07 08:26pm
Archive through October 05, 2018  25   10/06 04:58am
Archive through November 03, 2018  25   11/06 04:49am
Archive through November 18, 2018  25   11/19 04:48am
Archive through February 12, 2019  25   02/13 05:04pm
Archive through February 14, 2019  25   02/14 04:32pm
Archive through March 11, 2019  25   03/27 11:15am
Archive through March 30, 2019  25   03/30 09:57pm
Archive through May 20, 2019  25   05/21 12:08pm
Archive through June 03, 2019  25   06/03 04:54pm
Archive through June 30, 2019  25   07/01 02:07am
Archive through July 12, 2019  25   07/14 04:42am
Archive through July 22, 2019  26   07/22 03:58pm
Archive through July 26, 2019  25   07/29 11:56pm
Archive through August 02, 2019  25   08/02 04:32pm
Archive through August 08, 2019  25   08/08 12:35pm
Archive through August 09, 2019  25   08/11 05:45pm
Archive through August 17, 2019  25   08/19 01:33pm
Archive through August 29, 2019  25   09/01 07:09pm
Archive through September 28, 2019  25   09/29 12:40am
Archive through October 14, 2019  25   10/15 08:15am
Archive through October 28, 2019  25   10/28 02:57pm
Archive through November 18, 2019  25   11/24 06:10pm
Archive through December 16, 2019  25   12/16 11:00pm
Archive through January 06, 2020  25   01/07 06:31am
Archive through January 13, 2020  25   01/13 11:42pm
Archive through January 21, 2020  25   01/22 01:16pm
Archive through January 23, 2020  25   02/14 09:29am
Archive through February 19, 2020  25   02/20 06:35pm
Archive through March 03, 2020  25   03/03 08:56pm
Archive through March 07, 2020  25   03/07 03:58pm
Archive through April 03, 2020  25   04/04 03:22am
Archive through May 13, 2020  25   05/19 10:01am
Archive through June 18, 2020  25   06/18 03:08pm
Archive through June 28, 2020  25   06/29 07:30pm
Archive through August 06, 2020  25   08/14 02:51pm
Archive through September 04, 2020  25   09/09 04:39am
Archive through September 11, 2020  25   09/12 12:05pm
Archive through September 19, 2020  25   11/26 08:51am
Archive through December 07, 2020  25   01/30 10:25am
Archive through February 27, 2021  25   03/06 05:44pm
Archive through April 04, 2021  25   04/30 02:43am
Archive through May 15, 2021  25   05/22 12:43pm
Archive through June 01, 2021  25   06/02 02:27pm
Archive through June 03, 2021  25   06/04 12:09pm
Archive through June 08, 2021  25   06/09 12:17pm
Archive through July 18, 2021  25   07/21 03:08pm
Archive through July 26, 2021  25   07/31 10:53am
Archive through August 30, 2021  25   08/31 11:46am
Archive through September 08, 2021  25   09/09 06:34pm
Archive through November 03, 2021  25   11/24 10:13pm
Archive through December 07, 2021  25   01/08 11:16pm
Archive through January 11, 2022  25   01/12 05:58pm
Archive through January 16, 2022  25   01/17 12:03pm
Archive through February 11, 2022  25   02/12 01:09pm
Archive through February 19, 2022  25   02/20 06:51pm
Archive through March 15, 2022  25   03/18 09:04am
Archive through March 24, 2022  25   03/24 03:05pm
Archive through March 28, 2022  25   03/29 09:18pm
Archive through May 09, 2022  25   05/10 11:34am
Archive through May 24, 2022  25   05/24 05:09pm
Archive through June 06, 2022  25   06/18 09:01pm
Archive through July 12, 2022  25   07/14 03:25am
Archive through September 15, 2022  25   09/21 06:49pm
Archive through October 31, 2022  25   11/02 06:30pm
Archive through December 01, 2022  25   12/04 02:47pm
Archive through February 18, 2023  25   02/18 01:29pm
Archive through March 02, 2023  25   03/15 05:32pm
Archive through April 08, 2023  25   04/08 06:30pm
Archive through June 30, 2023  25   08/14 11:22pm
Archive through January 01, 2024  25   01/11 11:51pm
Archive through February 10, 2024  25   03/02 07:24am
Archive through April 17, 2024  25   04/24 06:16pm
Archive through May 25, 2024  25   05/27 07:28pm
Archive through August 19, 2024  25   08/20 06:40pm
Archive through October 10, 2024  25   11/14 08:22pm
Archive through January 08, 2025  25   01/11 01:28am
Archive through February 16, 2025  25   03/23 11:06pm
Archive through July 27, 2025  25   08/18 01:54am
Archive through October 06, 2025  25   10/07 10:46am
Archive through December 05, 2025  25   02/26 02:44pm

This topic is administered by FEAR and FEDS.

Please post supporting or dissenting information about F&E questions in this topic. If you would, please refer to the rule in question in your post so that it is easily referenced.

Thanks for your cooperation in this new way of handling questions and the discussion. We hope that this will let people find the answers to questions more easily while still encouraging discussion.
By Paul Howard (Raven) on Saturday, December 06, 2025 - 11:05 am: Edit

John

I beleive the intent is that the Expeditionary Fleet Tug - which is initially set up as the Expeditionary Supply Tug - can eiher remain in that roll for the entire game - or can switch to any other permitted Tug mission and then is used as a normal Tug.

However, if it does that, it can never go back to the Expeditionary Supply Tug mission.

i.e - it's single option to change and is permmanent.

(In effect, it's like the Klingon CVT 'Tugs' - they can be changed to a TGA, but the 'pods' they had are permamently lost)

By Ted Fay (Catwhoeatsphoto) on Monday, December 22, 2025 - 11:22 am: Edit


Quote:

By Sean Dzafovic (Sdzafovic) on Monday, December 22, 2025 - 09:23 am: Edit

The Kzinti capital is captured by the Coalition. They relocate the shipyard to the offmap.

If they subsequently recapture the capital hex, is Kzintai a "capital" planet for purposes of PDUs (ie: max 20)? Or a major since it's where the capital and shipyard are currently located?




Sean,

Not an official answer, but I believe the answer is "no."

433.424 states that "capital planets cannot have more than 20 PDUs". Other planets will have fewer (10 or 6, for major and minor planets, respectively).

The issue here is not the shipyard. The issue is what is the "capital." If Kzinti was lost at some point, then a new capital planet or starbase must have been declared when Kzintai was captured. See 511.31. In either case, the "capital" is no longer Kzintai. Therefore, the recaptured Kzintai could support no more than 10 PDUs as an "ordinary" major planet.

Note that this conclusion is supported by 511.61. You may voluntarily abandon the capital, but doing so has serious consequences (one of which is to designate a new capital). Nevertheless, you *could* "abandon" the new (presumably offmap) capital and re-declare the recaptured Kzintai as the "new" capital. NOW you could build 20 PDUs on the re-designated new capital.

In other words, once a capital is established, the only way to change the capital is by means of 511.61. Ergo, it is clear (in my opinion) that the recaptured Kzintai is NOT a "capital" and therefore may not host 20 PDUs - unless - the Kzinti abandon the offmap capital and re-establish it on the recaptured Kzintai (with all attendant consequences).

FEDS or FEAR (or possibly SVC) to confirm, deny, or modify as an official answer. While I'm staff now, I don't have authority to give authoritative rulings.

F&E JAG

By James McCubbin (Kimokhan) on Friday, January 02, 2026 - 03:30 pm: Edit

My apologies but I could not find this anywhere.

The Romulans have gotten in range to raid the Fralli cruiser and did 2 casualty points which destroyed it since it cannot move.
There is no build cost and the conversion cost is not possible either (due to no such thing as a crippled POL, or just even having those other crippled ships in the area). We ended up saying to make a crippled CL just build it for 3 points, a crippled FF is 2 points and the non-existent crippled POL is 1 point + 3 conversion = 9 points.

Is it really indented to give the Romulans a 9 point economic raid each turn?

What is the intended effect and replacement costs?

By Ryan Opel (Feast) on Friday, January 02, 2026 - 06:46 pm: Edit

Or you just ignore the Fralli's existence.

It's more a nod to a ADB staffer thana serioud ship.

By John M. Williams (Jay) on Thursday, February 26, 2026 - 02:44 pm: Edit

We're playing the Long-Distance War and treating all the Lyran and Klingon bases and planets as neutral outposts to be eliminated/conquered.

If Player A attacks a neutral planet, rule 503.63 allows Player B to assist in the defense of that planet (either via reaction or sending a reserve fleet).

Rule 503.633 says that if Player A is forced to retreat off the hex, then Player B's ships may remain in the hex. However, the rule also says that if Player B's forces don't move off the planet during their next movement phase, then they are considered to be attacking the planet.

If Player B does decide to attack that planet during his next turn, does that trigger an opportunity for Player A to react ships into the hex? Technically, Player B's ships haven't moved, but this switch from being defender to attacker seems material enough that an opportunity to react to it sounded reasonable. In discussing how to handle this, we noted that the "march in place" option under 203.64 is another situation where reaction is possible, even though actual movement did not occur.

I did a search on 503.633 and didn't find anything. I assume that this is an odd enough situation that it may not have come up before.

What are other people's thoughts?

By Stewart Frazier (Frazikar3) on Thursday, February 26, 2026 - 07:43 pm: Edit

Note that (503.63) says that if one side is attacking, the other may defend it. Doesn't matter how the 'attacker' got there, just that there is an attacker …

By Ted Fay (Catwhoeatsphoto) on Sunday, March 22, 2026 - 10:15 pm: Edit

Comment on Ken Kazinski's question in the Q thread:

Interceptors are not reflected in F&E. Their existence is wrapped up into the abstraction of the defined turns of PF introduction, AFAIK. So, I don't think that would affect the ruling.

Good thought, though.

By John M. Williams (Jay) on Friday, April 24, 2026 - 11:21 am: Edit

A tug is setting up a mobile base and is attacked.

After the approach battle is resolved, the attacker wishes to attack the tug setting up the MB. Rule 302.233 says the tug must be included in the battle force and that the tug counts against command limits.

Rule 510.231 says that the base (combat factor zero) must also be in the battle force. Does it also count against command limits? The implication seems to be "yes," but it is not explicitly stated.

By Ryan Opel (Ryan) on Friday, April 24, 2026 - 05:51 pm: Edit

Bases don't count against command limits.

(302.335) Bases, convoys, PDUs, and FRDs required to be included in the Battle Force (302.23) do not count against the Command Rating.

By John M. Williams (Jay) on Friday, April 24, 2026 - 10:24 pm: Edit

If it doesn't count against command limits, what is the practical effect of requiring it to be in the battle force? I don't see one. If the attacker could direct at it, then there would be one. However, the attacker can only direct at the tug. As I see it, if it doesn't count against the command rating, then whether it is in the battle force or not has no practical consequence.

By Ryan Opel (Ryan) on Friday, April 24, 2026 - 11:16 pm: Edit

Because the tug has to be in the battle force, so then the deploying base has to be in the battle force. Otherwise the base is considered abandoned and automaticly destoryed.

By Paul Howard (Raven) on Saturday, April 25, 2026 - 07:43 am: Edit

John

To add to what Ryan said - remember, a Tug is also required to upgrade a base and so in effect the rule covers two aspects : -

1) MB being emplaced by the Tug - so the Base has zero compot and is it's concsidered a base, is not included from Command Rating purpose - but the Tug does need to be included (and it's Compot counts - and it counts towards Command Rating - unless it's the Flagship etc)

1) A Base is being upgraded by the Tug - so the Base has the unupgraded compot included and as it is base, is not included from Command Rating purpose - but the Tug does need to be included (and it's Compot counts - and it counts towards Command Rating - unless it's the Flagship etc)

The only two diffences are, the being emplaced MB will always have 0 Compot - and base being upgraded could be the Flagship for the Force.

So bases are always free for Commmand Limit purposes :) (noting the Dual Location Base Rule can also apply!)

By Mike Erickson (Mike_Erickson) on Saturday, April 25, 2026 - 12:17 pm: Edit

And to John's point, forcing a 0 combat contributing base in progress to be in the battle force is indeed a rule, but it adds no combat value to the battle force itself. So it is largely inconsequential. The tug will be the focus of enemy action if the goal is to stop the base from being setup.

--Mike

By John M. Williams (Jay) on Tuesday, April 28, 2026 - 10:52 pm: Edit

I have a retreat question.

Suppose the Feds and Gorns fight the Romulans in 4309 and decide to retreat. The nearest Gorn base is in 4004; the nearest Fed bases are 3804, 3806, and 3808. There is a small, unresolved battle in 4208 (small enough that Priority 2 will not apply).

Under sub-priority 3D, the shortest Gorn supply path requires retreating into 4308 or 4208, and the shortest Fed supply path requires retreating in 4208 or 4209. All these hexes would be in supply for their respective empire.

The last sentence of the first paragraph of 302.761 says that if two allies can retreat to the same hex after applying the four priorities, they must do so.

Both the Feds and Gorns can retreat to 4208, but in each individual case, it would be a fighting retreat.

Given this situation, what should happen?

A: Because both the Gorns and Reds can retreat to 4208, they must do so. Because that is the only hex that satisfies sub-priority 3D for both empires, it is not a fighting retreat.

B: Because both the Gorns and Feds can retreat to 4208, they must do so. Because that would be a fighting retreat for each empire individually, it is fought as a fighting retreat.

C: The Gorns and Feds may retreat separately into 4308 and 4209 or may retreat together into 4208 as a fighting retreat.

By Paul Howard (Raven) on Wednesday, April 29, 2026 - 07:15 am: Edit

John

Fighting retreat is always optional - so neither 'has' to go to 4208.

4 Outcomes
A) Alliance Fighting Retreats to 4208
B) Feds go to 4209 and Gorns go to 4308
C) Alliance goes to 4209* OR
D) Alliance goes to 4308*

* - You and retreat all under the Flagship of the last battle force - so if it was a Gorn Flagship in 4309, A,B or D is an option - if it was a Federation Flagship in 4309, A, B or C is an option.


I don't know if Fighting Retreat just one Allied Memmber to 4208 and the other retreats normally is allowed - I can't remember which rule (Fighting Retreat is always optional v Retreat to same hex if that is possible trumps the other rule).

By Steve Cole (Stevecole) on Wednesday, April 29, 2026 - 12:27 pm: Edit

MEMO TO STAFF, something to address in your project.

By John M. Williams (Jay) on Wednesday, April 29, 2026 - 03:58 pm: Edit

To be sure I understand your option C and D:

Option C (Fed flagship): all ships may retreat to 4209, even though this means the Gorns would be violating sub-priority 3D.

Option D (Gorn flagship): all ships may retreat to 4308, even though this means the Feds would be violating sub-priority 3D.

I know that fighting retreats are always optional, but sometimes retreating towards supply requires retreating into a hex that already has enemy ships. For example, after a battle in 902, the Kzintis may be required to retreat onto a smaller force garrisoning the planet in 1001 because that is the only hex allowed by sub-priority 3D. In which case, it is not a fighting retreat.

In the scenario I described, I wasn't sure if 4208 stopped being a fighting retreat because it was the only hex that allowed both empires to retreat together and still satisfy sub-priority 3D.

By Patrick Sledge (Decius) on Wednesday, April 29, 2026 - 04:27 pm: Edit

John

Essentially, the retreating force has a choice under (302.76):

Evaluate retreat for the entire force as a whole based on (302.73) using the priorities of the empire that provided the last flagship

OR

Evaluate retreat for each empire separately based on (302.73).

If the entire force retreats together based on the flagship, there's no 'second' evaluation of (302.73) criteria for the other empire.

As for your question, I'm pretty sure 4208 is still a fighting retreat, since the restriction in (302.761) explicitly applies only after all retreat priorities have been run (and the retreating units have either chosen to exclude 4208 under Priority 4 or not).

Amusingly, it's theoretically possible for the Gorn and Federation to make different choices in regards to Priority 4. This would result in one taking the fighting retreat and the other eliminating hex 4208, and the forces ending up in separate places without violating (302.761) .

By Paul Howard (Raven) on Thursday, April 30, 2026 - 03:42 am: Edit

John

Yes - as if they retreat with their 'Allies' - their supply requirement is ignored at that point in time.

i.e. if they all retreat to 4209 under a Federation Flagship, they are required to folow the Federation retreat priorities.

(In effect it's a choice and you use which ever rule is most appropriate).

By Lawrence Bergen (Lar) on Friday, May 01, 2026 - 10:11 am: Edit

Suppose the Feds and Gorns fight the Romulans in 4309 and decide to retreat.
The nearest Gorn base is in 4004; the nearest Fed bases are 3804, 3806, and 3808.
There is a small, unresolved battle in 4208 (small enough that Priority 2 will not apply)


Lets look at the facts compared to the rules and use the Retreat checklist found over on the Warbook annex page.

First there are some stipulations to discuss when looking at a retreating allied force.
When any ally from a combined force retreats, all must go (no partial retreats outside of a capital hex which is not the case here).
Under (302.76) allied forces they must remain together and use the priorities of the force who either provided the flagship of the last battle round, the withdraw before combat (or in a partial retreat from a capital, again not the case those that first retreated from the hex).
Allies that are not the lead role here in this retreat may have to retreat out of supply when following supply of their ally.
There is an exception: Allied forces may choose to retreat separately following the priority steps.
Even if separate paths are chosen then all ships of the same empire must go to the same location i.e. no splitting of an empire's forces. (Sending some ships to their own hex while allowing some to go with their ally is not allowed).
Check both allies priority options. IF there is an overlapping hex (or hexes) when priorities are determined then both allies must go together to one hex.

Facts provided:
Combat is at Minor Planet 4309
Gorn closest supply point 4004 (5 hexes distance).
Assumed there must be something blocking the Gorn from BTS 4203 or their Capital in 4403(?)
Fed closest supply points are bases 3808, 3806 (5 hexes distance) 3804 (6 hexes distance).
Notes: There is no information provided as to the condition of the Romulan border bases so I am assuming they are all intact.
From Johns information it is also assumed no ship withdrew from combat previous to the combat and subsequent retreat step or the hex would have already been decided under (302.134).

Assuming John wants to look at the separate retreat force option.

Priority 1: Future Belligerent/Neutral There is no possibility from this battle hex to retreat into a Neutral territory/Future belligerent for either of his allies (Fed or Gorn). Move on to Priority 2.

Priority 2: Outnumbered Force "There is a small, unresolved battle in 4208 (small enough that Priority 2 will not apply)" Without a count provided it is assumed to mean the number of Romulan (assumed) ships present in this battle (4208) is not higher than the total number of friendly forces present in the battle plus the retreating Fed ships alone, Gorn ships or (or Fed plus Gorn ships). Under Priority 2 this hex is NOT eliminated by the presence of enemy forces.

Priority 3: Supply
3A: No Supply: Are any of the retreat hexes in supply? Yes, from the description provided some of the hexes are in supply for the Feds and some for the Gorn, some are not. As such Priority 3: Supply may NOT be skipped over. Move on to 3B.

3B: OOS: Which hexes would be out of supply? For the Gorn only 4409 seems truly eliminated as leaving the Romulans in the Minor planet hex would block their supply to 4004. (Again the capital path to 4403 must be blocked). For the Fed only 4409 seems truly eliminated as leaving the Romulans in the Minor planet hex would block their supply route through 4308 or 4310. All other hexes are still in supply for both empires.

3C: Partial Grids: Are there any hexes supplied by Partial Supply Grids? There are no partial supply grids indicated (main grid supply only) and as such 3C can be skipped for both empires. Move to 3D.

3D: Shortest Supply Path: Of all the remaining hexes in supply which have the shortest path?
The hexes with the shortest Gorn supply path are 4308 or 4208. (4209, 4310, 4408 are eliminated as too far from 4004.)
The hexes with the shortest Fed supply path are 4208 or 4209. (4308, 4310, 4408 are eliminated as too far from supply). Move to 3E.

3E: No Previous Hex: There are no previous hexes to consider in this situation, move to 3F.

3F: Varied Length of Supply: Are there any of the remaining hexes that would be out of supply for some units but not others in the retreating force? When taken individually the answer would be no the hexes that remained for each empire in priority step 3D would still be in supply for each empire in this step. Move to Priority 4.

Priority 4: Enemy Presence: Are their hexes with enemies present? 4208 is a battle hex with enemies present this hex is eliminated, (except by the possibility of Fighting Retreat if it qualifies). Since John has elected from the start to follow the individual retreat option this leaves only hex 4308 for the Gorn (their only hex remaining) and 4209 as an option for the Fed (their only hex remaining).

FR Option: Did Priority 4 eliminate any hexes? Since Priority 4 DID eliminate hex 4208 John could choose to conduct a fighting retreat with either the Fed or the Gorn or both. Despite the last line of the first paragraph in (302.761) referencing normal retreat, John is not forced to do a fighting retreat as fighting retreat is always an option.

Paul and Patrick are correct. Using the "retreat separately" option the choice is C. If not already clear then the language will be evaluated to state that one or more allied empire in a separate retreat may retreat normally while one (or more of the allies may choose a fighting retreat). This would not be an option if they follow the "retreat together" path.

Retreating together the force would have to follow the rule on who provided the last battle's flagship (or the withdraw hex already established at the beginning of combat). In this situation, 4308 if it were the Gorn Flag or 4209 if it were the Fed Flag. Priority 4 would still have eliminated 4208 allowing John to skip priority 4 in favor of FR taking both forces into 4208 for an FR battle and subsequent retreat.

By John M. Williams (Jay) on Friday, May 01, 2026 - 10:40 am: Edit

Thank you for the detailed analysis. That is very helpful!!


Add a Message


This is a private posting area. A valid username and password combination is required to post messages to this discussion.
Username:  
Password:

Administrator's Control Panel -- Board Moderators Only
Administer Page | Delete Conversation | Close Conversation | Move Conversation