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
{{ message }}
This repository has been archived by the owner on Feb 27, 2024. It is now read-only.
I've also reported this to thutmose. I cant always reproduce the issue. But it happens usually a few minutes after the server has been running and a player is logged in. Not sure if the problem is with you or him. He said its related to how he handles explosions. These messages essentially spam several hundred times until you get disconnected.
Should be fixed with this commit. If you can though, enable a config option in the global.conf like so:
cause-tracker {
# If true, when a mod changes a world that is different
# from an expected world during a WorldTick event, the
# cause tracker will identify both the expected changed
# world and the actual changed world. This does not mean
# that the changes are being dropped, simply it means that
# a mod is possibly unknowingly changing a world other
# than what is expected.
report-different-world-changes=true
// more stuff
The reason for this is that if Thutapi is performing world changes during a world tick event that it isn't supposed to, it will print out a report about it and can further be reported to Thutapi.
I've also reported this to thutmose. I cant always reproduce the issue. But it happens usually a few minutes after the server has been running and a player is logged in. Not sure if the problem is with you or him. He said its related to how he handles explosions. These messages essentially spam several hundred times until you get disconnected.
The text was updated successfully, but these errors were encountered: