Rain98 Activities

Rain98 Activities

Find the currently documented Rain98 Demo activities, understand whether each one earns money or creates a shared moment, and recover from common interaction problems.

3 guides
3 start here
Activities guide hub
ProductActivities documented for Demo AppID 3738760 and named public show-floor episodes; base game AppID 3498720 remains unreleased VersionPublic Demo released 2026-10-16; older episode details are labeled and never treated as current balance PlatformWindows PC via Steam

Rain98 uses short interactive activities to turn ordinary life with Reina into play. Some are piecework that earns money, some are shared moments that support the story, and some do both indirectly. The current public Demo includes multiple activity styles, but their controls, timing, payout, and availability must be read from the scene you are playing rather than borrowed wholesale from an older convention build.

The strongest public evidence comes from Steam Demo AppID 3738760, released October 16, 2026, and independent hands-on coverage of nearby public test episodes. The base game at AppID 3498720 has not launched. That boundary matters when a preview describes a task but the public Demo presents a different name, order, or result.

Currently documented activity index

Gacha capsule piecework

Type: home piecework.

Known interaction: prepare capsules, place items inside, and submit filled capsules.

Player use: earn money through completed units.

Scope: described in PAX East and later hands-on coverage; exact public-Demo values belong to the live result screen.

Open the capsule guide

Bead picture task

Type: pattern-based piecework.

Known interaction: arrange bead pieces to reproduce a shown image.

Player use: a documented way to perform home work and engage with the tactile minigame style.

Scope: public gamescom latam and later Demo coverage; official English activity name remains build-sensitive.

Open the bead picture guide

Dance Dance Dream

Type: rhythm activity.

Known presentation: a low-poly 3D sequence with Reina dancing to music.

Player use: follow timing cues and enjoy a shared activity rather than apartment piecework.

Scope: expanded Demo coverage; exact judgments and any reported bug require the current build.

Prepare the rhythm activity

Apartment interactions

Type: story and daily-life tasks.

Known examples: laundry, cleaning, clothing help, playing cards, and object inspection appear across public builds.

Player use: develop the relationship and understand the 1998 setting.

Scope: not every observed event is guaranteed to be repeatable piecework.

Call this a currently documented index, not a complete minigame list. Rain98’s Steam page promises a variety of minigames but does not enumerate every activity in the Demo or final game. Earlier events exposed different slices, so absence from one public playthrough is not proof that an activity was removed.

Read the task before chasing speed

At the beginning of an activity, identify the target object, its unfinished state, the action that changes it, and the destination for a completed object. Then complete one full cycle slowly. A clean cycle reveals the task’s actual logic and prevents repeated partial work from looking like an input failure.

Only optimize after the result is visible. A timed capsule job rewards completed units in an older PAX report, while a pattern task can reward accuracy or completion. A rhythm scene uses audiovisual timing rather than object transfer. Treating every activity as a speed test causes avoidable mistakes.

Use the on-screen pointer, prompt, or highlight as the source for inputs. Controller glyphs and mouse interactions can differ. If a prompt changes while another device is connected, pause, return to one input method, and resume from the activity’s normal restart option.

Separate work, spending, and memories

Piecework produces money. Money supports living expenses, purchases, and opportunities to spend time with Reina. A shared activity can lead to an Angel Passport memory when the game explicitly awards a sticker. Those are linked stages, not one interchangeable reward.

After a work task, note the displayed earnings and the current story goal. Before buying anything, price the next necessary step. After a shared scene, watch for the Passport presentation. This sequence makes it clear whether you earned cash, opened an opportunity, or recorded a special memory.

The Systems hub explains the economy and Passport relationship. Do not replay a piecework task expecting a sticker unless the scene itself establishes that connection.

Improve object-based piecework

Object tasks become easier when you recognize states. An empty capsule is not the same object state as a filled capsule, and a filled capsule is not scored until it reaches the accepted destination. A bead placed in the wrong part of a pattern can be visually present without satisfying the reference.

Keep the pointer path short but readable. Work from the source area to the assembly area and then to the submission area. Finish the object already in progress before starting several more. If the game allows multiple prepared pieces, introduce that technique only after one-object cycles register consistently.

On a missed interaction, look for a blocked state: the container may need to be opened, the item may need a precise target, or the previous object may still be active. Release the current selection and re-enter the expected sequence. Restarting the whole activity should be the last ordinary recovery, not the first.

Approach rhythm and timing activities differently

For a rhythm activity, establish audio and display stability before judging your timing. Wireless audio delay, an unstable frame rate, or a television’s image processing can move the perceived cue. Use a stable display mode, avoid changing several settings at once, and compare a short repeatable passage.

Follow the cue language the activity teaches. Do not import Dance Dance Revolution terminology or arrow assumptions merely because the in-game name references dance. GamingTrend documents Dance Dance Dream as a 3D rhythm minigame, but the public evidence does not support a permanent chart list, scoring table, or controller map.

If a sequence stops responding, preserve the save and record where it happened. A single Steam discussion can signal that another player saw a problem, but it does not establish the affected build or a universal fix. Relaunching the official Demo and repeating the smallest scene is safer than editing files or installing an unofficial patch.

Use a result log that stays useful

Record
Example value
Why it matters
Product
Demo AppID 3738760
Keeps Demo behavior separate from the unreleased base game.
Activity and scene
Capsule piecework during an apartment work choice
Names the task and its narrative context.
Input
Mouse or one controller
Explains prompt and selection differences.
Completed result
Displayed units, score, or earnings
Uses the game's result instead of an inferred payout.
Failure point
Object would not enter its destination
Makes a support report reproducible.

Do not label a SteamDB BuildID as a player-facing version. If Steam does not show a semantic version, the release date and AppID provide a clearer scope. Screenshots should omit account names and private notifications.

Recover without losing the session

If an activity cannot be completed, first return to its instruction screen or immediate prompt. Reset the task through an in-game option when one exists. If it remains stuck, exit to the nearest safe menu and relaunch through Steam. Keep the save intact and avoid deleting configuration folders as a first response.

For a controller issue, disconnect duplicates and test the keyboard or mouse once. For a visual target issue, reduce display scaling conflicts and ensure the full game frame is visible. For a timing issue, stabilize frame delivery and audio latency. For an unclear reward, rely on the result screen and compare it with the amount held before the activity.

The best activity route is not the one that turns Rain98 into an endless grind. Complete enough piecework to support the next visible goal, use shared activities for their character and story value, and move forward when the scene is ready. The Demo’s atmosphere and relationship are part of the intended reward.

Public evidence used for this index

Recommended guides

Choose the guide that matches what you want to do next.

All Activities guides

3 focused guides with steps, checks, and current caveats.