2 min read

Rift Relay: From Concept to Circuit

Rift Relay shows a different side of the arcade: a puzzle loop, a cleaner extraction boundary, and a useful test for standalone game repos.

Rift RelayGame DesignArchitecture

Rift Relay matters because it is not Dungeon Dash with different art.

The core idea is more puzzle-like: connect, route, react under pressure, and make the board state legible. That gives MBOP Arcade a second kind of play, and it gives the technical architecture a different kind of stress test.

Action games reveal input, collision, and screen-space problems. Puzzle games reveal state, reset, scoring, level generation, and clarity problems. The arcade needs both.

Why the extraction boundary matters

Rift Relay also became an architecture exercise. The long-term arcade plan is not to keep every game buried inside the shell repo forever. Each game should be able to live as a standalone repo while the arcade mounts it through a cabinet adapter.

That means the shell should own things like:

  • Route and game registration.
  • Account and patron state.
  • Score submission hooks.
  • Shared audio cues where appropriate.
  • Exit links and cabinet chrome.

The game should own things like:

  • Runtime state.
  • Input handling.
  • Game-specific audio choices.
  • Board generation.
  • Win and loss conditions.

The cleaner this boundary gets, the easier it is to let different agents work on different games without breaking the arcade platform.

What Rift Relay contributes

Rift Relay contributes a second design language to the arcade. It asks for concentration instead of only reflexes. It also gives the project a repeatable extraction story: define the contract, keep shell concerns out of the game package, and verify the mount path after every meaningful change.

That story is not glamorous, but it is what lets the arcade become a collection instead of a one-off site.

What to watch next

The most important next checks for Rift Relay are practical:

  • Does it still mount correctly in the arcade cabinet?
  • Does input work across keyboard, pointer, and any intended gamepad path?
  • Does the standalone repo have enough documentation for a future agent to resume?
  • Does the arcade shell treat the game as a package rather than a private folder?

If those stay true, Rift Relay becomes more than a game. It becomes the pattern for bringing future games into MBOP Arcade cleanly.