The two featured character wishes in Version 7.1 have separate panels, but their Character Event Wish and Character Event Wish-2 guarantee counts are shared. HoYoverse’s Phase I notice also says this count is independent from other wish types. For planning, that means a pull on one of the two compatible character wishes affects the shared character-wish counter you bring to the other. Switching the panel does not create a fresh counter or duplicate your existing pity.
This detail can make banner switching a useful strategy, but only when you understand what it does. If you prefer Vesna and begin pulling on her wish, then decide to switch to Vodyanitsa, the character-wish count does not reset merely because the banner artwork changed. Your past compatible character-wish pulls still matter. The wishes themselves are still spent, however; shared pity is not an extra pool of currency.
Record your current counter accurately
Before making a decision, check your wish history and write down your current Character Event Wish pity. If you have pulled on earlier character banners, include those wishes according to the game’s current banner rules. Do not estimate from memory if the history is available. A few forgotten pulls can change how close you believe you are to a 5-star.
Also write whether your next 5-star has a featured guarantee under the current rules. The pity count and guarantee status are separate pieces of information: one is a counter, and the other describes the state of your next 5-star result. Keep both beside your wish balance. Never add pity to your number of Intertwined Fates as if it were currency.
Avoid the two-calculator mistake
A common spreadsheet error is to treat Vesna’s panel as one pity pool and Vodyanitsa’s as another. The player enters the same current pity into both calculators and concludes that they have two separate head starts. The official shared-count rule means this double-counts the advantage. There is one compatible character-wish state, even though there are two featured characters to choose from.
For example, imagine you have a recorded 55 character-wish pity and make 20 more pulls on Vesna’s wish without receiving a 5-star. If you then switch to Vodyanitsa, your character-wish counter reflects the additional pulls; it has not returned to 55 or zero. If a 5-star appears during those attempts, update the counter and guarantee state according to the outcome before making another decision.
The example is about accounting, not a prediction of when a 5-star will arrive. Banner probability can make the result uncertain, so do not turn an illustration into a promise that a fixed number of pulls will produce a particular character.
Keep other wish types separate
The shared character-wish rule does not mean every wish type shares the same pity. Weapon wishes and the Standard Wish have their own systems and should be kept outside the character-banner calculation. Do not use a character guarantee to estimate a weapon target, and do not count Acquaint Fates as attempts on Vesna or Vodyanitsa.
If you use a third-party calculator or community guide, check that it reflects the currently displayed rules. The in-game notice is the final reference for the banner you are using. This habit is especially important when a game changes systems or when a guide was written for an older version.
Plan your switch before you pull
If you may switch between the two characters, decide why and under what condition. For instance, you might first try your primary target and switch only if an early result leaves enough wishes for the second. You might instead commit to one character and avoid banner hopping altogether. Either way, write the current pity once in a shared ledger and subtract wishes from one common balance.
A purchase does not alter the shared-pity rule. If you review a genshin top up cheap offer, calculate how many wishes it adds to your single shared plan, then check the final local cost and terms. Do not add the same purchased wishes separately to each character’s budget.
Understanding shared pity makes switching between compatible character banners easier to model. It does not make two targets independent or remove uncertainty. One balance, one character-wish counter, and one updated ledger are the simplest way to keep the plan honest.
A sample calendar from the player’s point of view
Suppose a player checks their account on October 2 and sees that the Phase I wishes are listed through October 13. They should not immediately add eleven days of every possible reward to the current total. Instead, they make a row for each day they expect to log in, then add only confirmed activities whose claim windows fit before the banner ends. If a multi-stage event has a final reward that becomes available on October 12, the player can count it only if they expect to finish the required stages in time. If a reward arrives after October 13, it belongs to a later saving plan, not this deadline’s budget.
This calendar can also show when the decision must be made. The player may want to pull before the final hours, rather than waiting until the last moment when there is no room to check account state or payment details. A sensible decision date can be earlier than the official banner end. Mark that personal cutoff, too. It creates breathing room for verifying wish history and updating the ledger after rewards arrive.
Keep a record of what was planned and what actually happened. When a daily reward is claimed, change its status from expected to received. When an event task is missed, remove the reward from the conservative total. This turns the calendar into an up-to-date budget instead of a screenshot of an optimistic forecast.
Finally, compare your conservative and optimistic totals. If both support the same pull limit, your plan is robust. If the optimistic version adds only a small number of wishes, do not let that amount determine a costly decision. It may be enough for an additional attempt, but it is not automatically enough to justify raising a spending cap. Timing and confidence matter just as much as the headline reward amount.
A final check is to compare your own notes with the Wish History after a session rather than relying on a remembered number. Record the date, panel, number of pulls, and whether a 5-star appeared. If your history shows a result that your spreadsheet missed, correct the spreadsheet before you calculate another target. This is especially important if you switch between Vesna and Vodyanitsa or if you have not pulled for several weeks. A one-line correction now can prevent a much larger error later. Keep the official notice available when reviewing the rules, but use the account’s actual history to determine what happened. Shared pity is a tracking rule, not a reason to assume that a result is due on the next panel.
Leave a comment