I keep seeing my server console saving about every other min even though no one is currently using the doors or on the server.
Forge 952 1.6
no server impact at this moment.
I keep seeing my server console saving about every other min even though no one is currently using the doors or on the server.
Forge 952 1.6
no server impact at this moment.
This is straightforward to fix. The reason that the messages appears every so often is because we save the rift-related data for each dimension every time the world saves. This happens every 30 seconds, I think. We output a message saying that saving is taking place, but assuming our dirty flags are working right, no actual saving is taking place. We should only save data for dimensions that have had their data change recently. The solution to the log spam would be not to output messages unless we actually do save something, or perhaps we shouldn't do it at all.
This is straightforward to fix. The reason that the messages appears every so often is because we save the rift-related data for each dimension every time the world saves. This happens every 30 seconds, I think. We output a message saying that saving is taking place, but assuming our dirty flags are working right, no actual saving is taking place. We should only save data for dimensions that have had their data change recently. The solution to the log spam would be not to output messages unless we actually do save something, or perhaps we shouldn't do it at all.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I keep seeing my server console saving about every other min even though no one is currently using the doors or on the server.
Forge 952 1.6
no server impact at this moment.
This is straightforward to fix. The reason that the messages appears every so often is because we save the rift-related data for each dimension every time the world saves. This happens every 30 seconds, I think. We output a message saying that saving is taking place, but assuming our dirty flags are working right, no actual saving is taking place. We should only save data for dimensions that have had their data change recently. The solution to the log spam would be not to output messages unless we actually do save something, or perhaps we shouldn't do it at all.
SenseiKiwi Fixed