Getting this error from paper-182.java server on shutdown

[11:28:14 ERROR]: Nag author: 'pop4959' of 'Chunky' about the following: This plugin is not properly shutting down its async tasks when it is being shut down. This task may throw errors during the final shutdown logs and might not complete before process dies.

You received that error because you did not pause the tasks before shutting down the server, and Chunky was attempting to save them. This process is very quick normally but in your case it took longer than usual and printed that error. This can also occur more frequently on low end systems. It is not a bug.

TLDR; you should probably pause your tasks properly and not rely on shutdown to save them.

I could not pause the task because chunky was causing the server to crash.

I see your comment on the other issue, and most likely the problem is because you are running on a Pi (which is at the extreme end of low end systems, and typically not used for running Minecraft servers).

My advice for now, since there is not an option to slow down generation yet in Chunky, is to use the WorldBorder plugin to pre generate your world. It has an option for setting the fill frequency. In your case, setting this to 5 or 10 might be necessary (the default is 20).

I hope that helps!

Yeah, I had to stop using WorldBorder on 1.16.2 because it was causing chunks to be skipped. Chunky does a much better job here, we just need fill frequency of some sort :)

Fair enough. It may take some time still for me to get around to implementing a limiter, but it is fairly high on to to-do list at this point. Originally there weren't any plans for this, which is why it doesn't exist yet. The idea was that the automatic rate of generation would always match that which the server is able to support, however it seems that is not always the case. If you don't mind, please add me on Discord and I'll let you know when I have something for you to test.

Fixed the original issue in 1576da7.

You should no longer get the nag warning, and task saving is now done sync on shutdown, which means that it should never be the case that tasks fail to save by the time the server stops, even on low-end systems.