Case I

The Bell at
Mourning House

A sealed townhouse bell rings every night. Follow the evidence through rain-dark streets, decide what is truly haunting the borough, and determine which secrets deserve daylight.

Begin the investigation

Playable prototype

Open the casebook

Select locations, inspect their points of interest, and gather three pieces of evidence before forming your conclusion.

Best experienced in a modern desktop browser. The prototype contains no save system yet.

Design direction

Investigate. Deduce. Decide.

Purposeful searching

Every meaningful interaction reveals evidence, contradiction, character, or atmosphere.

Uncertain causes

A haunting may conceal a crime. A rational explanation may conceal something stranger.

Consequential endings

Understanding the truth does not automatically tell you what should be done with it.

Build the borough with us

Contribute with a coding agent

You do not need to prepare a development environment by hand. Open a coding agent with GitHub access, copy the complete prompt, and answer its focused creative questions. It should propose one small playable improvement before changing code.

Install or open your preferred coding agent.
Paste the kickoff prompt shown here.
Review its proposed slice and answer questions.
Let it test the change and open a pull request.

Manual instructions Browse open work →

Complete kickoff prompt

I want to contribute to The Unquiet Borough, a 2D Victorian point-and-click investigation game built in Godot 4.6.

Repository: https://github.com/TsilenT/unquiet-borough

Please clone or open the repository and inspect README.md, CONTRIBUTING.md, docs/GAME_CONCEPT.md, project.godot, the existing GDScript, and current GitHub issues before proposing changes. Use Git, Godot, and GitHub directly rather than asking me to run routine commands.

The settled foundation is a point-and-click investigation loop: visit locations, inspect meaningful hotspots, collect evidence, form a theory, and choose a consequential resolution. Crafting and survival are stretch goals; do not add them unless the core investigation clearly benefits.

First, ask me no more than three focused creative questions. Then propose one small, player-visible, playable slice that fits the design pillars and can be completed in a focused pull request. Wait for my approval of that slice before implementation.

After approval, create a feature branch, implement the slice, add or update appropriate verification, run the Godot import/runtime checks and web export verification, inspect the final diff, and open a pull request. The pull request must explain the player-visible result, design reasoning, changed files, exact checks run, and any asset sources or licenses. Do not push directly to main.