The Angel Passport is Rain98’s in-story record of special memories with Reina. When the protagonist does something meaningful for her, the game can award a sticker and move the pair’s world-ending ritual forward. Public developer material and hands-on coverage describe the long-term objective as filling the Passport with one hundred stickers. The October 16 Steam Demo does not present a verified, complete route to all one hundred.
Think of the Passport as a narrative progress book, not an experience bar. It tells you that a shared event mattered. It does not by itself reveal a hidden affection value, a rarity tier, or the exact branching consequence of every choice.
Recognize a Passport-worthy moment
The official Demo description uses a simple rule: doing something special for Reina earns a sticker. In practice, begin with her explicit request and complete the associated scene. A request can involve conversation, an apartment task, spending money, an outing, or another shared activity. The sticker presentation—not the player’s guess—confirms the reward.
Do not count ordinary object descriptions as sticker progress. Rain98 uses period details to build its 1998 setting, and many interactions are valuable for atmosphere or character context without being Passport entries. Likewise, completing piecework can pay money without automatically producing a memory.
Story request
Watch for: Reina asks for help, attention, an item, or time together.
Player action: follow the scene objective and finish the whole interaction.
Passport result: wait for an explicit sticker presentation.
Piecework
Watch for: a short home job with an output or result screen.
Player action: complete the task to earn its displayed money.
Passport result: none should be assumed unless a later scene awards one.
Optional observation
Watch for: an object, room detail, or Shibuya landmark with a prompt.
Player action: inspect it for context and possible dialogue.
Passport result: treat it as worldbuilding until the game says otherwise.
Track stickers without spoiling the story
Use a memory log built around scenes rather than guessed requirements. Record the chapter, the request in your own words, the activity or purchase involved, and the displayed sticker moment. Avoid writing a result for a choice you did not play. This keeps the log useful while preserving alternate dialogue for a later run.
A minimal entry could read: “Chapter 1 — Reina requested help in the apartment — task completed — Passport presentation appeared.” It does not need an invented sticker name. If the game displays a name or icon, copy it exactly and distinguish it from your own description.
The public Demo ends before Chapter 2 is complete, so any “all stickers” list published during this period needs a clear Demo boundary. An empty number in a sequence does not prove a missed collectible; it can belong to later Demo material or the unreleased base game.
Connect money to memories carefully
Money can enable food, outings, purchases, or activities, and those moments can become special experiences. That relationship does not mean cash converts directly into stickers. First identify the next visible goal, then earn and reserve enough to pursue it. Let the resulting scene establish whether the Passport advances.
If you spend everything on an optional object, return to an available piecework task rather than assuming the save is blocked. The official game description makes home piecework part of the normal living loop. Exact earnings and prices belong to the active Demo build, so record your displayed values instead of importing figures from an older event preview.
The Systems hub explains how money, piecework, achievements, and the Passport stay distinct. The Gacha Capsule guide handles one documented piecework activity without claiming it grants a sticker.
Understand the one-hundred-sticker goal
Multiple public previews and developer interviews describe one hundred stickers or memories as the ritual target. Earlier English coverage sometimes used “happiness stamps,” while the current Steam description says “stickers” in the “Angel Passport.” These are vocabulary differences around the same disclosed goal, not separate point systems.
The number belongs to the story’s larger structure. It does not establish that the Demo contains one hundred activities, that each chapter has an equal share, or that a missed scene permanently blocks completion. It also does not settle how the retail game handles branches, endings, or repeat play.
Use the number to understand Reina and the protagonist’s stated plan. Use the game’s actual Passport screen to understand the entries available in your build.
Recover when a sticker does not appear
If an expected presentation is interrupted by a crash, preserve the save and relaunch through Steam. Repeat only the immediate scene if the game offers a normal save boundary. Do not edit save data or use achievement tools to manufacture an in-story sticker; the Passport and Steam Achievements are separate systems.
Keep Demo and launch progress separate
The developer plans to expand the Demo to the remainder of Chapter 2 and says a player can continue from the point reached before that Demo update. This supports continuity inside the Demo’s future expansion. It does not confirm that Passport progress transfers from AppID 3738760 to base AppID 3498720.
At full release, treat the retail Passport as its own record until the game or developer explicitly explains migration. Revisit sticker names, chapter positions, money prerequisites, and branch behavior. A Demo memory can remain useful context without being a guaranteed retail unlock.
For now, a strong Passport route is simple: listen to Reina’s current request, complete the whole shared activity, preserve enough money for visible needs, and record only stickers the game actually presents. That method respects both the narrative and the limits of the public build.