← Projects

2025 – 2026

Here To Slay

An unofficial digital version of the Here to Slay card game, with an Electron desktop client and an event-driven backend on Apache Kafka.

  • React
  • TypeScript
  • Electron
  • Java 21
  • Apache Kafka
  • Docker
  • Nginx

Here to Slay is a fantasy strategy card game by Unstable Games, TeeTurtle’s games label and the team behind Unstable Unicorns. Each player builds a party of heroes, tries to slay monsters and, of course, sabotages their opponents along the way. This project is an unofficial digital version of the game, which I built to study distributed systems in practice and to play with friends.

The client is a React and TypeScript desktop app running on Electron. It talks to the backend through a WebSocket gateway, and the whole stack runs with Docker Compose behind an Nginx reverse proxy.

The backend is event-driven: the gateway, lobby and game-engine services never call each other directly and communicate only through an Apache Kafka cluster (3 brokers, KRaft mode). Compacted topics hold the state of the lobbies and the list of players in each match.

Disclaimer

  • This is an unofficial, unlicensed fan project. It is not affiliated with Unstable Games or TeeTurtle, and it is not sponsored, endorsed or approved by them.
  • “Here to Slay”, “Unstable Games”, “TeeTurtle”, card names, artwork and all other game elements are trademarks and intellectual property of their respective owners. I claim no ownership of any of them.
  • The project is non-commercial: it is free, it is not sold and it generates no revenue of any kind. It exists for learning and portfolio purposes only.
  • Card images were taken from the official Unstable Games wiki.
  • If you enjoy the game, please support its creators and buy the original Here to Slay.
  • If you hold the rights to any of these elements and want them removed, email me and I will take the content down as soon as possible.

Writing about this project

  1. Here To Slay, part 1: how it all started

    My first paycheck, a card game I saw on TikTok and a two-hour match at a barbecue. That's how the idea for an online version of Here To Slay was born.

  2. Here To Slay, part 2: the first month

    From an Electron login screen to the first playable match in a week. What the architecture looked like before Kafka, the match as a state machine and card effects built like Lego pieces.

  3. Here To Slay, part 3: introducing Kafka

    How an event-driven systems course became the perfect excuse to take the single server apart into a gateway, a lobby and an engine that only talk through topics on a Kafka cluster.

  4. Here To Slay, part 4: Kafka Streams and in-game achievements

    A service that only watches matches and turns patterns into alerts like First Blood and Combo, using time windows, state stores and even Allen's interval algebra.

  5. Here To Slay, part 5: the new interface

    Why the first thing after the course was redesigning every screen, where the idea of a tavern at night came from, and how rolls, cards and animations started following one system.

  6. Here To Slay, part 6: a table that talks

    The "I'm ready" button in the lobby and a chat that travels the same path as every play, with a length limit, a rate limit and a history for whoever arrives late.

  7. Here To Slay, part 7: a new engine for the rules

    Why the effects system from part 2 stopped scaling once the real deck arrived, how each card became a script of steps that can stop and wait for the player, and what it was like to think this change through.

  8. Here To Slay, part 8: going live

    From a game that only ran on my machine to an executable that connects to a 1 vCPU, 2 GB server, the load test that found a lobby bug and what the first matches with other people showed.

  9. Here To Slay, part 9: the visual side and Electron

    Why Here To Slay's client is a TypeScript web app inside Electron, what that choice costs and whether it's worth swapping for a tool made for games, like Godot or PixiJS.

  10. Here To Slay, part 10: how a bot should think

    Before I started developing Here To Slay's bots, I read up on how other people build game bots. What I found about play styles, about scoring every move and about reacting at a table with several players.

  11. Here To Slay, part 11: the bots, hands on

    Halfway through developing Here To Slay's bots. How the bot receives the match and acts like a player, how it scores every move and the exact dice math.

  12. Here To Slay, part 12: threat, styles and difficulty

    The second half of Here To Slay's bots: when to challenge, how the bots team up against the leader, the three styles and the difference between the normal and advanced levels.