Resident Evil ZombieBuster (2011)

Spoiler-free maximum verifiable completion of the 2011 Japanese mobile remake route · 8 areas · 49 tracked items

This page shows everything, including exact locations. It exists so you can search for one specific collectible and find it. If you are playing blind, use the interactive spoiler-free version instead — it hides locations until you ask for them, one item at a time.

Open the spoiler-free interactive guide

Archival Remake Route

You are here when: The preserved Japanese feature phone, carrier package, runtime metadata, and remake title screen.

The chosen route is the 2011 remake; the earlier mobile version is not substituted for missing remake evidence.

2011 Japanese Remake Route (missable)

Route

HintThe selected catalog route is a discontinued feature-phone remake.

WhereUse a lawfully preserved copy of the 2011 Japanese mobile release.

Full detailVerify the Japanese title screen, 2011 build context, handset model, application files, and carrier metadata before play. A modern imitation or footage-only reconstruction cannot establish completion of this route.

Carrier Variant Record

Route

HintSeveral Japanese networks distributed the remake.

WhereIdentify whether the surviving package belongs to docomo, au, or SoftBank.

Full detailPhotograph the handset and record the network branding, application identifier, file metadata, and launch path. Preserve each distinct carrier package separately rather than assuming their files are interchangeable.

Flash Runtime Record

Archive Safety

HintThe required Flash generation depends on the carrier build.

WhereRecord Flash Lite 3.0 for docomo or Flash Lite 2.0 for au and SoftBank.

Full detailConfirm the runtime reported by the handset or preserved technical metadata before launching. Keep the phone firmware and browser version with the archive because timing and compatibility may change across implementations.

Original Subscription Context

Archive Fact

HintThe remake came through a monthly mobile service.

WhereRecord the historical access price as 315 yen per month.

Full detailStore any surviving subscription or carrier page beside the build. Treat 315 yen as historical context only; it does not identify a current lawful storefront or a working modern service.

Earlier Version Exclusion

Route

HintAn older release exists outside the chosen route.

WhereKeep the 2001 version only as a historical comparison.

Full detailComplete the 2011 remake for this pack. Do not merge screenshots, timing values, graphics, controls, or balance observations from the earlier mobile version into the remake checklist unless direct comparison proves they match.

Complete Session Capture (missable)

Archive Safety

HintA working launch may be difficult to repeat.

WhereRecord from application boot through menus, play, score result, and exit.

Full detailBegin native-resolution capture before launch, include every input and result screen without cuts, and save the raw recording with the handset metadata. Duplicate both application data and footage to two checked storage locations.

Operator Routes

You are here when: The character-selection screen and the opening enemy formation.

Player-facing text distinguishes the selections by mechanics and does not expose character identities.

Power-Focused Operator

Character Style

HintOne selection favors stronger individual shots.

WhereChoose the menu portrait whose weapon pushes targets back farther.

Full detailStart a fresh run with the power-focused selection. Record the selection screen, then measure target displacement and time between shots against the same early formation used for the other operator; avoid assigning numerical stats without frame-tested evidence.

Rapid-Fire Operator

Character Style

HintThe other selection trades impact for firing speed.

WhereChoose the menu portrait that can shoot more rapidly.

Full detailStart a separate run with the rapid-fire selection. Capture identical early targets and compare shot spacing, knockback, reload timing, and survival margin with the power-focused run while keeping all unverified numerical values out of the guide.

Operator Comparison

Character Audit

HintBoth control styles need evidence from equivalent conditions.

WhereRecord one comparable opening sequence with each operator style.

Full detailUse the same handset, formation, capture rate, and input method for both runs. Compare only directly visible differences in impact and firing cadence, then retain the two recordings together so later hardware latency is not mistaken for character balance.

Verified Defense Loop

You are here when: The single-screen playfield, horizontal firing lane, approaching targets, and lower defense boundary.

Only directly supported controls, reload behavior, and failure mechanics are stated as established facts.

Horizontal Positioning

Core Control

HintThe defense line is protected by lateral movement.

WhereMove sideways until the weapon is aligned with the approaching target.

Full detailTrack the target's lane, shift horizontally into alignment, and leave enough distance to recover from the next forced reload. Record the actual handset inputs because the surviving sources do not establish a universal key layout.

Fire

Core Control

HintAligned shots are the only verified attack.

WhereShoot the nearest target before it reaches the lower boundary.

Full detailFire while aligned, watch for visible recoil or backward movement, and prioritize the threat closest to the defense line. Keep shooting only as fast as the chosen operator and reload cycle allow.

Target Knockback

Combat Mechanic

HintA hit creates space before it finishes a target.

WhereUse repeated shots to drive an approaching target away from the boundary.

Full detailConfirm a hit by visible rearward movement, then use that space to address another lane or prepare for reload. The power-focused operator creates the larger displacement, but the exact distance remains unverified.

Target Defeat

Combat Mechanic

HintKnockback alone does not clear the formation.

WhereContinue landing hits until the aligned target disappears or enters its defeat state.

Full detailMaintain lane alignment through the target's full damage sequence and confirm the defeat animation before changing lanes. Do not infer a fixed hit count because durability can change later in the run.

Six-Shot Reload

Weapon Cycle

