Turn a long list of build orders into a short chronicle of the reign

At the end of a long game the player would like to read what their reign did, not three hundred lines of placed and torn-down buildings. Here is how to merge the orders into what really changed, set apart the plans that were dropped, and write short lines that count correctly.

Why this works

A story of what happened is the net result, not the list of actions. Following each building from its first order to its last tells you what really changed, and separating dropped plans from finished ones keeps the summary honest.

When not to use it

Skip it when the order of events is the story, such as a diary or a replay where the player wants to relive each step. A merged summary would hide it. Keep the full log there and show the short chronicle only as a headline.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• A diagram of every state
• 27 lines of example code with 4 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "Turn a long list of build orders into a short chronicle of the reign" (read_entry reign-chronicle-from-build-and-demolish-orders) in my game. Build it step by step, and show me how you checked that it works.

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