CP run calculator
Please read the instructions at the bottom of the page first.
Output
Output will appear here.
Instructions
Health bonus fields refer to the sum of health, health against players, and health in reinforcements (for the tank if applicable) or on group marches (for participants). The maximum participant health bonus should be an overestimation of the highest health bonus found on a participant stack; the minimum tank health bonus should be an underestimation of the lowest health bonus found on a tanking stack.
Participant numbers on stacks where monster boost applies are adjusted automatically for the maximum possible monster boost to avoid these stacks representing health spikes, and this adjustment is relative to the maximum health bonus. This is the only influence the participant bonus has on participant numbers. Since the reduction diminishes with higher bonuses, it is safe not to adjust the participant numbers as participants grow.
The health cap controls how the losses of the tank are spread. A low cap will result in more small stacks being lost, whereas a high cap will see a smaller amount of large stacks being lost. This outcome depends on various factors outside of this calculator, such as the participation level, and can therefore not be predicted.
There is no fixed obvious best outcome in terms of the tank loss spread: a low number of stacks lost allows the tank to optimise bonuses and leverage their already most cost-effective stacks, whereas a high number of stacks lost means rewards can potentially be spread out more equally over participants of various strength levels and lowers the bar for participation. Note that the health cap in general does not significantly affect the damage the group can inflict on the defender, provided the tank brings enough stacks. However, this damage can be affected in a counterintuitive way: a lower cap may mean some players can carry more stacks, which increases the potential damage.
The complexity of selecting correct troops may affect participation. For this reason, monsters are limited to a single number per level (based on the monster with most health within that level), and all participant numbers are rounded down according to the selected number of significant digits.
If the tank bonuses differ significantly between for instance G and S stacks, more efficient numbers can be obtained by running the calculator once for each of these categories with the respective minimum health bonus. This technique can be applied all the way down to individual stacks. Tank numbers are not automatically adjusted for monster boost, so Griffins and Royal Lions in particular are candidates for further optimisation.
As long as the minimum tank bonus is higher than the maximum participant bonus, the tank can safely add additional participant stacks to hit their own CP target. If this is not the case, care must be taken to avoid these additional stacks becoming the (more expensive) tanking stacks. As a general rule, the proportion of the sizes of these additional stacks to the respective participant stack sizes should be significantly lower than the proportion of the tanking stack sizes to their respective participant stacks.
Various controls can be put in place to ensure efficient and well-distributed CP runs: restricting the choice of captains, disallowing artifacts for participants, restricting the number of guardsman/specialist/monster levels each participant can take, etc. These are up to the organisers; this calculator simply provides troop numbers within the given parameters.