NASUBI

What NASUBI Is

NASUBI is a first-person psychological endurance simulation set inside an almost empty room. The first-party description frames the player as a participant in a controversial television experiment, stripped of personal possessions, supplies, and ordinary human contact. An analog rotary phone is the one stated connection to the outside world. That narrow setup makes observation more important than exploration across a large map.

FunB4nan and st1sdan describe the game as inspired by the late-1990s Japanese program Susunu! Denpa Shōnen. The browser build visibly opens with that inspiration notice before entering the Godot game. This page treats the game as fiction inspired by a real television premise; it does not present its events as a documentary reconstruction or claim that every mechanic reproduces a historical incident.

The public release is still marked in development. It supports HTML5 and Windows, lists keyboard and mouse input, English and Russian, subtitles, and an interactive tutorial. The creators recommend the downloadable desktop build for better performance. The embedded edition here is therefore useful for immediate browser play, but performance and input capture may differ from the desktop package.

NASUBI Beginner Guide

1. Click Play and wait through the opening notice and Godot loading sequence. Click inside the game area before moving so the browser gives pointer and keyboard focus to the embedded runtime.
2. Use WASD to orient yourself before interacting. Scan the room slowly, note the phone and any object that produces an interaction prompt, and avoid assuming every prop can be collected or used.
3. Press E only when the game presents a useful target. The room is intentionally sparse, so a changed object state, new sound, prompt, or phone event may be more meaningful than physical distance traveled.
4. Use C to crouch when the tutorial or object height makes it relevant. ESC pauses or resumes the build; it is also the safest first response when pointer capture or the current view feels unclear.
5. Treat each new event as evidence. Recheck the phone, readable material, and the immediate room after a transition instead of inventing a fixed sequence from an earlier attempt.

Careful First-Run Tips

• Let the opening and loading screens finish before diagnosing a black screen. The browser export may take longer than the surrounding page.
• Read the current prompt before clicking. A community report mentions inconsistent return-button labels, but that report is not enough to publish one universal mouse instruction.
• Do not assume a stuck door or object is a puzzle solution. The public comments include bug reports, and the developer still labels the release in development.
• Keep audio and subtitles available. In a sparse room, a call, sound cue, or text change can carry more information than movement.
• If mouse look stops after clicking outside the frame, pause, click back inside, and follow the build’s focus behavior before restarting.