Predictive Victory Dynamics Emblem Planner

How to use the Predictive Victory Dynamics Emblem Planner

1. Enter your available Emblems. Use the balance shown in your event interface. This is the budget for the scenario you are comparing.
2. Choose one side for Match 1. Enter the whole number of Emblems you want to assign, your win estimate as a percentage, and that side's winning multiplier.
3. Add a second match if needed. Match 2 represents a separate battle. To omit it, leave all three of its fields blank.
4. Select Calculate my plan. Review the allocation summary and each match's modeled points per Emblem.
5. Compare another scenario. Change an allocation, probability, or multiplier, then calculate again. Editing an input hides the previous result until you recalculate.
6. Confirm your final choice in-game. Check the active round, current multiplier, available balance, and prediction deadline before submitting.

Use Load hypothetical example to fill a sample scenario, then select Calculate my plan. The sample is an arithmetic demonstration, not a current matchup recommendation. Clear resets the form and hides the result.

Choose the right inputs

Total available Emblems is your planning budget. Enter a nonnegative whole number. The planner does not retrieve your balance or add future Emblem income.

Emblems assigned is the amount allocated to your selected side. Enter whole numbers and keep the combined allocation within the budget. You can leave some Emblems unassigned in a scenario; the tool does not establish whether they can carry into another round.

Your win estimate (%) is your assessment of that side's chance of winning, from 0 to 100. Enter 60 for 60%, rather than 0.60. Base your estimate on the available matchup evidence and acknowledge uncertainty.

Winning multiplier shown in-game is the numerical factor applicable to the selected side. Check its meaning in the event interface. Support Rate and a winning multiplier are different inputs; do not substitute a percentage of player support for a scoring factor.

For a used match, complete all three fields. To omit a match, leave all three blank. Entering an allocation alone is insufficient because the calculation also needs a probability and multiplier.

Understand the allocation summary

The result contains three figures:

Expected score is an average implied by the model. A single round can finish above or below it. The all-win figure is a conditional scenario, not a predicted result or a reward guarantee.

The summary also shows modeled points per Emblem for each entered match. When two picks have different values, it identifies the higher one under your inputs. It compares the scenario you entered; it does not automatically create an optimal allocation.

The expected-score formula

Expected score for one pick = assigned Emblems × win estimate ÷ 100 × winning multiplier

Add the expected scores of the entered picks to obtain the total. Unassigned Emblems equal the budget minus assigned Emblems. The all-win score adds each allocation multiplied by its winning multiplier.

The model assumes losing picks score zero, multipliers stay as entered, and there are no extra bonuses, refunds, caps, or game-specific rounding adjustments. Confirm whether those assumptions fit the current event rules before relying on the estimate.

Adding expected values does not require independent match outcomes. However, the planner does not calculate correlations, a probability that all picks win, or the full distribution of possible scores. Those require additional assumptions beyond this calculator.

Worked example: a 100-Emblem budget

These are the values loaded by the hypothetical-example button:

Match 1 contributes 60 × 0.60 × 25 = 900. Match 2 contributes 40 × 0.30 × 60 = 720. The combined modeled expected score is 1,620, with 0 Emblems unassigned.

If both picks win, the score is 60 × 25 + 40 × 60 = 3,900 under the model. Match 2 has higher modeled points per Emblem despite its lower win estimate. That comparison depends on the probability and multiplier you entered; it does not establish which team will win.

Compare allocations without confusing confidence and payoff

Keep your assumptions fixed when testing an allocation change. In the example, reducing Match 2 from 40 to 20 Emblems leaves 20 unassigned. The expected score becomes 900 + 360 = 1,260, and the all-win score becomes 1,500 + 1,200 = 2,700.

Then test uncertainty separately. Keeping the original allocations, changing Match 2's win estimate from 20% to 40% changes the combined expected score from 1,380 to 1,860. These are alternate inputs, not a statistically established confidence interval.

At a 25% estimate, Match 2's multiplier of 60 produces 15 modeled points per Emblem, matching Match 1's value. Below that estimate it contributes less per Emblem; above it, more. This makes the assumption driving your comparison visible.

Splitting Emblems across matches does not guarantee a minimum score or always reduce risk. Read the prediction strategy guide for a method of separating lineup evidence, probability estimates, and score potential.

Fix an incomplete or invalid plan

If a calculation fails, check the budget first, then every used match. Emblem amounts must be whole numbers, probabilities must be between 0 and 100, and multipliers must be nonnegative. Invalid numbers or allocations above the budget prevent a result from being displayed.

A zero allocation contributes zero score. A zero win estimate also produces zero expected score for that pick, while the separate all-win calculation still uses its allocation and multiplier. Read those outputs according to their definitions.

If both match sections are blank and the budget is valid, the summary shows no assigned Emblems. Add a complete pick to model a match. After changing any input, calculate again before copying the summary.

Copying, privacy, and returning later

Select Copy summary after a successful calculation. If browser clipboard access is unavailable, the page provides a text field for manual copying. Keep your team names and input assumptions alongside the summary when recording a plan.

The planner does not save your inputs or results; browser features may restore form values separately. Optional analytics records limited tool actions only after consent. The planner's own analytics events do not include allocations, win estimates, or copied summary text. Read the privacy information for details.

Emblem planner FAQ

Does the planner recommend a winning team?

No. You select the side and supply its probability estimate. The planner compares the arithmetic of those assumptions.

Can I enter two opposing sides from the same battle?

This form is designed for one selected side in each of two different matches. Do not treat its two sections as a supported same-battle allocation model.

Is expected score my Prediction Score?

Expected score is a planning output. Your actual Prediction Score depends on submitted choices, settled outcomes, and the applicable game rules. The results archive separates recorded outcomes from forecasts.

Does a high expected score guarantee Primogems?

No. Check actual reward conditions and your settled score in-game. The rewards guide explains the distinction between participation, score requirements, and claiming.

Do I need JavaScript or a game login?

JavaScript is needed for interactive calculations. The instructions, formula, and worked example remain readable without it. No game login is requested.

Sources and event information

Use the HoYoverse launch announcement and official HoYoLAB notice for event context. Check changing values and submission availability in your own event interface.

The Predictive Victory Dynamics Emblem Planner is an independent planning tool. For the participation process, read how to play the event; final predictions must be submitted in-game.