Game event log

Your AI adds a small log to your game that writes down what happens, such as a level started or a player died, in a plain file or in the browser on the player's own device. It keeps no accounts, device ids or IP addresses, sends nothing anywhere, and records nothing until the player says yes.

When you need it

Before you want to learn anything from your players. All the other game data recipes read the list this one writes. Players hand you their file with a copy button, because nothing leaves their device by itself.

Say this to your AI

Use the game event log from Spielerando. First draw what is supposed to happen in my game as a Mermaid state diagram, and list only the events that answer a question I have. Then play one test round, check the log against the diagram with checkAgainstPlan and show me the counts. Ask the player before recording anything, keep nothing personal, and tell me plainly if anything does not fit.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP

Settings

maxEvents (5000): The most events kept. Past this, the oldest whole sessions are removed, so no half sessions remain.
maxTextLength (40): The longest text a value may be. Short labels only, so that no one can log a chat message by mistake.
flushEvery (20): Events are written in groups of this size, so the game does not stutter.

Your AI gets the code

The finished code and math come through the Spielerando connection, so your AI can use them right away. Connect your AI

Common questions

how do i track what players do in my game without an account

Write events to a list on the player's device, with a random label for each sitting that is thrown away afterwards. You never learn who anyone is, and players send you the file themselves if they want to.

what happens if a player closes the game in the middle of writing

The last line can be cut in half. The reader counts it as broken and carries on with the rest, so a closed tab costs you one event, not the file.

how do i know my tracking is right

Write down what should happen as a list of allowed moves, play one round, and compare. An event that fires twice or never turns up shows at once, before you trust any number.