Replies: 1 comment
-
|
Partially-relevant patches we run for something to this effect on our fork: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Is your feature request related to a problem?
Currently, the API does not have any way of getting information about the reason a chunk was loaded, by what (load ticket type), and at what level it was loaded (entity ticking, redstone ticking) (ticket level). This would be really useful information for debugging and administration purposes. Especially to quickly find what is causing lag, where, and who made it, that would be really useful. Currently, this is only possible with workarounds like checking around players, etc.
Describe the solution you'd like.
Expose the ticket system in the API with capabilities to retrieve both the ticket level and type.
Describe alternatives you've considered.
The alternative is to check all chunks around the player and then determine it through an after-the-fact calculation. However, this becomes quite complicated when there are multiple people and Load resons. Same for determining the load level by checking chunks on the edge of loaded areas. It is also not possible to distinguish, for example, chunk loaders from players except by checking the size of the continuously loaded area.
Other
No response
Beta Was this translation helpful? Give feedback.
All reactions