The battle report
The REPORT tab: what happened in the last battle, and why.
After a battle, REPORT has the details: the result and why, both vehicles' totals, the biggest problems, and every event of the battle with its time. It's the place to start when your vehicle did something odd.
RESULT
The headline says who won (INFERNO WINS, say), followed by how: who destroyed whom and when, or the health each had left when time ran out, with the shots, hits and damage that decided it. The tag shows the battle's seed, and SWAPPED if the starting places were swapped.
- WATCH AGAIN plays the battle from the start.
- EDIT PROGRAM goes to the editor.
- DEBUG (with the subscription) opens the debugger.
- SHARE makes a clip and a link of the battle (see Sharing a battle).
The line under the buttons gives the battle's fingerprint, such as 137561cd114a1d3d. The same seed, vehicles and programs always give the same battle, and so the same fingerprint, on any device. If two people get the same fingerprint, they watched the same battle.
WHAT WENT WRONG
With the subscription, the battle's biggest problems in plain words: Ran out of missiles at 41 s, for 12 s, and never reloaded. It says what happened, never what to write, which is your part. When nothing stands out, it says so.
TOTALS
Both vehicles side by side:
| Row | Means |
|---|---|
| Health left | What each had at the end |
| Missiles launched, Hits | Shots, and how many hit |
| Damage dealt | All the damage done to the other |
| Absorbed by shield | Damage the shield soaked up |
| Scans, Scans with a contact | How often the radar looked, and how often it found the opponent |
| Rejected or cut out | Orders that couldn't be carried out: firing while reloading, scanning without the energy, everything while out of power |
| Program faults | Updates that failed (see Writing the program) |
| Debug messages | Lines the program wrote with debug.log() |
Amber means something to look at. Against a house vehicle, or in a league battle, its own counts are hidden (??).
TIMELINE
Every event of the battle, with the second it happened, a label for its kind, and which vehicle. Tap an event to go to that moment in the arena. The buttons along the top show one kind at a time:
| Filter | Shows |
|---|---|
| ALL | Everything |
| COMBAT | Missile warnings, shots, hits and misses, decoys, cannon, flame and ramming, reloading, charging and repairing, destruction and the result |
| RADAR | Contacts found and lost, and tracking locks |
| DEBUG | Your program's debug.log() messages |
| FAULTS | Updates that failed, with the line and the reason |
| REJECTED | Orders refused, power failures and overheating |
What's that? explains each label.
debug.log("...") in your program to put its own reasons on the timeline, such as going to recharge. Then the DEBUG filter tells the story of what your program was thinking.