Skip to main content

​
Build with Reverse

Connect Reverse to the way your server already works. Start with the feature you want to build, then choose the API for the machine where it runs.

​
Choose your integration

Record a match

Start when the arena is ready. Save when the game finishes. Keep the replay ID with your match.

Add a Watch button

Authorize a selection and start local playback, or send a viewer through your lobby.

Make it your own

Add menu actions, hotbar controls, and game-specific replay events.

​
Learn the API from the beginning

The introduction builds one recording integration a little at a time. Start with service discovery, create a recording, then add arena bounds and participant selection to the same example.

​
Which API do I need?

Shared data contracts live in api; menu action contracts live in api-gui. Player and recorder can run on separate machines, so keep their role-specific bindings separate too.

​
Browse by task

Authorize before playback. Raw storage and playback methods are building blocks, not catalog permission checks. Use a trusted actor and the catalog when serving a player’s selection.

​
Going deeper

Add custom recordables for portable game-specific events. Implement terrain providers or protocol adapters only when extending the runtime itself. Ordinary minigame integrations do not need to replace these internals.