Characters & story · Story spoilers

Narinig Mo Ba Ending: What the Game Files Show

This article discusses the Narinig Mo Ba ending, but every reveal stays inside a closed spoiler block. Above those blocks, it explains how the answer was checked: by reading the story files of the browser build on this site (b_67742981ff37), not by trusting search results or rumours. Each section separates what the files show from interpretation and from claims that still need a recorded playthrough. If you have not finished Day 6 of Narinig Mo Ba, play first.

Story spoilers on this page stay inside closed “Story spoilers ahead” panels. The title, summary and headings are spoiler-free.

Shop Journal card reading Behind the final conversation, beside an open book icon.

Spoiler boundary

Outside the closed blocks, this page covers only how the answer was checked and a few structural facts about the files. The blocks hold details from the last two days and the final scene; their titles give nothing away.

The answers come from a static review of the Narinig Mo Ba build this site hosts. Its story files were read in full; its scripts were decoded for names and constants only. So this page can say what the files contain; where it describes what a script does, that is what the files indicate, not something watched in play. No full playthrough of this build has been recorded yet.

Some structural facts are spoiler-free. The story files list six days of four visits each. In those files each conversation is a fixed list of steps, so whichever reply you pick, the next line and the order of events are the same. The scripts contain no save system, and START on the main menu begins at Day 1.

Story spoilers ahead Short answer: how many endings the files contain

One ending file was found in this export: a single ending scene in a single file, and no second ending file. The scripts indicate that its two final replies lead to the same credits and back to the main menu. That does not settle every route in play: what happens if you never open the book, for example, has not been verified by a playthrough (see "Claims that need testing" below).

What is directly shown

The story files are plain lists of steps: lines of dialogue, reply buttons, sounds, music changes and orders. They show what appears on screen and in what order. The block below retells the end of Narinig Mo Ba from those files, with short quotes.

Story spoilers ahead The last day and the final scene

On Day 6, Jomar tells you the body found near the canal has been identified: "a man named Miguel Jr.", who "went by Junjun". Lucia arrives last. She asks you to keep her paluwagan record book, says she has to leave town and adds: "Please don't open it." The book is left on your counter.

Clicking the book opens its page, and the script then loads the ending scene. A sudden sound and violins announce Lucia's return: "I told you not to open it." A heartbeat starts. She insists it was not her fault, says Junjun was trying to break into her house and adds: "I didn't mean to kill Junjun... It was an accident!" She bangs on the gate and shouts that she only wants the record book. Then Jomar arrives: "Hoy! What are you doing at this hour?"

Choices and outcomes

Across all six days, the story files show a reply changing the words your shopkeeper says, not what happens next: every story file is a fixed list of steps, and none of them opens a different path depending on your reply. Script-side handling was not decompiled, so this is what the data files show rather than a recorded run.

That matters if you arrived looking for a Narinig Mo Ba "all endings" tutorial. A video or post that lists several endings needs a date, a build and a recording before you trust it, because a search for another ending is not evidence that one exists.

Story spoilers ahead What the final replies change

The last choice offers two replies: "She killed Junjun…" and "Arrest her!". The scripts indicate that either one stops the music, rolls the credits for about 35 seconds and returns you to the game's main menu, where START begins again at Day 1. The review found no branch on this reply in the files and no second ending file; nobody has yet recorded both replies in play.

Facts versus interpretation

The story files record what characters say. They do not confirm that what a character says is true. That difference matters most in the final scene.

Story spoilers ahead What the files state and what they leave open
Statement What the build supports
The body by the canal is Junjun Stated by Jomar on Day 6
Lucia killed Junjun Her own words in the final scene
It was an accident Lucia's claim; nothing else confirms or rules it out
Junjun tried to break in and hurt her Lucia's claim only
Carlo was involved Lucia's accusation on Day 5; her own words at the end point elsewhere
Why the book matters to her Never explained; she only says it must not get "into the wrong hands" and later shouts "DON'T RUIN MY LIFE"

Earlier details are easy to connect: Junjun's small debt and job hunting, his shaken look on Day 3, and Lucia's big order for a payday celebration on the same day. Narinig Mo Ba never states a motive, so any link between them is interpretation, not fact.

Claims that need testing

If Narinig Mo Ba stops responding near the end, note the day, the visit, your browser and device. A stuck game is a bug report, not a different ending.

Read the record-book guide

The record-book guide (spoilers) explains what a paluwagan is, what the files show and do not show, and how to test the unopened-book question step by step. The Day 6 guide (spoilers) covers the visits before it. Or open the player and start from Day 1.

How we checked this

Checked the Day 5, Day 6 and ending story files of build b_67742981ff37, the script names around the record book and the credits, and the developers' 17 September 2026 update notes. Not checked: a full playthrough, including what happens on Day 6 if the record book is never opened.

  • Static review of the browser build hosted on this site (dialogue, item data, input map and scripts) (checked 24 September 2026)
  • “Phone users rejoice!” — touchscreen update, 17 September 2026 (checked 24 September 2026)

Back to the counter

Already playing? Your game keeps running in the tab where you started it, so switch back to that tab. The button below opens the player here and starts a new game from Day 1.

Back to the counter

Browser & loading help

A failed check can come from the browser, device, driver or a managed setting. Choose your browser below.

Chrome could not start WebGL2. Update and relaunch Chrome, then check graphics acceleration if your desktop settings allow it.

  1. Open the menu, choose Help → About Google Chrome, install any update and select Relaunch.
  2. On a computer, open Settings → System and check that graphics acceleration is available. Relaunch after changing it.
  3. On Android, update Chrome and the system from their usual update screens instead.
  4. Do not force experimental flags. On a managed device the setting may belong to your administrator.

Update macOS, iOS or iPadOS to update Safari. If native fullscreen is unavailable, use the expanded view inside this page.

  1. Safari updates with the system: use Software Update on your Mac, iPhone or iPad.
  2. The game does not need any experimental Safari settings. If WebGL2 still fails, try an updated, supported device.
  3. On iPhone and iPad most browser apps use Safari’s engine (WebKit), so switching browsers there usually changes little. The WebGL2 check on this site is what counts.
  4. Where native fullscreen is not available, Fullscreen expands the player inside the page. Rotating is always your choice.

Update Firefox, review its Performance settings and restart. If WebGL2 still fails, try another supported device.

  1. Update Firefox, then open Settings and find the Performance section.
  2. Use the recommended performance settings, or review the hardware acceleration option if your system shows one. Restart after a change.
  3. Option names vary between versions and systems. Do not bypass the compatibility safeguards that block unstable graphics drivers.

Update Edge and restart it. On desktop, check graphics acceleration. A managed device may need help from its administrator.

  1. Open Settings and more → Help and feedback → About Microsoft Edge to install updates, then restart.
  2. On a computer, look under Settings → System and performance for graphics acceleration, then restart.
  3. An organisation can control this setting. Ask its administrator instead of trying to override the policy.

Opening help does not save or necessarily pause the game. Restarting may lose this session.

Report a problem

These details show where the player stopped. Check the text, copy it, then add what you see on screen.

Send them to [email protected]. Opening this panel does not reload the game.

Read the full help page