Rain98 Wiki

The Rain98 Wiki is a lookup for what the game has actually named or shown in public material. It begins with a small cast, a Tokyo split between the present and 1998, Reina’s apartment, portions of Shibuya, and everyday objects that carry the late-1990s setting. Because the base game is still Coming Soon and the public Demo stops in Chapter 2, every index here is currently documented, not complete.

Use the product and source fields before treating an entry as playable. A fact shown in Demo AppID 3738760 describes the downloadable October 16 build. A statement on the base-game store page for AppID 3498720 describes the intended full game. A show-floor preview proves that an element appeared in that episode, not that it kept the same role in the public Demo.

Find a character without guessing the cast

The Characters index starts with Reina Amehara and the unnamed protagonist because both are anchored by the official Steam description. Reina is voiced by Rio Tsuchiya and calls herself “Angolmois.” Those two labels refer to one person: Angolmois is not a second character to count separately.

The protagonist is the player’s viewpoint and is described as moving from today’s Tokyo into 1998. Public material deliberately leaves much of the character’s identity unresolved. Use “the protagonist” unless the active build supplies a canonical name. Do not convert a player-entered name, pronoun assumption, or preview author’s shorthand into a universal identity.

Characters who appear later in the Demo should enter an index only with a displayed name or an official role. A voice credit, trailer cut, or discussion nickname can be a clue, but it is not sufficient on its own to settle relationships, motives, survival, or the final cast.

Read places as scene boundaries

Rain98’s official premise spans today’s Tokyo and 1998 Tokyo. The public Demo centers on shared life in an apartment and excursions into rainy Shibuya. Independent current coverage also describes an isometric exploration view for parts of the city. These are useful navigation facts without implying that every street joins into an open world.

A place record should contain the displayed name, scene type, first known appearance, product scope, and what the player can do there. “Apartment” can be a story location, interaction space, and piecework hub. “Shibuya” can be the broader district setting while individual shops or streets remain distinct scene destinations.

Directions need a stable starting point and visible landmark. Avoid publishing a full map from an older event build when the public Demo can rearrange scenes or gates. If a path is not available, return to the active objective before declaring the route broken.

Classify objects by use, not appearance

Rain98 fills its scenes with objects associated with late-1990s Tokyo: public phones, arcades, magazines, cards, older electronics, shop goods, and domestic items. Developer interviews emphasize the cultural role of those details. Their presence creates a lived-in era, but not every object is loot, a collectible, or a quest requirement.

Use four practical types: story tool, activity object, purchasable item, and environmental detail. The Angel Passport is a story tool and progress record. Capsules and bead pieces are activity objects. Food or other displayed goods can be purchasable when the game shows a price. A poster or phone can remain environmental context unless the scene assigns an action.

Leave rarity, price, effect, and collection status blank when the build does not show them. An empty field is more useful than a confident but false attribute that sends a player searching for an unlock that does not exist.

Use a scope-first lookup

This structure also helps when names differ by language. Keep the English Steam name for the English page, preserve the original Japanese name when officially displayed, and list a transliteration as an alias rather than a separate entity.

Keep spoilers attached to the right scene

Rain98 is a psychological suspense story. Character motives, the meaning of the ritual, memories, and the Demo’s stopping point are designed to be discovered. A lookup can answer “who is this?” without revealing a later event. Put a spoiler warning immediately before any field that depends on a specific chapter outcome.

Avoid using hidden Steam achievement data or extracted files to fill gaps. A hidden entry is intentionally not part of the ordinary public achievement view. Leaked scripts, private test material, or datamined assets do not become acceptable evidence because a public Demo exists.

When two public interviews conflict, preserve the conflict instead of choosing the more dramatic statement. For example, older and newer discussions of possible endings use different framing. Until current developer material or the full release settles it, no character page should promise a fixed ending count.

Correct a mistaken identity

If two labels appear to describe the same person, compare the scene, voice actor, official description, and whether one is introduced as a title or alias. Reina and Angolmois are the clearest current example. Merge aliases under one canonical card rather than creating duplicate biographies.

If an event preview names an object or activity differently from the public English Demo, prefer the current displayed term and keep the preview wording as an attributed alias. Media translations such as “happiness stamp” can help players search, but the current Steam copy’s “sticker” should lead the English Passport record.

If a claimed place, item, or character has no accessible primary source and only one copied summary, leave it out. The Wiki should become broader as Rain98 releases more public material, not broader by turning rumors into pages.

Continue from an entry

A character lookup often leads to a system or activity question. Use Systems for the Angel Passport and money loop, Activities for hands-on tasks, and Guides for Demo pacing. Use Updates when an entry depends on whether later Chapter 2 material has actually shipped.

The current Wiki intentionally stays small enough to trust. At full release, its cast, locations, objects, and relationships will need a fresh pass against AppID 3498720. Until then, every card should tell a player what is known, where it applies, and what remains unresolved.

Primary references

• Rain98 base game on Steam
• Rain98 Demo on Steam
• Creative Bloq interview and BitSummit hands-on