Yet-Another-World-Protector icon indicating copy to clipboard operation
Yet-Another-World-Protector copied to clipboard

Spam in console

Open danila2021 opened this issue 1 month ago • 12 comments

How to off this? [Server thread/INFO] [YAWP-DataManager/]: Requested save. Saving region data for all levels.

danila2021 avatar Nov 04 '25 16:11 danila2021

Hi there.

You don't. Its a built in information log with currently no way (configuration) to turn it off.

Is it really that bad knowing when the data was saved?

I already thought about moving this to the debug log so it does not show in the normal server log.

Until then you and everyone else is stuck with those messages.

Best regards

Z0rdak avatar Nov 04 '25 16:11 Z0rdak

Image

danila2021 avatar Nov 04 '25 18:11 danila2021

Oh wth. This is not normal. Are there any timestamps included in the logs?

Please provide more information about your used versions.

Z0rdak avatar Nov 04 '25 18:11 Z0rdak

FORGE 1.20.1-0.6.2-beta1 and i can't change settings in configs. After server restart, returns to its original form.

[19:48:26] [Server thread/INFO] [YAWP-DataManager/]: Requested save. Saving region data for all levels [19:48:26] [Server thread/INFO] [YAWP-DataManager/]: Requested save. Saving region data for all levels [19:48:26] [Server thread/INFO] [YAWP-DataManager/]: Requested save. Saving region data for all levels [19:48:26] [Server thread/INFO] [YAWP-DataManager/]: Requested save. Saving region data for all levels [19:48:26] [Server thread/INFO] [YAWP-DataManager/]: Requested save. Saving region data for all levels [19:48:26] [Server thread/INFO] [YAWP-DataManager/]: Requested save. Saving region data for all levels [19:48:26] [Server thread/INFO] [YAWP-DataManager/]: Requested save. Saving region data for all levels [19:48:26] [Server thread/INFO] [YAWP-DataManager/]: Requested save. Saving region data for all levels [19:48:26] [Server thread/INFO] [YAWP-DataManager/]: Requested save. Saving region data for all levels [19:48:26] [Server thread/INFO] [YAWP-DataManager/]: Requested save. Saving region data for all levels [19:48:26] [Server thread/INFO] [YAWP-DataManager/]: Requested save. Saving region data for all levels [19:48:26] [Server thread/INFO] [YAWP-DataManager/]: Requested save. Saving region data for all levels [19:48:26] [Server thread/INFO] [YAWP-DataManager/]: Requested save. Saving region data for all levels [19:48:26] [Server thread/INFO] [YAWP-DataManager/]: Requested save. Saving region data for all levels [19:48:26] [Server thread/INFO] [YAWP-DataManager/]: Requested save. Saving region data for all levels...........

danila2021 avatar Nov 04 '25 19:11 danila2021

I just remember there was someone having similar or the same issue... They had a host which was somehow stuck in a loop and very aggressively trying to save data..

Are you using a hosting service?

If there is any debug.log it would be great to have and also a full server.log from the start until this issue happens.

I also invite you to join the discord for a more "easy" way of working on your issue.

Z0rdak avatar Nov 04 '25 21:11 Z0rdak

Thanks. I’ll try to take a look at it later. What about my question about the hosting service though?

Z0rdak avatar Nov 05 '25 18:11 Z0rdak

Yes, i use vds

danila2021 avatar Nov 05 '25 19:11 danila2021

I've looked at the debug.log.

Its not only YAWP being triggered to save data constantly, but it just shows in the INFO log. Other mods e.g. OpenPartiesAndClaims also prints the saving of data but only in the DEBUG log.

TL;DR: There is something wrong with your server being stuck in a save loop for some reason. This is not necessarily something caused by YAWP (but might be in combination with other mods). Just YAWP alone does not trigger this behavior.

My suggestion: Remove one mod at a time and see when it stops. Start with the ones which you expect will save something in the world data, like OpenPartiesAndClaims or FTB (maybe?), and go from there.

You could

  • delete the debug.log
  • remove YAWP first
  • start the server
  • look if the debug.log

Check whether it contains the same behavior just without the info from YAWP

Z0rdak avatar Nov 05 '25 20:11 Z0rdak

I tried installing the mod on version 1.21.1 of neoforge and got the same thing. I decided to switch back to an older version. Where there is no such bug.

danila2021 avatar Nov 08 '25 08:11 danila2021

Well okay. Good to hear that there is an older version not causing this bug.

Would you please so kind and share which version you are now using? I'd really like to find this bug and remove it from the newest versions.

Thanks

Z0rdak avatar Nov 08 '25 08:11 Z0rdak

yawp-1.20.1-forge-0.6.0-beta1 yawp-1.21.1-neoforge-0.6.0-beta1

danila2021 avatar Nov 08 '25 09:11 danila2021