Reverse: 1999 4.0 Gatekeeper Guide: Box Parade Progression and Pull Planning | GameHub

The Reverse: 1999 character tier list will shift in the new version, but the logic behind resource planning doesn't: fill the missing roles in your team first, then start talking about the power ceiling. This guide is broken into six sections — version overview, what the Tour banner actually means, build priority, pull planning, the returning-player route, and version cadence.

Reverse: 1999 4.0 Patch Window

Version number and update date

The official website lists version 4.0.0, titled "The Gatekeeper", launching with the 2026 Box Parade celebration, updated 2026-09-24. The same page notes that promotional assets are for display only and in-game performance is authoritative.

What a Box Parade patch means

The TapTap version list runs 3.1 "Long Night Whistle", 3.2 Box Parade "The Moving Feast", 3.3 "Expedition Record", 3.4 "Everlasting Spring", 3.5 "Turquoise Snake Club", 3.6 "Where People Go", 3.7 "The Sorrow of Others", 3.8, and now 4.0. Because both 3.2 and 4.0 are Box Parade patches, the parade is a recurring annual-scale window that usually brings a limited character, reruns, and bonus events.

What a parade patch does to your roster

Parade patches historically reshuffle the meta more than a filler patch, because the limited character usually defines a new team shell and the reruns bring back the pieces that shell needs . That is the reason this guide separates "what to build" from "what to pull": build the shell you already own, and only pull for the pieces that shell is missing.

Reverse: 1999 4.0 Parade Rewards

Using selector opportunities

Community-compiled parade coverage shows these patches typically include a selector, check-in bonuses, and reruns. Spend a selector on the role your roster completely lacks first, then on key copies, and only then on collection picks.

Timing the bonus claims

Parade events usually unlock in stages, so finish the check-in bonus in the first half of the patch and hold resources until banner information is public . The reason not to dump everything on day one is that parade patches often run a limited banner and a rerun at the same time, and both need comparing before you commit.

Reverse: 1999 Progression Priorities

Levels and insight before copies

Push character level and insight to the usable threshold first, then resonance and skills, and leave copies for last . Levels and insight decide whether a character can even take the field, while resonance and skills are later steps on the same stat curve.

Psychubes

Pick psychubes by role: damage dealers want bonuses that match their damage type, and supports want team buffs plus rotation value. Psychubes are reusable, which is why they rank below characters and skills: build your main team's characters first.

Why copies come last

Copies raise ceilings, not floors. A character with no levels and no insight cannot carry a stage regardless of copies, while the same character at a usable insight threshold performs fine at zero copies. For a returner account with a thin roster, one extra usable character beats one extra copy every time.

Reverse: 1999 4.0 Pull Planning

Where pull resources come from

Pull resources come from dailies, events, and patch bonuses, and parade patches pack more events into the same window than a normal patch . Count what you hold, add what the patch still pays out, and see whether that reaches a pity.

Limited versus rerun

When a limited banner and a rerun overlap, take the limited first. Reruns return in later patches, while a limited character waits for the next parade window. There is one exception: if the rerun fills the single missing role in your team, complete the team first and treat the limited as optional.

Reverse: 1999 30-Day Returner Route

Week one

Spend week one pushing the main story and unlocking dailies, so every resource stage is open, and finish the parade check-in bonus . Do not spend heavily on banners yet; map out the free resources and your roster first.

Weeks two to four

Weeks two to four are for progression: bring the main team's levels, insight, and skills up, then look at psychubes and copies. If a new event opens during this stretch, take event rewards first because their windows are short and do not return.

Milestones to check at day 30

By day 30 a comfortable returner account should have the main story caught up to the current patch content, dailies unlocked, and one main team at a usable insight level with skills raised . If any of those three is missing, keep spending stamina there instead of farming optional traces.

Reverse: 1999 Patch Cadence

Estimating the next window

The version sequence from 3.1 through 4.0 shows a fairly tight release cadence. With 4.0 landing 2026-09-24, the next patch sits somewhere in the 4.x range, with exact timing pending official announcement.

Reading the patch list as a calendar

Because 3.1 through 4.0 shipped back to back with only small gaps, the version list doubles as a planning calendar: if you can see how many patches sit between parade windows, you can decide how aggressively to spend in between.

How much to hold back

Keep a portion of pull resources for the next patch so a surprise limited banner cannot derail your plan. Holding back matters because parade-scale limited characters rerun on long cycles, while regular patch characters can be collected over time.

Reverse: 1999 FAQ

Q: When did version 4.0 launch?
A: The official website lists version 4.0.0 updated 2026-09-24, titled "The Gatekeeper" and tied to the 2026 Box Parade celebration.

Q: How should I use a parade selector?
A: Take the role your roster completely lacks, then copies, then collection picks.

Q: What should a returner build first?
A: Push the main story to unlock dailies, then follow levels and insight for the main team; leave psychubes and copies for last.

Q: Should I spend all my pulls now?
A: No. Parade patches often run a limited banner and a rerun together, so compare first and keep part of your resources for the next patch .

Q: Is the 4.0 selector worth saving?
A: Use it during the parade window rather than saving it, because selector availability and roster value both track the current banner lineup.

Action Checklist

1. Confirm the client shows version 4.0.0 and check which parade events are live.
2. Finish the check-in bonus before deciding your pull schedule.
3. Progress the main team in the order levels, insight, resonance, skills, then psychubes and copies.
4. Prefer the limited banner over the rerun unless the rerun fills a roster hole.
5. Hold part of your pulls for the next patch.
6. This guide is revised on GameHub after each patch.