HintThe weapon pauses after a short fixed firing cycle.

WhereExpect a reload immediately after every sixth shot.

Full detailCount fired rounds from the last completed reload and create distance before round six. The reload begins automatically, so plan the final shot for the most urgent lane instead of spending it on a distant target.

Reload Exposure

Weapon Cycle

HintNo shot can be fired during the reload pause.

WhereUse knockback and lateral spacing before the weapon becomes unavailable.

Full detailPush the nearest threat back before the sixth round, begin the reload with no target touching the lower boundary, and reposition while firing is locked. Resume shooting only when the game visibly returns control.

Defense-Line Breach (missable)

Failure Rule

HintThe run ends when an approaching threat crosses the protected boundary.

WhereKeep every target above the defense line at the bottom of the playfield.

Full detailWatch the lowest target rather than the largest group. If a controlled archival attempt is available, capture one natural breach, the full result screen, and every retry or exit option without risking the only preserved session.

Formation Clear

Progression

HintRemoving an ordinary formation advances the run.

WhereDefeat every standard target currently present on the playfield.

Full detailSweep lanes until no ordinary target remains, preserve the transition that follows, and continue recording into the next distinct encounter. Do not use a presumed stage number or order in the player-facing guide.

Documented Special Encounters

You are here when: The same defense playfield after an ordinary formation has been cleared.

Physical descriptions replace identity names, and no encounter order is exposed.

Large Humanoid Encounter

Special Encounter

HintA tall single target replaces the ordinary formation.

WhereContinue clearing formations until the large upright target appears.

Full detailStay aligned with its lane, use early shots to preserve distance, and enter each forced reload with room above the boundary. Capture its full appearance, movement, hit response, defeat state, score change, and the next screen without naming its franchise identity.

Serpentine Encounter

Special Encounter

HintA long-bodied target creates a different defense pattern.

WhereContinue the run until the giant serpentine target appears.

Full detailRecord its occupied lanes and movement before committing to a firing rhythm. Use the chosen operator's knockback to protect the nearest boundary point, count every reload cycle, and preserve the complete defeat transition without exposing its identity.

Airborne Flock Encounter

Special Encounter

HintSeveral airborne targets share one special encounter.

WhereContinue clearing formations until the multi-target flock appears.

Full detailTrack each airborne threat separately, shoot the lowest one first, and avoid beginning a reload while another remains close to the boundary. Capture the full target count, movement, individual defeats, score changes, and completion transition.

Escalating Survival Run

You are here when: Later repeats of the defense playfield, transition screens, live score, and final result.

The pack follows only the visible survival mechanics and does not describe story structure.

Repeating Encounter Cycle

Survival Progression

HintClearing the documented encounters does not finish the survival run.

WhereContinue playing when the game returns to another defense formation.

Full detailTreat the new formation as a later cycle of the same run, keep the score and operator unchanged, and continue until the result screen appears. Preserve the transition without assigning a stage number or narrative meaning.

Movement-Speed Escalation

Survival Progression

HintLater threats close the distance more quickly.

WhereCompare target travel time after each completed encounter cycle.

Full detailMeasure from a consistent spawn point to the defense line and record the cycle context. Adjust lane priority and reload spacing to the observed increase, but do not publish a multiplier until repeated footage confirms it.

Durability Escalation

Survival Progression

HintLater targets require more sustained fire.

WhereCount confirmed hits on matching targets across later cycles.

Full detailUse the same operator and target type, exclude missed shots, and record the defeat frame. Plan extra reloads when durability rises, while leaving exact health and scaling values marked unverified.

Run Score Record

Score

HintThe survival attempt produces a score for comparison.

WhereCapture the score before play, after each transition, and at failure.

Full detailKeep a ledger containing operator style, cycle context, formation result, special encounter, reload count, breach moment, and final score. Repeat comparable actions before assigning points or bonuses to any event.

Natural Run End (missable)

Completion Boundary

HintMaximum verifiable completion ends with a documented survival attempt.

WhereContinue the escalating loop until a target reaches the defense line.

Full detailRecord the entire longest lawful attempt, including the final breach and result screen. Archive completion requires every verified mechanic and encounter plus one uninterrupted attempt from character selection through that final result.

Historical Network Ranking

You are here when: The score result, upload prompt, carrier connection screen, and ranking table or error response.

Rotating or discontinued network data is never presented as an ordinary requirement available today.

Network Ranking (missable)

Online Record

HintThe original release could compare scores through a carrier service.

WhereOpen the ranking or score-upload option if the preserved build still exposes it.

Full detailCapture the menu path, submitted score, connection request, endpoint response, displayed table, and date. If the carrier service no longer responds, retain the failure evidence and mark live placement unobtainable.

Discontinued-Service Evidence (missable)

Online Record

HintA dead endpoint is an archival result, not a missing score target.

WhereRecord the complete network error or unavailable screen.

Full detailPreserve the unedited connection attempt with handset clock, network state, application version, and error text. Do not emulate a successful submission or invent a ranking threshold when the historical service cannot answer.

Unverified Completion Boundaries

You are here when: Any undocumented control, menu, statistic, wave, score, reward, save, or retry screen exposed by a lawful remake build.

Unknown data remains visibly withheld instead of being padded into false completion instructions.