Skip to content
Alpha version. These pages describe a game that is not built yet. Everything here can still change, and in the alpha every city can be reset at any time.

When something goes wrong ​

Your program lost money, or a car stands still, or nothing happens at all. This page shows how to find out why.

The game keeps two histories for this.

HistoryThe question it answers
History of changesWhat happened in the city?
History of decisionsWhat was decided for my company, by whom, why, and what came of it?

The history of changes ​

The Changes panel lists what happened, in order: a car arrived, an order ran out of time, an auction closed, a business got a new controller. You can filter it by kind, by car and by business.

It is tied to the time bar. Drag the time bar, and the map and all panels show the city at that moment.

The history of decisions ​

The Decisions panel shows every decision that was made for your company. One entry is one decision:

Schema — One entry of the history of decisions
Whenday 14, tick 3 380
Who decidedyour code, version 31
What it reacted toidle for car 2, because it had delivered
What it decidedcar 2: drive to Storage North
The reason"order 881 pays 31"
The answeraccepted
What came of itarrived at tick 3 391 → loaded 20 kg → delivered at tick 3 402 → received 31
Where in the codemain.py, line 48

Things worth knowing about this panel:

  • Decisions that belong together are shown together. The drive, the loading and the delivery of one order form one chain. You can open the chain and see every step.
  • An event that got no answer is shown too. "Your code was told that car 2 is free, and did nothing" is often the most useful line of all.
  • A refused command shows why, with a short code such as too_heavy or order_taken.
  • It says who decided: your uploaded code, the CLI, or an AI assistant through MCP.
  • It is tied to the time bar. Choose a decision, and the map shows the city as your program saw it.
  • It is private. Only you see the decisions of your company. There is one exception: the commands a controller sends for a business, with their reasons, can be read by every shareholder of that business.

The reason is the text your program gave with the command. A program that gives no reasons leaves this column empty, and you will miss it. Give a reason with every command.

Finding out why you lost money ​

  1. The top bar shows your cash going down. Open Company, and see which kind of cost grew. Say it is fines.
  2. Tap that line. The Decisions panel opens, showing only the decisions that led to a fine.
  3. Open one chain. Your program sent car 3 to a shop far away with a quarter of a tank. The reason reads "order pays 40".
  4. Choose the entry. The time bar jumps there, and the map shows where car 3 was and how far the nearest fuel station was.
  5. The entry names the line of code. Fix it and push.

When your code is broken ​

The code mark in the top bar turns red in two cases.

Your newest push was refused. Your code is checked before it is started. If it cannot even be loaded, it is refused. Tap the mark to see the file and the line. Your city keeps running the last good version, and the page says which one that is.

Your code keeps crashing. An error in one of your functions does not stop your program: the error is recorded, and the next event is handled as usual. But if the whole program stops again and again, the game waits longer and longer before it starts it again, and marks your code as broken.

Every error is kept with its file and line, and with the lines your program logged just before it.

My cars do nothing ​

Go through this list from the top.

  1. Is your code running? Look at the code mark in the top bar.
  2. Are there errors? A function that fails every time looks exactly like a car that does nothing.
  3. Is your code asked, and answers nothing? Open Decisions and look for events with no command. Then your program runs and chooses to do nothing.
  4. Are the commands refused? The entry shows the code.
  5. Has the car broken down? Then it is out of action for a while and comes back by itself. See Cars.
  6. Does the car have a driver? A car without a driver cannot move.

My change had no effect ​

  1. Look at the code mark. A refused push leaves the old version running, and from the outside that looks like a change that did nothing.
  2. Did you push to the main branch of the repository? A push to another branch does nothing.
  3. A value that your program kept in an ordinary variable is gone after every restart. Keep what must last in the memory.

Delivery is part of simgit.io. This is an alpha version.