What Should I Do When Progression Stops?
Four gates to check before concluding the game is stuck — and the version note that matters.
1 · Quick Answer
Don't immediately assume the game is stuck. First check the current interaction, dialogue state, latest request, and recent transition — in that order. Most "stuck" reports in story games mean the current interaction has not finished, and Narinig Mo Ba?'s scenes advance on completed conversations.
2 · The Decision Flow
1. Current interaction complete?
Order handed over, price handled, change returned.
2. Dialogue complete?
Text, animation, and audio fully finished — no rapid clicking.
3. Latest request complete?
Right item, price checked, payment and change handled.
4. Recent event triggered?
Give the scene transition a moment; quiet scenes are often the game changing tone.
Still no progress?
Check for known version-specific issues (see Version Notes below), then re-run the gates once more while letting the scene play without clicking.
3 · Why These Checks Matter
Narinig Mo Ba? presents itself as a cozy sari-sari store simulator, but it is a story-driven visual novel (E1 — official description). Its progression runs on a small set of structures:
- Interaction structure.Each customer visit is a self-contained transaction: request → item → price → counter → payment/change. An open transaction blocks the scene. (E3)
- Dialogue progression.Scenes advance on conversation completion; clicking through text early can leave a scene half-finished. (E3)
- Customer requests.Change-making is intentional design, not a bug — overpayment is part of the transaction. (E3)
- Transitions.When the routine is complete, the next story beat needs room to trigger. (E3)
- Known bugs.It shipped as a 4-day jam entry (E1); progression bugs are possible, and one late-story softlock was real enough to fix in v1.1.1. (E1)
4 · Evidence
Game structure (store sim / visual novel, story-driven)
E1 — Official itch.io description and tags. Verified 2026-09-17.
Interaction / dialogue / request / transition checks for stuck scenes
E3 — Corroborated across independent walkthroughs grounded in official itch.io comments. No official progression manual exists, so these cannot be E1/E2.
Controls (click take/place, hold return, right-click price, edge-look)
E3 — Community-documented, consistent across guides; the developer has not published a formal controls manual.
v1.1.1 fixed a late-story softlock; v1.1.0 added official touchscreen support
E1 — Official devlog, 2026-09-17.
5 · Version Notes
v1.1.1 · 2026-09-17 — Small bugfix that fixes a softlock towards the end of the story. If the game stopped progressing near the ending, refresh the itch.io page to pull the updated browser build. (E1)
v1.1.0 · 2026-09-17 — Official and improved touchscreen device support (tablets, iPads, phones). The original build was mouse-and-keyboard first. (E1)
post-jam · 2026-07-25 — Browser build released on the itch.io page after Game Jam Los Baños 2026. (E1)
6 · What This Guide Cannot Determine
- Whether a missed dialogue detail is required for a specific story event.
- Which dialogue choice to pick, or whether choices branch the ending. No official route map is published — be cautious with guides that claim one.
- Whether an unusual detail is a confirmed progression trigger. Observation may help; GameMeta does not treat every strange moment as a mechanic.
7 · Related Tool
Run the deterministic check: report what is happening right now, get a Next Check with its evidence level.