I need to full re-render a world on my server.
I noticed it doesn't works properly, so to understand, I purged the maps for this world, and retry fullrender.
And so DynMap generated only the chunks visited since server has been updated to 1.13.1 : it do not detects other chunks, so it stops and says "render complete", but 99% of map is black and no rendered !
I have this problem on my server as well. Using a world migrated from 1.12.2 to 1.13.1.
Same here i do a --forceUpgrade for a pre generated World with 602501 Generated Chunks but only a little bit of the chunks will be rendered.
Having the same problem as well
Same here. I think this is the problem: https://github.com/Brettflan/WorldBorder/issues/113
EDIT : NEW VERSION. Do not use anymore the old 0.0.1-SNAPSHOT version !
So, as this is issue is not resolved, I made a very little plugin witch refresh all chunks in all worlds.
And... IT'S WORKS ! Waiting for this issue to be resolved, it's a a temporary solution.
It's provided as is and comes with no warranty, save your server first.
Make sure your read the joigned readme.txt file !!!
Just a command to use, from console.
So, as this is issue is not resolved, I made a very little plugin witch refresh all chunks in all worlds.
And... IT'S WORKS ! Waiting for this issue to be resolved, it's a a temporary solution.
It's provided as is and comes with no warranty, save your server first.
Make sure your read the joigned readme.txt file !!!
Just a command to use, from console.NB : there can exist issues on some case in large worlds... Beware...
What kind of issues? Also thanks for making this
ChunksRefresher_0_0_1-SNAPSHOT-2018-11-02.zip
Thanks a lot ! It Works Fine for me !
My 2.5GB Wolrd Chunk Data needed 32GB RAM to run the plugin.
On 16GB RAM machine, I got An Error of "GC overhead limit exceeded".
For safety, I only use the generated map data, and the chunk data remains as it was before the refresh.
and a solution for server with less memory?
and a solution for server with less memory?
I just uploaded new version, 0.0.2-SNAPSHOT, you can use it on any server, issues are fixed. When the server goes near out of memory, tasks stops. You can start them again, after cleaning memory or restarting server. It will skip regions already refreshed ;)
that sounds good :)
Spigot bug - added workaround in latest dev build ( http://dynmap.us/builds/dynmap/ ) on 1.13.2 (workaround not available on 1.13.1). Issue opened for Spigot - https://hub.spigotmc.org/jira/browse/SPIGOT-4512
Dup of #2313
Most helpful comment
Spigot bug - added workaround in latest dev build ( http://dynmap.us/builds/dynmap/ ) on 1.13.2 (workaround not available on 1.13.1). Issue opened for Spigot - https://hub.spigotmc.org/jira/browse/SPIGOT-4512