This article is a stub.
You can help by expanding it.
Screenshot Showing the Debug-Information
The debug screen is a screen that is triggered when the F3 key is pressed. It shows the chunk cache, the memory usage, various parameters, the player's map coordinates and a graph that measures latency. It can be very useful for telling other players your map location, checking for lag and various other purposes.
Legend:
| Name | Description[1][2] |
|---|---|
| C | Number of chunks rendered over total number of chunks |
| F | Number of chunks loaded outside the viewing distance |
| O | Number of chunks removed through occlusion culling |
| E (first row) | Number of chunks ? |
| E (second row) | Number of rendered entities over total entities |
| B | Number of entities removed due to hidden chunks |
| I | Number of individually removed entities |
| P | Particles on screen |
| T | Terrain data |
| ChunkCache | The maximum number of chunks it'll load |
| f | View direction (1 being north) |
Below these parameters, the player's map coordinates are displayed. The X and Z axis are both horizontal, and the Y axis is vertical.
At the bottom of the screen, a graph is displayed which measures latency.
When you activate the debug screen, it also shows numbers above every mob in the chunk. This is useful for finding mobs to kill. It is often used to find dungeons.
Bugs
- As of Beta 1.5, the FPS shows the same number as chunk updates.
- If you go to menu with the f3 menu open it stays open and if you then go to the main menu it stays open and the red bar becomes green.
- Opening a chest with the debug screen on turns the debugging area grey. The text does not turn grey, however. This will not crash the game.