Daravi Border Weekend
Posted: Tue Oct 20, 2020 9:18 pm
Posted in game, but it was suggested that these rules might be easier to digest here on the forums, so reposting them here.
Event is scheduled for the weekend of November 13th through 15th.
Synopsis:
We are planning to hold a weekend-long border conflict by gathering players
ICly at a command camp in Farin, where they will RP out deciding orders to
give to the assembled troops. These can be either PCs or new NPCs, and we
have come up with rules to decide how to resolve the results of the orders.
The group can decide how many troops to travel, scout, defend, attack,
besiege or blockade and where they should do it. Orders will be submitted
into a google-doc by a few trusted leads, with up to one order per troop per
hour slot, and can be submitted in advance if desired. Each player will also
get their own unit to command by personal board. Then, staff will process
the results after that time slot has occurred and tell the player group what
happened or what they learned, hopefully leading to more roleplay and heated
discussions over what to do next and what those wily Daravi are up to. Based
on the results at the end, we will decide the new situation with the Daravi
Border going forwards.
Detailed Rules:
Two weeks before the event, players can nominate their characters to attend or create new NPC characters with roles that make sense for being present at Farin strategic planning. They can transition them to permanent characters afterwards if they are not guild roles. They can additionally volunteer if they would like to be a lead - regular characters or NPCs, but NPC leads are required to be honest pro-Lithmorrans.
One week before the event, staff will publish the list of proposed leads. If the Seneschal, Earl Marshall, or Justiciar want to be a lead, they will automatically be approved (players can oust them if they disapprove). Staff will hold a private vote with yes/no/abstain for each other potential lead, and at least the top three will be selected. If there are more than three without many nos (by staff judgement compared to overall voting), they can optionally allow more.
Once it's time for the event, staff will transfer all those who self-nominated to the command camp area. All those participating can wander the area and RP amongst one another. The leads will have edit permissions on a spreadsheet to submit moves, and everyone will be able to view it. The spreadsheet is organized by time, and leads can submit moves for any time in the future, and then once the time has happened, staff will action the move and lock the time. Certain times will be blocked out as breaks. Moves can still be submitted for these times, but they won't be processed until after that whole time block, so staff can sleep or attend to other things.
The whole border map is divided into a grid (A-G by 1-10). Armies, scouts, medics, horses, provisions, weapons and armoring will all have locations on the grid. The Daravi will also have these things with positions on the grid, that will be unknown to the players except through their actions.
A move can be:
Travel - move any army, medic or scout to a grid square +/- 1 in either or both directions. So an army in A10 can move to A9, B10 or B9 in one turn. For each unit of horse, one unit of army, medic or scout can double its speed, moving up to +/- 2 in either or both directions. Horses, provisions, weapons and armor can move along with any armor, medic or scout movements. The number of horses, provisions, weapons or armor accompanying those movements can exceed the count of units and move at the same pace, but only provide benefit up to the number of units. If 10 army units have only 5 horse units, only 5 of the army units can move 2 squares. The other 5 can only move the usual 1 square. Or all 10 units can remain together and move only the 1 square.
Scout - scout units can scout in the grid square that they are currently in. First, there is a 1d100 roll for survival. A roll above 90 and the scout perishes in the desert. If there is an enemy army present, a roll above 75 and the scout is caught by the enemy. Second, if the scout has survived, there is a second 1d100 roll for what they find. If the roll is under 10 and no enemy army units are present, the scout is certain there are no armies there and can report the existence of movements through the area in the last round and the direction. If the roll is under 25, any enemy scouts are sighted. If the roll is under the number of enemy army units, the scout finds the full strength of the enemy. If the roll is under double the number of enemy army units, the scout finds some of the enemy units. Roll a third 1d100 for the percent of the troops found.
Defend - army units can move into defensive positions in the grid square that they are currently in. This allows their numbers to count for 1.5x in a battle where they are attacked. This bonus lasts until they make another move - if they travel or move to attack, besiege or blockade, the bonus no longer applies. (ie the last thing in the history for those units must be the defend)
Attack - army units can attack in the grid square that they are currently in. This kicks off a battle if there are any enemy army units present. If there are not any enemy army units present, the armies are informed that there are not.
Besiege - army units can start a siege in the grid square they are currently in. While under siege, non-scout enemy units cannot travel. The siege lasts until the sieging unit takes another action or is attacked. For each turn that the siege is in place that it is not attacked, deduct 1 unit of provisions from the enemy for each unit they have in that grid square of army or medics. Sum all of these units for which there was not a unit of provisions to deduct and divide that number by 2, and roll 1d(that result) and that number of units perishes from starvation in the siege.
Blockade - army units can start a blockade in the grid square they are currently in. While the grid square is blockaded, army units cannot travel anywhere except back to the last square they travelled from. The blockade remains in effect while the blockading army units remain present and does not take another action. Attacking the blockade does not remove it like attacking a siege does, unless the enemy is defeated and flees.
When battle is enacted, count the total power of each side. Power is the number of army units present in that grid square. Each army unit that can be paired with its own armor unit counts for an additional 0.25 units, and the same for an additional 0.25 units for for weapon units, representing better weaponry (all troops are armed with something). Defending units which are defending from attack count for an additional 0.5 each. Add the power of each army to 1d(that power). The army with the greater sum wins. Subtract the loser's sum from the winner's. Roll 1d(that difference), and the loser loses that number of troops, minus any medic units that are present in the same grid square. The winner also takes casualties of 1d(the loser's losses), minus their own medic units. The loser then flees to the last grid square they had been in (or the most opposite square from the one the enemy has previously been in, if the loser has not moved. If the loser has more losses than there are troops without armor, weapons or horses, the overlap will be captured by the winner.
Orders are given by the leads, one order per set of troops, by entering it at a time in the future. For example, if it is before 1:00 PM, and a lead wants to move some troops from the Cort Pass to Istho Village and attack the Daravi there, they might put at 1:00 PM in the D2 Column "10 Troops, 5 armor, 1 medic travel to E2", at 2:00 PM in the E2 Column "10 Troops, 5 armor, 1 medic travel to F1", at 3:00 PM in the F1 Column "10 Troops, 5 armor, 1 medic attack". Staff will reply after each time with any results for all moves.
Players will also each receive 1 unit of a chosen type at the command camp. This should be of the type that makes the most sense for their character. Leads will just add their units to the totals and command them as normal, but non-lead players will have their unit labeled with their name and they can command it by personal board. Staff will copy these orders in for players. Private player units will be visibly tracked on the shared orders, but they will receive private results if they are not part of actions taken by shared units.
FAQ:
What do players do in the command camp?
They can roleplay life in a war camp. Given regular updates of new information, they should play out the discussions of strategy and information sharing, and decide what new orders to give. If players are present in the command camp, they should RP being there, and their unit can be receiving orders. If they are not online, they can either be at the command camp or with their unit, enacting things themselves. We will overlook any weird time warps if players wish to claim personal involvement and travel back to camp to RP again, but they shouldn't just pop back and forth constantly.
What if I want to participate, but it doesn't make sense for my character?
We are giving players the option to create new NPC characters that make more sense to be present and involved. We are also willing to overlook some misfits for players that wish their characters to join as volunteer recruits.
Can my NPC be a noble?
NPCs can be representatives sent by nobles who are not currently played, but we are not adding new noble canon to support this event. Player nobles can of course participate as themselves.
What if an order is not possible as given (e.g. due to a siege or blockade?)
If an order is not possible, the stack of orders will be shifted down one round, and that first order will be tried again in the next round (and the next, until it succeeds, or the orders are changed).
What if I want to support the Daravi?
For simplification, all players will be playing on the Lithmorran side, and staff will not support communication or extra knowledge between the Daravi and players, and there will be no friendly fire. NPC leads are required to be supportive of Lithmorran interests, but any other player, regular character or NPC, can attempt deceit and bad advice, and provide misinformation from their own private unit.
What if no order is given for a unit at any given time?
It will remain in its last state and take no additional actions until such a time as it is given orders again. It's not expected that every unit or every time will necessarily have orders.
What if player orders and Daravi actions both happen at the same time?
Player actions will all be enacted before Daravi actions. So if players attack in a grid square and Daravi are scheduled to travel from that grid square at the same time, the attack will happen before the Daravi movements.
How are Daravi actions decided?
Staff will determine the rough Daravi strategy ahead of time and will maintain that strategy within the bounds of their own scout and battle results. Staff orders will be recorded before evaluating player orders to maintain fairness.
What affect will this have on things going forwards?
This is a somewhat gamey mechanism, but the actions represented are the ones that are actually happening IC, assumed to be happening on a realistic scale. If the Daravi gain a foothold or are repelled, that will be the IC state with which further actions move forwards.
Can my character die?
Players will generally be at a command camp, rather than out on the battlefield, so we are not assuming any risk of death by the event mechanisms, unless a player would requests that their character die. The command camp area will be IC with normal rules and consequences, however.
Event is scheduled for the weekend of November 13th through 15th.
Synopsis:
We are planning to hold a weekend-long border conflict by gathering players
ICly at a command camp in Farin, where they will RP out deciding orders to
give to the assembled troops. These can be either PCs or new NPCs, and we
have come up with rules to decide how to resolve the results of the orders.
The group can decide how many troops to travel, scout, defend, attack,
besiege or blockade and where they should do it. Orders will be submitted
into a google-doc by a few trusted leads, with up to one order per troop per
hour slot, and can be submitted in advance if desired. Each player will also
get their own unit to command by personal board. Then, staff will process
the results after that time slot has occurred and tell the player group what
happened or what they learned, hopefully leading to more roleplay and heated
discussions over what to do next and what those wily Daravi are up to. Based
on the results at the end, we will decide the new situation with the Daravi
Border going forwards.
Detailed Rules:
Two weeks before the event, players can nominate their characters to attend or create new NPC characters with roles that make sense for being present at Farin strategic planning. They can transition them to permanent characters afterwards if they are not guild roles. They can additionally volunteer if they would like to be a lead - regular characters or NPCs, but NPC leads are required to be honest pro-Lithmorrans.
One week before the event, staff will publish the list of proposed leads. If the Seneschal, Earl Marshall, or Justiciar want to be a lead, they will automatically be approved (players can oust them if they disapprove). Staff will hold a private vote with yes/no/abstain for each other potential lead, and at least the top three will be selected. If there are more than three without many nos (by staff judgement compared to overall voting), they can optionally allow more.
Once it's time for the event, staff will transfer all those who self-nominated to the command camp area. All those participating can wander the area and RP amongst one another. The leads will have edit permissions on a spreadsheet to submit moves, and everyone will be able to view it. The spreadsheet is organized by time, and leads can submit moves for any time in the future, and then once the time has happened, staff will action the move and lock the time. Certain times will be blocked out as breaks. Moves can still be submitted for these times, but they won't be processed until after that whole time block, so staff can sleep or attend to other things.
The whole border map is divided into a grid (A-G by 1-10). Armies, scouts, medics, horses, provisions, weapons and armoring will all have locations on the grid. The Daravi will also have these things with positions on the grid, that will be unknown to the players except through their actions.
A move can be:
Travel - move any army, medic or scout to a grid square +/- 1 in either or both directions. So an army in A10 can move to A9, B10 or B9 in one turn. For each unit of horse, one unit of army, medic or scout can double its speed, moving up to +/- 2 in either or both directions. Horses, provisions, weapons and armor can move along with any armor, medic or scout movements. The number of horses, provisions, weapons or armor accompanying those movements can exceed the count of units and move at the same pace, but only provide benefit up to the number of units. If 10 army units have only 5 horse units, only 5 of the army units can move 2 squares. The other 5 can only move the usual 1 square. Or all 10 units can remain together and move only the 1 square.
Scout - scout units can scout in the grid square that they are currently in. First, there is a 1d100 roll for survival. A roll above 90 and the scout perishes in the desert. If there is an enemy army present, a roll above 75 and the scout is caught by the enemy. Second, if the scout has survived, there is a second 1d100 roll for what they find. If the roll is under 10 and no enemy army units are present, the scout is certain there are no armies there and can report the existence of movements through the area in the last round and the direction. If the roll is under 25, any enemy scouts are sighted. If the roll is under the number of enemy army units, the scout finds the full strength of the enemy. If the roll is under double the number of enemy army units, the scout finds some of the enemy units. Roll a third 1d100 for the percent of the troops found.
Defend - army units can move into defensive positions in the grid square that they are currently in. This allows their numbers to count for 1.5x in a battle where they are attacked. This bonus lasts until they make another move - if they travel or move to attack, besiege or blockade, the bonus no longer applies. (ie the last thing in the history for those units must be the defend)
Attack - army units can attack in the grid square that they are currently in. This kicks off a battle if there are any enemy army units present. If there are not any enemy army units present, the armies are informed that there are not.
Besiege - army units can start a siege in the grid square they are currently in. While under siege, non-scout enemy units cannot travel. The siege lasts until the sieging unit takes another action or is attacked. For each turn that the siege is in place that it is not attacked, deduct 1 unit of provisions from the enemy for each unit they have in that grid square of army or medics. Sum all of these units for which there was not a unit of provisions to deduct and divide that number by 2, and roll 1d(that result) and that number of units perishes from starvation in the siege.
Blockade - army units can start a blockade in the grid square they are currently in. While the grid square is blockaded, army units cannot travel anywhere except back to the last square they travelled from. The blockade remains in effect while the blockading army units remain present and does not take another action. Attacking the blockade does not remove it like attacking a siege does, unless the enemy is defeated and flees.
When battle is enacted, count the total power of each side. Power is the number of army units present in that grid square. Each army unit that can be paired with its own armor unit counts for an additional 0.25 units, and the same for an additional 0.25 units for for weapon units, representing better weaponry (all troops are armed with something). Defending units which are defending from attack count for an additional 0.5 each. Add the power of each army to 1d(that power). The army with the greater sum wins. Subtract the loser's sum from the winner's. Roll 1d(that difference), and the loser loses that number of troops, minus any medic units that are present in the same grid square. The winner also takes casualties of 1d(the loser's losses), minus their own medic units. The loser then flees to the last grid square they had been in (or the most opposite square from the one the enemy has previously been in, if the loser has not moved. If the loser has more losses than there are troops without armor, weapons or horses, the overlap will be captured by the winner.
Orders are given by the leads, one order per set of troops, by entering it at a time in the future. For example, if it is before 1:00 PM, and a lead wants to move some troops from the Cort Pass to Istho Village and attack the Daravi there, they might put at 1:00 PM in the D2 Column "10 Troops, 5 armor, 1 medic travel to E2", at 2:00 PM in the E2 Column "10 Troops, 5 armor, 1 medic travel to F1", at 3:00 PM in the F1 Column "10 Troops, 5 armor, 1 medic attack". Staff will reply after each time with any results for all moves.
Players will also each receive 1 unit of a chosen type at the command camp. This should be of the type that makes the most sense for their character. Leads will just add their units to the totals and command them as normal, but non-lead players will have their unit labeled with their name and they can command it by personal board. Staff will copy these orders in for players. Private player units will be visibly tracked on the shared orders, but they will receive private results if they are not part of actions taken by shared units.
FAQ:
What do players do in the command camp?
They can roleplay life in a war camp. Given regular updates of new information, they should play out the discussions of strategy and information sharing, and decide what new orders to give. If players are present in the command camp, they should RP being there, and their unit can be receiving orders. If they are not online, they can either be at the command camp or with their unit, enacting things themselves. We will overlook any weird time warps if players wish to claim personal involvement and travel back to camp to RP again, but they shouldn't just pop back and forth constantly.
What if I want to participate, but it doesn't make sense for my character?
We are giving players the option to create new NPC characters that make more sense to be present and involved. We are also willing to overlook some misfits for players that wish their characters to join as volunteer recruits.
Can my NPC be a noble?
NPCs can be representatives sent by nobles who are not currently played, but we are not adding new noble canon to support this event. Player nobles can of course participate as themselves.
What if an order is not possible as given (e.g. due to a siege or blockade?)
If an order is not possible, the stack of orders will be shifted down one round, and that first order will be tried again in the next round (and the next, until it succeeds, or the orders are changed).
What if I want to support the Daravi?
For simplification, all players will be playing on the Lithmorran side, and staff will not support communication or extra knowledge between the Daravi and players, and there will be no friendly fire. NPC leads are required to be supportive of Lithmorran interests, but any other player, regular character or NPC, can attempt deceit and bad advice, and provide misinformation from their own private unit.
What if no order is given for a unit at any given time?
It will remain in its last state and take no additional actions until such a time as it is given orders again. It's not expected that every unit or every time will necessarily have orders.
What if player orders and Daravi actions both happen at the same time?
Player actions will all be enacted before Daravi actions. So if players attack in a grid square and Daravi are scheduled to travel from that grid square at the same time, the attack will happen before the Daravi movements.
How are Daravi actions decided?
Staff will determine the rough Daravi strategy ahead of time and will maintain that strategy within the bounds of their own scout and battle results. Staff orders will be recorded before evaluating player orders to maintain fairness.
What affect will this have on things going forwards?
This is a somewhat gamey mechanism, but the actions represented are the ones that are actually happening IC, assumed to be happening on a realistic scale. If the Daravi gain a foothold or are repelled, that will be the IC state with which further actions move forwards.
Can my character die?
Players will generally be at a command camp, rather than out on the battlefield, so we are not assuming any risk of death by the event mechanisms, unless a player would requests that their character die. The command camp area will be IC with normal rules and consequences, however.