Bloody Rails

Back to home

Group project for Software Engineering

Bloody
Rails

A first-person investigation game set aboard a passenger train in the late 1800s.

Find the truth before the final stop.

Built with Godot Class MVP, now in continued development
Explore the project
Bloody Rails cover art: a black locomotive beneath a red title, silhouetted against an orange sunset.
Project cover art View full image

On board

A case unfolding between stations.

Move through the passenger cars, speak with the people aboard, and follow the evidence.

First-person view down a dim passenger carriage toward a door, with forest visible through the windows.
Looking through one of the passenger cars. View full image

The story

Five days. One murder to solve.

Before the train reaches its final stop, the player must question suspects, collect clues, and take notes to discover who murdered Adrian.

On the train

WS
Move forward and back
E
Interact
Enter
Advance dialogue
Tab
Open or close notebook

Inside the train

Gameplay captures from the supplied build, from the forest outside to conversations on board.

Elevated view of the dark train moving through a low-poly evergreen forest.
The train crossing a forest at night. View full image
A paper note on a table beside a curtained train window.
A note beside the carriage window. View full image
A conversation with the doctor, shown in a dialogue panel inside the train.
Dialogue with the doctor. View full image
Passengers sitting in booths and at tables in the dining car.
Passengers in the dining car. View full image
An empty seat beside a train window, framed by dark curtains.
An empty seat beside the carriage window. View full image
A locomotive and circular track shown in a Godot preview with a 50 percent loading bar.
Early prototype capture of the locomotive and track. View full image

My contribution

A path from feature work to a stable build.

I handled DevOps, backend work, and game configuration, and developed the one-way integration ladder from feature branches through THE RING, MUDPIT, and POND to MAIN.

I’m continuing development beyond the class MVP to expand and complete the game.

The integration ladder

Changes move forward through the team’s development path.

  1. Feature branches Build features in isolation.
  2. THE RING Check how completed features work together.
  3. MUDPIT Make major changes in the working build.
  4. POND Handle QA and polish.
  5. MAIN Keep the stable release.

Project timeline

From class MVP to the next build.

  1. Spring 2026: Software Engineering MVP

    The team built Bloody Rails as a group project for my Software Engineering class and presented it as the class MVP.

  2. In progress

    Expanding beyond the MVP

    I’m continuing development to bring the game closer to a complete experience.

A group project.