Loading game…
Plotted values · UTC. Longer ranges may use aggregated observations; gaps are not zeroes.
| Time | Players |
|---|---|
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 1 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 1 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 0 | |
| 0 |
Stop the wave and read your variables A breakpoint could already stop the wave on a line. What it couldn't do was tell you anything. You got a highlighted line and a hover tooltip, and if you wanted to know which enemy your loop had actually picked, you were reading your own code