Gacha Pity Carry-Over Guide

Short answer: do not treat Monster Hunter Outlanders pity as one universal number. In the third closed beta, the Featured Recruitment counter for an SSR within 90 recruits and the guarantee created after losing the featured 50/50 were reported to carry into a later Featured Recruitment. A separate guarantee for the featured SSR within 120 recruits was tied to one Featured Recruitment period and reportedly reset when that period changed. Standard Recruitment kept its own independent count, while Beginner Recruitment had its own limited guarantee.

Those were CBT3 rules, not confirmed global-launch rules. As of October 28, 2026, the international launch is scheduled for October 29, so the final live wording has not yet been verified. The useful decision is therefore simple: track every guarantee separately, and do not spend on the assumption that a beta carry-over rule survived launch until the current Recruitment details say so.

The CBT3 carry-over answer at a glance

The table below separates the counters that are often compressed into the single word “pity.” Its carry-over column describes the CBT3 report only.

The key distinction is between a counter that follows the Featured Recruitment category and a guarantee limited to one Featured Recruitment period. Both can advance while you recruit on the same banner, yet they can have different reset rules. Seeing “90” and “120” in the same beta rules did not make them parts of one combined meter.

CBT3 Featured Recruitment example with its banner identity and guarantee counter.

Why pity cannot be tracked as one number

A reliable pull plan needs three pieces of information: the Recruitment type, the exact guarantee, and the time scope attached to that guarantee. If any one of those is missing, a total such as “I am at 70 pity” is ambiguous.

The SSR counter and the featured-period guarantee were different

The reported 90-recruit rule answered one question: how long could Featured Recruitment go without awarding an SSR Adventurer? The reported 120-recruit rule answered a narrower question: how many recruits within that Featured Recruitment period could pass before the featured SSR Adventurer was guaranteed.

Those questions are not interchangeable. An off-feature SSR could interact with the 90 counter and the 50/50 state, while the 120 rule existed to cap the wait for the period’s featured Adventurer. Those separate triggers do not form one combined arithmetic formula. Track their displayed progress or written conditions separately.

This distinction changes the decision at a banner transition. Under the CBT3 report, progress toward the 90-recruit Featured SSR guarantee could remain useful after the target changed, but progress toward the 120-recruit period guarantee could not. A player who remembered only the larger number could incorrectly assume every recruit remained credited toward the next featured target.

The 50/50 result was a state, not just a pull count

The reported Featured rules also included a 50% chance that an SSR would be the featured Adventurer. If that check produced a different SSR, the next SSR was reported to be the featured one. CBT3 coverage said this post-loss guarantee moved to another Featured Recruitment.

That state should be recorded as “featured guarantee active,” not buried inside a generic pity total. Two accounts with the same number of recruits since their last SSR could be in different positions if one had previously lost the featured check. Conversely, knowing that you lost a 50/50 does not tell you how close you are to the separate period-specific 120 guarantee.

For launch, look for explicit wording that connects a failed featured result to the next SSR and defines whether the promise applies across later Featured Recruitments. Similar-looking banner art or the reuse of the word “Featured” is not enough to establish that scope.

Standard, Featured, and Beginner were separate tracks

CBT3 material described Standard, Featured, and Beginner Recruitment as distinct banner types. Standard used its own SSR guarantee and one-time selection milestone. Featured used its own SSR counter, featured-result state, and period guarantee. Beginner offered a shorter path to an SSR and then ended.

A recruit made on one type should not be added to another type’s total unless the current rules explicitly say the two share progress. In the beta description, Standard did not share pity with Featured, and no Beginner transfer was established. The safe ledger therefore has separate rows even when several banners are visible in the same menu.

Standard Recruitment is shown as a separate recruitment track.

How to verify carry-over in the launch client

After the international servers open, verify the rules without spending recruits merely as a test. The goal is to read the contract attached to the banner and preserve enough information to compare it later.

1. Identify the exact service and Recruitment

Start with the publisher or regional service, your server, the Recruitment type, the featured target, and the displayed period. Level Infinite or Proxima Beta listings and Garena listings are distinct; that fact alone does not prove their banner rules differ, but it prevents one service’s screen from being silently applied to another.

