Back to Home11/19/2025, 4:20:29 PM

Show HN: Terminal roguelike using Entity-Component-System in pure Ruby

3 points
1 comments

Mood

supportive

Sentiment

positive

Category

tech

Key topics

Ruby

Entity-Component-System

Roguelike Games

The author is sharing a terminal roguelike game implemented using Entity-Component-System architecture in pure Ruby, showcasing a technical achievement.

Snapshot generated from the HN discussion

Discussion Activity

Light discussion

First comment

3m

Peak period

1

Hour 1

Avg / period

1

Comment distribution1 data points

Based on 1 loaded comments

Key moments

  1. 01Story posted

    11/19/2025, 4:20:29 PM

    3h ago

    Step 01
  2. 02First comment

    11/19/2025, 4:23:46 PM

    3m after posting

    Step 02
  3. 03Peak activity

    1 comments in Hour 1

    Hottest window of the conversation

    Step 03
  4. 04Latest activity

    11/19/2025, 4:23:46 PM

    3h ago

    Step 04

Generating AI Summary...

Analyzing up to 500 comments to identify key contributors and discussion patterns

Discussion (1 comments)
Showing 1 comments
davidslv
3h ago
I spent 5 years building a roguelike game in pure Ruby (no game engines) to explore Entity-Component-System architecture and event-driven patterns outside of typical Rails applications.

Full disclosure: The project benefited significantly from AI assistance in the later stages to keep momentum going while balancing a full-time job and family. I used AI as a coding partner - I made all architectural decisions, reviewed every change, and stayed in control of the direction. It let me focus on the interesting problems (ECS design, event systems) rather than grinding through boilerplate.

The game runs entirely in the terminal and uses the same architectural patterns we use in production web apps - ECS for entity management, pub/sub for events, observer patterns for game state.

Why Ruby? Honestly, because it's the language I know best, and I wanted to prove you could build a game without reaching for Unity, Godot, or even a Ruby game library. It's all vanilla Ruby.

The codebase is fully open source and I've also written a book about the process (5 years in the making) that walks through the architecture decisions: https://www.amazon.com/Building-Your-Own-Roguelike-Hands-ebo...

Technical highlights:

- Entity-Component-System from scratch - Event-driven game loop - No dependencies (just Ruby stdlib) - Runs in the terminal

I'd love feedback from the HN community, especially on the architecture patterns. Happy to answer any questions about the implementation.

Thank you, davidslv

ID: 45981410Type: storyLast synced: 11/19/2025, 5:38:53 PM

Want the full context?

Jump to the original sources

Read the primary article or dive into the live Hacker News thread when you're ready.