The Rain98 capsule activity is a home piecework job built around a short production chain. Public hands-on coverage describes three essential actions: prepare a capsule, place an item inside it, and move the filled capsule into a collection box. Completed units earn money. An older PAX East 2026 build used a short timed session and tied earnings to output, but the public October Demo’s own instruction and result screens control its exact timing and payout.
This is not a randomized character-pull system and it does not ask you to spend premium currency. “Gacha” describes the capsule-toy object being assembled inside Rain98’s story world.
Learn the three object states
Complete one capsule through all three states before trying to prepare several objects at once. If the result counter increases only after submission, partially filled containers do not contribute until they reach the box.
Build a clean hand path
Identify three zones on screen: capsule supply, item supply, and completed-unit destination. Move in the same order every cycle. Consistency reduces the time spent searching for the next target and makes a missed action obvious.
Use deliberate placement first. If an item returns to its source or the capsule does not change state, release it and aim for the highlighted interior rather than dragging faster. If the filled capsule refuses the box, ensure the filling step visibly completed before moving it.
Once five or six cycles register cleanly, shorten pointer travel while preserving the same order. Do not add parallel preparation unless the current Demo clearly supports it; unfinished objects spread across the screen can be harder to diagnose than one complete pipeline.
Read the clock and result separately
Raider King reported roughly two minutes in the PAX East episode and described earnings based on the number of capsules completed. That observation proves the activity used a short production challenge in that public build. It does not establish a permanent duration, exchange rate, or maximum for Demo AppID 3738760.
During your session, look for the displayed clock or end condition before starting. At the result screen, note completed units and money awarded as separate values. If there is a quality or error field, record it exactly rather than assuming every incomplete capsule is penalized in the same way.
Compare attempts only within the same build and input setup. Switching from mouse to controller, changing window scaling, or using a later Demo update can alter your route and make the numbers less comparable.
Fix common capsule failures
Item will not enter
Confirm that the capsule is in its open or empty state. Drop onto the active target area, not the shell edge, and release before selecting another object.
Capsule will not submit
Look for the visual change that marks it as filled. An item resting near a capsule is not necessarily registered inside it.
Counter does not rise
Follow one unit all the way into the destination. The activity can count completed submissions rather than intermediate assembly.
Prompts flicker
Disconnect unused controllers and choose one input method. Relaunching with a single device gives the activity one stable pointer source.
Screen target feels offset
Return to a standard resolution or display mode and make sure the whole game frame is visible. Avoid operating-system scaling changes during a timed attempt.
Payout differs from a preview
Use the value shown by your Demo. Public event episodes and the downloadable build do not share a guaranteed economy.
If the activity remains blocked after a normal reset, preserve your save, exit through the menu, and relaunch from Steam. Do not install a community executable or modify save data for a piecework task.
Decide how long to work
Capsule piecework exists to support the apartment economy, not to replace the story. Before starting another run, identify the purchase or living expense you are funding. Stop when you have that amount plus a small reserve. This prevents unnecessary repetition and keeps the next Reina scene close to the work that enabled it.
The activity’s money reward does not automatically produce an Angel Passport sticker. A later purchase or shared moment can become special, but the game must show the Passport award. Keep work results and memory results as separate lines in your session notes.
If another job becomes available, compare it by comfort and reliable completion before comparing raw payout. A slightly lower result from a task you can complete cleanly can be more useful than a higher advertised result based on an older build or an error-prone route.
Record a reproducible capsule result
Write down Demo AppID 3738760, the calendar date, the input device, the activity’s displayed duration, completed units, money awarded, and any failed object state. A support report should describe the exact transition that broke: “filled capsule did not enter the destination” is more useful than “gacha is bugged.”
Include a screenshot only when it does not expose your Steam account, private notifications, or story material beyond the activity. Use the game’s displayed labels. Do not call a SteamDB BuildID a version number or use an event preview date as proof of the current executable.
For the larger money loop, return to Systems. For other activity types and input recovery, use the Activities hub. The capsule job becomes manageable once each object completes a visible empty-to-filled-to-submitted route.