You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues before opening this bug report.
Current Behavior
The README table (https://github.com/Cubxity/UnifiedMetrics?tab=readme-ov-file#metrics) shows outdated metrics. For example, it shows the metric world, but this metric does not exist. In contract, the exporter exports the metric minecraft_world_entities_count, but this isn't shown in the table
Also, would it be possible to document them more ? For example, I'd like to know what minecraft_world_loaded_chunks exports precisely, as there are multiple stages of loading for chunks (https://minecraft.fandom.com/wiki/Chunk#Level_and_load_type)
Expected Behavior
The README metrics table should be up to date
The README metrics table should document metrics
Server type
Fabric
Server Version
1.20.1
Other Mods / Plugins in your server
Syntra connector (I am using Forge)
Error log
No response
More information
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this bug?
Current Behavior
The README table (https://github.com/Cubxity/UnifiedMetrics?tab=readme-ov-file#metrics) shows outdated metrics. For example, it shows the metric
world
, but this metric does not exist. In contract, the exporter exports the metricminecraft_world_entities_count
, but this isn't shown in the tableAlso, would it be possible to document them more ? For example, I'd like to know what
minecraft_world_loaded_chunks
exports precisely, as there are multiple stages of loading for chunks (https://minecraft.fandom.com/wiki/Chunk#Level_and_load_type)Expected Behavior
The README metrics table should be up to date
The README metrics table should document metrics
Server type
Fabric
Server Version
1.20.1
Other Mods / Plugins in your server
Syntra connector (I am using Forge)
Error log
No response
More information
No response
The text was updated successfully, but these errors were encountered: