Thanks for the video. Very helpful in understanding the flow of the solo gameplay better! One question: I'm having trouble understanding the "...until 4 Troops" directive in the DS Move Priorities. For example, in your campaign, around timestamp 20:25, why do you stop with 4 Troops in the Mountain Pass? Shouldn't you add until you have 5 Troops there to have "majority" in the Mountain Pass (i.e., one more cube than the Invaders)? I thought it might have to do with this "until 4 Troops" note, yet later on when adding Troops to Karnataka, many more than 4 Troops are added. I'm a bit confused with this qualifier, I think.
If you look on the DS Move priorities, you are asked to get a Majority/Control in *Delhi and Provinces*. The Mountain Passes (and Punjab) are Mongol Invasion Regions, not Provinces, so that priority is skipped. 'Until 4 troops' is indeed why 4 Troops are moved to the Mountain Passes. Later, in Karnataka (which is a Province), that priority to get Majority/Control is relevant, and leads to the movement of more units. Hope that helps!
@@sespagnolie Ah yes, you’ve found my error. Indeed I was considering the Mountain Pass as a “province” - whoops! Thank you for the fast clarification!
Your example of a campaign has made me check again my understanding of the rules. I already knew that the non-player Delhi Sultanate should treat all spaces as adjacent. But I had assumed that there was a limit to the number of spaces which could be involved in the overall process. The normal rule for a campaign (4.2.2) specifies "a single route" and "from a single origin space to a single destination space up to three spaces away". Units can be picked up and dropped off along this route, but that still limits the unit redistribution to four different (connected) spaces in total. In your example, in addition to the three destination spaces, you took units from at least four different origin spaces, making the convoluted "route" at least seven spaces in length. Should I therefore assume that for the NP Delhi Campaign, not only are all spaces considered adjacent, but the "single route" can be as long as you want it to be, leapfrogging around all over the map? The only limitation to the unit re-distribution seems to be the maximum of three destination spaces (as per the Ibn Battuta card) or one destination space for the Succession cards.
Hi, I can see the potential for confusion with the NP Delhi Sultanate Campaign. The intent is for the NP Campaign to be completely replaced by the one specified in the NP rulebook (6.8.1) which doesn't reference the normal path constraints (or number of selected spaces). So the answer to your question is: yes, for the NP Campaign, the pieces will come from all over, and potentially from many spaces. This was the only Command or Decree in the game that is different from those in the main game - we simply could not find an easy way to 'program' it that would not put a huge burden on the player. The NP March still only uses adjacent spaces, like a human player must. Thanks for the question!
Thanks for the video. Very helpful in understanding the flow of the solo gameplay better! One question: I'm having trouble understanding the "...until 4 Troops" directive in the DS Move Priorities. For example, in your campaign, around timestamp 20:25, why do you stop with 4 Troops in the Mountain Pass? Shouldn't you add until you have 5 Troops there to have "majority" in the Mountain Pass (i.e., one more cube than the Invaders)? I thought it might have to do with this "until 4 Troops" note, yet later on when adding Troops to Karnataka, many more than 4 Troops are added. I'm a bit confused with this qualifier, I think.
If you look on the DS Move priorities, you are asked to get a Majority/Control in *Delhi and Provinces*. The Mountain Passes (and Punjab) are Mongol Invasion Regions, not Provinces, so that priority is skipped.
'Until 4 troops' is indeed why 4 Troops are moved to the Mountain Passes. Later, in Karnataka (which is a Province), that priority to get Majority/Control is relevant, and leads to the movement of more units.
Hope that helps!
@@sespagnolie Ah yes, you’ve found my error. Indeed I was considering the Mountain Pass as a “province” - whoops! Thank you for the fast clarification!
Your example of a campaign has made me check again my understanding of the rules. I already knew that the non-player Delhi Sultanate should treat all spaces as adjacent. But I had assumed that there was a limit to the number of spaces which could be involved in the overall process. The normal rule for a campaign (4.2.2) specifies "a single route" and "from a single origin space to a single destination space up to three spaces away". Units can be picked up and dropped off along this route, but that still limits the unit redistribution to four different (connected) spaces in total.
In your example, in addition to the three destination spaces, you took units from at least four different origin spaces, making the convoluted "route" at least seven spaces in length. Should I therefore assume that for the NP Delhi Campaign, not only are all spaces considered adjacent, but the "single route" can be as long as you want it to be, leapfrogging around all over the map? The only limitation to the unit re-distribution seems to be the maximum of three destination spaces (as per the Ibn Battuta card) or one destination space for the Succession cards.
Hi,
I can see the potential for confusion with the NP Delhi Sultanate Campaign. The intent is for the NP Campaign to be completely replaced by the one specified in the NP rulebook (6.8.1) which doesn't reference the normal path constraints (or number of selected spaces).
So the answer to your question is: yes, for the NP Campaign, the pieces will come from all over, and potentially from many spaces. This was the only Command or Decree in the game that is different from those in the main game - we simply could not find an easy way to 'program' it that would not put a huge burden on the player. The NP March still only uses adjacent spaces, like a human player must.
Thanks for the question!