Death map
Your AI lays a grid over a level, counts where players died and draws the result as a simple map, sometimes called a heatmap. It tells a real trap from one stubborn player who died there thirty times or a busy spot everyone passes anyway, and each hot spot comes with the numbers behind it.
When you need it
When players die a lot in a level and you want to know where and whether it is fair. Use it to find the spot, then play that spot yourself to find out why.
Say this to your AI
Use the death map from Spielerando on my event log for one level. First describe the route through the level as a Mermaid state diagram, with where a player is meant to be in danger and where they are meant to be safe. Then show me the map and each hot spot with its deaths, different players and passes, and compare them with that route. If too few players died, say so. Tell me what to look at, not why, unless you can show it.Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP
Settings
- cellSize (5): The width and height of one grid cell, in your game's units.
- minPlayers (5): A hot spot needs at least this many different players.
- hotShare (0.1): And at least this share of all players who died in the level.
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
where do players die in my level
Write down a position with every death and count them on a grid. Rank the cells by how many different players died there, not by the raw number of deaths.
one player died 30 times in the same place does that matter
Not much. The report counts different players, so one stubborn person shows up as one player. Thirty deaths by one person is not a trap.
what is a heatmap in a game
A picture of a level with the busy spots marked, here the places where people died. It shows you where to look, not why it happens.