Write the exact Recruitment name. “The limited banner” is not specific enough for later comparison. If more than one Recruitment is available, create a separate record for each one rather than assuming shared progress.

2. Read every guarantee as a separate sentence

Open the available Details, Rules, Probability, or equivalent information panel. Search for language covering:

• the maximum recruits before any SSR Adventurer;
• the result after an SSR is not the featured Adventurer;
• any maximum recruits for the featured Adventurer;
• the phrase “Recruitment period” or equivalent reset scope;
• whether progress transfers to a later Featured Recruitment;
• what happens when Beginner Recruitment ends;
• whether Standard milestones are one-time or repeatable.

Do not infer missing text from the beta. If the live panel confirms only the SSR counter but says nothing about the post-loss state, mark the second item “unclear” rather than copying the old rule into the gap.

3. Capture the visible account state

If the client shows remaining recruits, progress, history, or a guarantee marker, capture the entire relevant panel. Include the Recruitment name and period in the same record when possible. A cropped number without its banner identity cannot prove which counter it belongs to.

Record the calendar date, service, server, Recruitment name, and whether an SSR or featured loss has occurred. Do not rely on memory after several ten-recruit actions, especially when the same action may advance more than one guarantee.

4. Compare only like with like after a rotation

When a Featured period changes naturally, compare the old record with the new Featured Recruitment before making the next recruit. Check the 90-style SSR progress, the post-loss state, and the period-specific featured guarantee independently. One surviving counter does not prove that every other counter survived.

A reset in the displayed period guarantee also does not prove that the general Featured SSR counter reset. The entire purpose of the comparison is to avoid collapsing multiple records into one verdict.

5. Stop if the wording and display disagree

If the rule text says progress carries but the displayed state appears reset, do not spend to investigate. Preserve both screens and use the game’s support route. The text may have a scope condition, the display may use “remaining” rather than “completed,” or the account may be on a different Recruitment than expected. More pulls make the original state harder to reconstruct.

Decisions for common account states

You have Featured recruits but no SSR yet

CBT3 reporting suggests that the 90-recruit Featured SSR count could carry to another Featured Recruitment. It does not establish that the launch client will preserve it. If you prefer a later target, the low-risk action is to pause and confirm the live transfer language rather than finish the current banner solely to protect a beta counter.

Also check whether your progress is being described as completed recruits or remaining recruits. Record the label with the number. Reversing those meanings can make an unchanged counter look reset.

You lost the featured 50/50

Record two things: the post-loss guarantee state and the general SSR count after that SSR appeared. The beta report said the next featured guarantee carried, but the SSR result and its counter reset are separate events. Do not write only “guaranteed” and assume that note also captures how many recruits remain.

Before switching to a later target, confirm that the live rule extends the guarantee beyond the current Featured Recruitment period. If that sentence is absent, the state remains unverified even if CBT3 used that behavior.

You are close to the reported 120-period guarantee

This is the highest-risk place to rely on carry-over. CBT3 described that guarantee as once per Featured Recruitment period and said it did not transfer. If the current target is not one you want, do not assume those recruits will become progress toward the next target.

If the current target is one you do want, make the decision from the live rule, your available resources, and the exact remaining progress. The beta threshold can tell you what to look for, not what the launch client owes the account.

You have only recruited on Standard

Keep that progress on the Standard row. CBT3 described its SSR counter and one-time selection reward as independent. Neither was evidence of progress on Featured or Beginner Recruitment.

Standard progress may still be valuable on its own, but evaluating Standard versus Featured value is a different decision. For carry-over purposes, the important point is that the tracks were not shared in the beta description.

You are using Beginner Recruitment

Treat Beginner as its own temporary track. CBT3 described an SSR within 50 recruits and said the banner ended after that result. No transfer of unfinished Beginner progress to Standard or Featured is confirmed for the global launch.

Before recruiting, read what the launch panel says about the banner’s end condition, discount, and unused progress. Do not assume that using Standard Contracts, if the live version does so, would make the pity itself part of Standard Recruitment. A shared resource does not automatically create a shared counter.

Beginner Recruitment is presented as its own temporary track.