Game Integration
Before writing game code, your agent checks what your installed game can really do and how a mod loads into it. Then it builds one small connected slice that works in game. Server and provider setup carries on alongside this research.
Check The Game First
- Your installed build. The agent records your game version and the mod loader it would use, and checks that loader supports that exact version.
- Real sources. Every game fact comes from the game's own SDK, a loader's documentation or a small test. Anything unconfirmed is marked unknown, with the next small test to try.
- A blocker is not a dead end. A missing piece stops only the work that needs it. Server and provider setup continue.
The repository includes an Elden Ring reference port. It builds and passes its own offline checks, but it has not been verified in game, and it does not mean other games are supported.
What The Plan Covers
- Chat in game. A native chat box that shows who the player is talking to, takes over the controls while open and gives them back on send, Esc, pause, loading or when the character leaves.
- Not blocking the game. Network calls run in the background; the game never waits on the server.
- Replies and voice. Where subtitles appear, and how voice plays if you want it.
- Actions. Which things the game already knows how to do, and how to check they happened.
- Saves and sessions. Which save a conversation belongs to, and what is cancelled on loading or quitting.
- Normal loading. The mod starts with the game through its normal mod loader, with no extra command each session. Where a game needs an offline loader profile (Elden Ring uses me3 offline), that is the normal route. Never launch a modded game through online play or past anti-cheat.
Game Awareness
Characters should know what the game can actually see right now: where they are, who is nearby, what just happened. For each value, the agent records where it comes from and how fresh it is. Old or unreadable values are sent as unavailable, so the character does not invent them. Lore and guesses stay separate from observations.
The First Connected Slice
The first prototype is the loop from your gameplay design, working in the game: the player opens the chat box, types to a visible character and gets a reply, with voice if you asked for it. After a one-time install, the mod loads through the game's normal mod loader and connects by itself. If the server is not running, the game stays playable and says so.
- Developer tools stay optional. The template's console client and mock replies are diagnostics, not a required warm-up and not the prototype.
- In-game first. Use the game's own UI first, then a tested in-game rendering hook. An external window or desktop overlay is a last resort, adopted only with your agreement once nothing in game works. It is never presented as the finished mod.
Actions
The AI can only ask for an action. The game runs it only through its own handler for that action, after checking the target and conditions, and the action counts as working only once the game later sees the result.
- The first conversation is set up with no actions on both the server and the game side. Actions are added one at a time once their handlers are ready.
- The template's own example settings still allow
follow_playerfor older installs, so a new mod turns actions off explicitly.
A worked example is in WAVE_ACTION.md.
Dashboard Pages
Your mod's server includes a dashboard you can extend with your own pages. See UI_GUIDE.md.
Evidence
A successful build does not show the mod works in game. The kinds of evidence and the in-game checks are defined once, on Testing.
Full reference: docs/ENGINE_PLANNING.md and docs/feature-recipes/PORT_RECIPES.md.
Next step: Set up providers and voice.
KAGRENAC
Get started