Debug mode is used mainly by developers and modders to analyze the running state of the game. It can be enabled to show detailed information about the game world, and its information varies based on which level is active. The keys to enable debug mode are f5 through f7.
For example, one can:
- See the path the Biters are coming from and where they plan to target,
- See the position / coordinates of the cursor,
- See a grid-overlay for the Tiles and Chunks,
- See the blocks in a railway network,
- See additional non-game related information, such as Updates Per Second and FPS.
Activate the debug mode
You have 4 debug-levels:
- Always - This is the default mode, if no mode is active. Keep very few things active here.
- Basic - The first mode, accessed by pressing F5 . What power users often use.
- Detailed - The second mode, accessed by pressing F6 . The most commonly used for modders and developers.
- Full - The third mode, accessed by pressing F7 . Shows literally everything, tends to be unreadable.
To switch back to "always" you need to press the previous key again. Example: Press F5 to go to "basic", then press F6 to watch "detailed" and then press F6 again to switch back to "always".
Configuring the debug mode
To configure the 4 modes, press F4. This opens up a menu with many options. You can move this menu with the mouse, if it hides some interesting underlying thing. You can switch between 4 folders, which reflects the option for that debug-mode ("always", "basic", "detailed", "full"). The options are the same for each mode. Each mode can be configured to the user's liking, the different modes are only for convenience.
List of debug-options and their function
- Will show the current frames-per-second, or FPS. Should be normally about 60. See Lua/Game#speed.
- Many important internal statistics about the timing. F5 debug info - how to read it? - how to interpret...
- Shows the collision boxes of each entity (red).
- Shows the a blue box over each entity, if you hover over it, it will be selected.
- The calculated paths for the biters in different colors.
- Shows waypoints for biters (in green), nearly the same info as the next.
- Shows the current target of the biters (red).
- Biter groups, which belong together (circles and lines belonging together)
- Should show stuck enemies (?)
- The A*-algorithm at work, calculating new paths.
- The source-positions of a path and about the length (?)
- Which path a train will follow.
- Shows inserter positions
- Shows rail connections.
- Shows the segment borders and enables you to see the borders of the block.
- When a train slows down it shows the calculated point where it should halt
- Displays the network-id of the electric network that a pole is connected to
- Shows the number (and color) of circuit networks
- Which network-id an entity is connected to.
- Shows items, which are blocked (see for example full belts)
- Inserters, fish, turrets are turned to passive, if not used; Red = inactive, Purple = inactive until enemies aren't around (turrets etc), Green = inactive until player isn't around (fish). Passive entities consume less CPU power.
- Not 100% clear: displays in the map view, how much biter nests (blue) are targeting to which are (red for the number of biters?), green: unknown?
- Shows in the map view, which chunks are "on", unmarked chunks are not calculated
- Where is space left to spread the brood?
- Shows, which tile-variation (1, 2 or 4 tile sized) is painted for which area of the map quite confusing, zoom in to see the meaning.
- Turns connected textures for land and water off, so the distinction can easily be made.
- How much fluid is in a pipe/storage tank, shows flow of liquid in pipes.
- Displays which sound of which entity is played and how loud.
- F5 debug info - how to read it? - how to interpret show_time_used_percent