Wuthering Waves Convene History: Track Pity By Hand

Wuthering Waves does not put a pity number anywhere on the pull screen. The only record you get is the Convene History log, opened from a button on each individual banner page — not a single combined list for your whole account.

• The character banner, the weapon banner, and the standard banner each open their own separate History log.
• Entries are listed newest-first, showing the item you received and its rarity for every pull on that specific banner.
• The log only holds a recent rolling window of pulls, not your full history since you started playing — so it is not a permanent archive you can rely on months later.

Verdict: because the three banner types never share a log, any pity math you do has to stay within one log at a time — mixing them is the single biggest source of bad counts.

Since there is no running counter, you build your own by counting backward through the log.

1. Open the History log for the exact banner you want to check.
2. Scroll to the newest entries and find your most recent 5★.
3. Count every single pull listed below that 5★ (toward older entries) until you reach either the top of the log or an even older 5★.
4. That count is your current pity — pulls since your last 5★ on that banner.

Cross-check the number against the known math: base rate is a flat 0.8%, soft pity ramps up from around pull 66, and hard pity guarantees a 5★ by pull 80. If your manual count already sits past 66 with no 5★ showing, expect one to land within the next several pulls.

The log will not literally say "guarantee active" — you have to infer it from what your last 5★ actually was.

• If your most recent 5★ on the character banner was the featured Resonator, you won that 50/50 and no guarantee is carried.
• If it was a standard 5★ instead of the featured one, you lost the 50/50 — your guarantee flag is now active, and the very next 5★ you pull on that same banner is locked to the featured unit.
• The weapon banner has no flag to track at all: every 5★ pulled there is already the featured weapon, so this step only matters for the character banner.

Write down which case you are in before you plan any pulls — a lost 50/50 changes your realistic pull budget completely.

Pity is not reset when a banner rotates — it carries over, but only within the same banner type, and the log itself will not show you that continuity directly.

• Before a banner ends, use the counting method above to note your current pity and guarantee status for that banner type.
• When the next banner of the same type (character-to-character, or weapon-to-weapon) opens, your pity should simply continue from that number — it does not reset to zero.
• The standard banner keeps its own independent counter entirely separate from both featured banners, so nothing you do there affects character or weapon pity.

Since the game gives no on-screen confirmation of this, the only reliable check is to jot your pull count down yourself at the moment a banner switches, then verify your next few pulls match up.

Once you have a manual count, plug it straight into the pity calculator on this site instead of guessing at your odds.

• Enter which banner type you are checking — character or weapon, since their math differs (weapon has no 50/50).
• Enter your pulls since last 5★, the number you just counted from the log.
• Flag whether your guarantee is active, based on what your last 5★ actually was.

The tool returns your real probability of hitting the featured unit within a given number of remaining pulls, built from the 0.8% base rate and the 80-pull hard pity — far more useful than eyeballing a scroll of log entries.

Most bad pity estimates come from a handful of repeat mistakes, not bad luck.

• Mixing standard pulls into a featured count. The standard banner runs its own counter — pulls there never add to character or weapon banner pity, and counting them together inflates your real pity number.
• Merging character and weapon banner tallies. Both cost the same 160 Astrite and both live under "Convene," but their pity counters are completely independent; a count from one log tells you nothing about the other.
• Forgetting the guarantee flag when it applies. Skipping the check in the previous section means treating a locked-in featured pull as a coin flip it no longer is.
• Assuming the log covers your whole account history. Since older entries roll off the log over time, a count based on a partial view can undercount real pity — always start from the newest 5★ you can actually see.

Verdict: keep one tally per banner type, recheck it every time a banner rotates, and treat the guarantee flag as a fact you look up, not something you remember from memory.