Genshin Impact 7.1 Leaks: Save for Vesna or Vodyanitsa?
Multiple current leaks place Vesna and Vodyanitsa in Genshin Impact Version 7.1, following the Version 7.0 launch on August 12, 2026. Vesna is repeatedly associated with Anemo and a damage-oriented Stellar Swirl role, while Vodyanitsa is associated with Hydro, support functions, and possible value for Stellar Swirl or Skirk teams. None of these Version 7.1 banner or kit details is official yet. This article helps players reserve Primogems without presenting early leaks as final beta data.
Genshin Impact Version 7.0 has not launched yet, but the Version 7.1 rumor cycle is already focusing on two Snezhnayan names: Vesna and Vodyanitsa. Players planning future Wishes can prepare Genesis Crystals through Topuplist and the dedicated Genshin Impact top-up page only after choosing a confirmed purchase, while current Version 7.1 information should be used to protect Primogems rather than justify immediate spending.
The repeated part of the leak picture is relatively simple. Several independent summaries place Vesna and Vodyanitsa in Version 7.1, with Vesna associated with Anemo and Vodyanitsa with Hydro. The uncertain part includes phase order, weapon types, exact rarities, complete kits, team restrictions, signature weapons, reruns, and whether both characters really release in the same patch.

What Is Actually Repeated Across Current Leaks
Vesna and Vodyanitsa have appeared together in several Version 7.1 roadmap reports. That repetition raises the rumor above a single anonymous claim, but it does not turn the banner into an official HoYoverse announcement.
Vesna is commonly described as an Anemo character connected to the new Stellar Swirl system. Some reports describe her as a damage dealer or central reaction unit. Vodyanitsa is commonly described as a Hydro character with support value, including possible benefits for Stellar Swirl teams and teams centered on Skirk.
Detail | Current Rumor Status | Planning Use |
|---|---|---|
Vesna in Version 7.1 | Repeated by multiple leak summaries | Keep a reserve if the character is a priority |
Vodyanitsa in Version 7.1 | Repeated by multiple leak summaries | Preserve support budget until beta details |
Vesna is Anemo | Frequently repeated | Watch Stellar Swirl and Anemo support needs |
Vodyanitsa is Hydro | Frequently repeated | Compare with existing Hydro support depth |
Both are 5-star characters | Common but not official | Use a two-character worst-case budget only as a ceiling |
Banner phase order | Conflicting or incomplete | Do not schedule pulls around a rumored phase |
Exact kits and numbers | Early and unstable | Do not pre-farm unconfirmed materials |
Rerun lineup | Not established | Do not assume the new characters are the only priorities |
The correct label is “repeated leak,” not “confirmed banner.” Version 7.1 beta data should provide a stronger basis after Version 7.0 approaches release, and the official Special Program will remain the final source for banner identity and timing.
Why Version 7.0 Changes the Decision
Version 7.0 launches on August 12, 2026. It introduces the Snezhnaya era, new characters, new reaction systems, exploration rewards, weapons, artifacts, and a large amount of fresh account spending pressure.
A player who uses the entire launch reserve on Version 7.0 may enter 7.1 with little recovery time. The usual six-week version rhythm provides new Primogems, but the amount available depends on exploration completion, events, Spiral Abyss, Imaginarium Theater, subscriptions, and personal activity.
This makes the 7.1 rumor useful even before its details are stable. It tells players that another potentially important pair may arrive immediately after the nation launch. The safe response is not to skip 7.0 automatically. It is to set a Version 7.0 stopping point before the Wishes begin.
List the Version 7.0 target, maximum constellation, weapon decision, and minimum Primogem balance that must remain untouched. A clear floor prevents a lucky early pull from turning into an unplanned constellation chase.
The Vesna Case
Vesna currently appears in leaks as the more damage-oriented Version 7.1 option. Her Anemo association and reported connection to Stellar Swirl make her relevant to players who want to build around the new reaction system rather than simply add another general Anemo support.
That role is still unstable. “Damage dealer” can mean an on-field carry, a reaction driver, a quick-swap source, or a unit whose personal damage depends heavily on specific teammates. Early summaries do not settle field time, Energy needs, grouping, resistance reduction, reaction ownership, or how much of her output depends on Version 7.0 characters.
Vesna is a stronger saving target when the account wants a new Anemo-centered team, intends to invest in Stellar Swirl, and can preserve compatible supports. She is less urgent when the account already has several unfinished carries or when the player does not enjoy reaction teams that require fixed elements.
Do not pre-farm normal boss materials, local specialties, talent books, or weekly boss drops. Version 7.1 materials may come from areas or enemies not available before the patch. Generic Mora, Hero's Wit, Mystic Enhancement Ore, Artifact EXP, and Fragile Resin are safer reserves.
The Vodyanitsa Case
Vodyanitsa is repeatedly associated with Hydro and a support-oriented role. Early discussion connects her to Stellar Swirl while also suggesting value for Skirk teams or other Cryo-Hydro structures.
Hydro support is one of the most competitive roles in Genshin Impact. An account may already own Furina, Yelan, Xingqiu, Kokomi, Mona, or other Hydro options. Vodyanitsa therefore needs to be judged by the exact problem she solves rather than by element alone.
If her final kit gives a unique Stellar Swirl multiplier, reaction condition, Max HP effect, resistance interaction, or teamwide buff, she may become difficult to replace in a specific archetype. If her value is mainly broad Hydro application or generic damage support, existing characters may reduce the need to pull.
Players with Skirk should wait for direct team testing. A statement that Vodyanitsa “supports Skirk” does not reveal whether she improves the best current team, replaces a premium support, fixes rotation comfort, or only offers an alternative.
Vodyanitsa is a stronger reserve target for accounts that value flexible supports, lack high-end Hydro options, or plan to build the Version 7.1 Stellar Swirl core. She is less urgent when Hydro support is already deep and Vesna's team would not be used.
Save for a Pair, Pull for an Account
The leaks often discuss Vesna and Vodyanitsa together, which creates an assumption that the complete team requires both. That is possible, but not proven.
Do not commit to a two-character package until beta kits show whether one is functional without the other. A carry-support pair can be powerful while still allowing alternatives. It can also become expensive if both signature weapons or constellations are marketed as major improvements.
Build three budgets. The first is a one-character reserve for the preferred target. The second is a two-character ceiling used only if the pair proves necessary and affordable. The third is a protected balance for later Snezhnaya characters.
The protected balance matters because roadmap leaks extend beyond Version 7.1. Reports place other characters in Versions 7.2 and 7.3, including names connected to major Snezhnaya story roles. Spending every Primogem on an early pair can remove flexibility for the Archon or another favorite.
Primogem Planning After August 12
Record the Primogem, Intertwined Fate, pity, and guarantee state immediately before Version 7.0. That snapshot is the opening balance for the Snezhnaya cycle.
During Version 7.0, count only confirmed income already claimed or realistically reachable. Do not add every exploration chest, achievement, event, and endgame reward if the account will not complete them before Version 7.1.
Separate permanent exploration income from time-limited event income. Permanent Snezhnaya content can be completed later, while limited events and maintenance compensation have deadlines.
Stop Version 7.0 pulls when the predetermined floor is reached. If the chosen character arrives early, reassess instead of immediately chasing a signature weapon. A weapon banner can consume the reserve intended for Vesna or Vodyanitsa.
When Version 7.1 beta information becomes available, update the plan with actual roles, material sources, team requirements, and banner order. Do not keep following an older rumor after stronger data contradicts it.
Who Should Prioritize Vesna
Players who prefer on-field or reaction-centered damage should watch Vesna first. An account that already owns strong Hydro support but lacks a new Anemo team direction may obtain more value from her.
Vesna also becomes more attractive if Version 7.0 establishes Stellar Swirl as a powerful reaction and her beta kit controls its damage, frequency, or field time.
Skip or delay when the account has too many unbuilt carries, lacks the reported reaction partners, or prefers characters with broad off-field value.
A favorite-character decision can override meta concerns, but the player should still reserve enough to reach the personal stopping point without relying on an early win.
Who Should Prioritize Vodyanitsa
Players with Skirk, limited Hydro support depth, or interest in a flexible Version 7.1 enabler should watch Vodyanitsa first.
She may also offer stronger account longevity if her final kit supports more than one reaction archetype. Support characters often retain value when new damage dealers arrive, but only a complete kit can establish that flexibility.
Skip or delay when the account already has every relevant Hydro support, does not use the teams she enhances, or would need to pull Vesna solely to create a purpose for her.
Do not assume a support automatically requires less investment. Talent levels, Energy Recharge, weapon choice, artifact requirements, and constellation pressure can make a support expensive.
What to Watch During the 7.1 Beta
First, confirm element, rarity, weapon type, and field role. These are basic facts that should replace early descriptions.
Second, identify Stellar Swirl activation conditions. Check required elements, reaction ownership, cooldowns, and whether the effect works from off-field.
Third, compare Vodyanitsa's support with existing alternatives. Look at buff duration, team restrictions, Hydro application, Energy, healing or survival, and opportunity cost.
Fourth, evaluate Vesna without a signature weapon or constellation. A character's baseline should solve the advertised role before premium upgrades are considered.
Fifth, inspect team cost. A team requiring two new five-stars plus several contested supports can be powerful but difficult for a normal account to assemble.
Sixth, wait for late beta changes. Multipliers, Energy costs, cooldowns, and constellations can change between early testing and release.
Avoid Leak-Season Mistakes
Do not publish the rumored Version 7.1 lineup as official. Use “leaked,” “reported,” and “subject to change.”
Do not state an exact release date until the version schedule is officially established. Version rhythm can support an estimate, but maintenance changes remain possible.
Do not recommend a fixed team before complete kits exist. A reported synergy is a watch point, not a final rotation.
Do not pre-farm regional materials based on placeholder data. Preserve universal resources.
Do not skip a favorite Version 7.0 character solely because an anonymous account says a Version 7.1 unit is stronger. Compare confidence levels and personal priorities.
Do not buy Genesis Crystals for a character that has not been announced. Recharging should follow a final purchase decision, not a leak.
A Practical Saving Decision
Choose one statement that best describes the account.
If the account wants Version 7.0 most, secure that target and stop at the planned balance floor. Keep the remainder for 7.1 testing.
If Vesna is the clear favorite, skip optional Version 7.0 weapons and constellations, preserve a one-character guarantee, and watch whether Vodyanitsa becomes necessary.
If Vodyanitsa is the clear favorite, protect a support reserve and test whether existing carries benefit from her final kit. Do not assume Vesna must also be obtained.
If both are equally important, budget for two characters but wait for banner order and final beta. A two-character plan should not include both signature weapons by default.
If neither is compelling, save through 7.1. The Snezhnaya roadmap contains later characters, and unused Primogems preserve choice.
FAQ
Are Vesna and Vodyanitsa officially confirmed for Version 7.1?
No. Multiple leaks place them in Version 7.1, but HoYoverse has not officially confirmed the banner lineup as of August 6, 2026.
What elements are they rumored to use?
Vesna is repeatedly associated with Anemo, while Vodyanitsa is associated with Hydro. Both details remain subject to beta and official confirmation.
What are their rumored roles?
Vesna is commonly described as a Stellar Swirl damage unit. Vodyanitsa is described as a support for Stellar Swirl and possibly Skirk-related teams, but exact kits are not final.
Should I skip Version 7.0 for them?
Only if the Version 7.1 characters are personally more important. A safer plan is to set a Version 7.0 stopping point and preserve a defined reserve.
Should I pre-farm materials?
Preserve universal Mora, EXP, weapon ore, and Artifact EXP. Do not farm unconfirmed regional specialties, boss drops, or talent books.
Do I need both characters?
That is not established. Wait for beta team testing to determine whether the rumored carry and support can use existing alternatives.
When should I top up?
Wait until the desired character and banner are officially announced and the account's exact currency gap is known. At that point, players can use Topuplist and the Genshin Impact top-up page; a recharge does not confirm a leak or guarantee a Wish result.
What is the safest plan today?
Protect a one-character reserve, avoid optional Version 7.0 overspending, and update the decision when Version 7.1 beta data becomes available.

