Brett Flannigan

> The dark areas are definitely not lighting issues: You're right, they are almost certainly Dynmap rendering issues.

Thanks for posting about this, with the info that it is the host ShockByte intentionally covertly causing this problem. I know others with the same problem will find this useful.

Hmm, I had no idea. I just checked briefly and see that the "poi" folder was added in 1.14. According to the MC wiki, those files are for "villager identified...

If the commands returned no errors and indicated success in the server log, then they were successful, regardless of whether Dynmap managed to properly update or not.

Note that regions (and thus region files) cover 32x32 chunk areas, so if a region file is "missing", that would be a full 32x32 chunk region. The isolated random chunks...

Just in case you don't realize it, DynMap doesn't really properly handle the possibility that a chunk gets deleted ("Trimmed" in this case) and will generally continue showing a chunk...

Borders have no Y component, they effectively have infinite height. I'm not sure about them being displayed in DynMap with a height to them in the isometric view, offhand. Pretty...

EDIT: Mistakenly pointed to wrong code earlier. It does appear to specify 64 for some reason: https://github.com/Brettflan/WorldBorder/blob/master/src/main/java/com/wimbli/WorldBorder/DynMapFeatures.java#L184 Not sure why, that could probably be switched to reference World.getMaxHeight() instead. Or...

Attempted fix. https://github.com/Brettflan/WorldBorder/commit/0d45093fa61cc6285d8a1f5144b8fd81179c6ff2 Try it out, please. If you can't build it yourself, I can provide a test build.

So something else is keeping those regions in memory, preventing them from being deleted. If a server restart and another Trim don't take care of it due to something else...