#WARN: [dynmap] Unknown chunk status: minecraft:full

1 messages · Page 1 of 1 (latest)

tidal robin
#

[15:44:06 INFO]: [dynmap] Loading default resource pack
[15:44:27 WARN]: [dynmap] Unknown chunk status: minecraft:full

I get these warnings now and then since a long time. Things seem to work fine though.
Is it anything I should worry about?

Dynmap version: core=3.7-beta-4-935, plugin=3.7-beta-4-935
This server is running Paper version git-Paper-462 (MC: 1.20.4) (Implementing API version 1.20.4-R0.1-SNAPSHOT) (Git: 00fd87a)

blissful merlin
tidal robin
#

some hundred GBs on this drive

#

Which is hosting both the Paper server with map data and dynmap (with all web tiles) and other plugins. It has never been close to full.

#

World folders are ~2GB total, and dynmap with web tiles uses ~25GB.

tidal robin
#

On this page ( https://minecraft.wiki/w/Chunk_format ) I find this about chunk status minecraft:full:

Status: Defines the world generation status of this chunk. It is always one of the following: minecraft:empty, minecraft:structure_starts, minecraft:structure_references, minecraft:biomes, minecraft:noise, minecraft:surface, minecraft:carvers, minecraft:features, minecraft:light, minecraft:spawn, or minecraft:full. All status except minecraft:full are used for chunks called proto-chunks, in other words, for chunks with incomplete generation.

It seems to me that this should be a rather common chunk status for Dynmap to encounter? Maybe it is just something that changed from "full" to "minecraft:full"? But I am mostly guessing...

blissful merlin
#

Imma leave this one to lostbot

gray plover
#

that's strange, cannot really find a note in the code of this error, just tested this paper-version and dynmap together and I don't get any issue, maybe that chunk is corrupt or something?

tidal robin
#

It still seems a bit strange to give a warning about a chunk status that seems quite normal? But maybe I am not understanding "minecraft:full" correctly.

gray plover
#

yeah indeed, I have never seen the minecraft:full error message, normally it gives an ID which then means a corrupt chunk

tidal robin
#

I'll take a look at old logs and try to see if there are any hints.

gray plover
#

would be great, thanks!

tidal robin
#

I see this from the very first time I started up this new server (a pretty vanilla world, without any chunks generated or inherited), Sep 14 2023, on git-Paper-176, MC API 1.20.1-R0.1-SNAPSHOT, dynmap 3.6-899. That is even before any player joined the server. I have never done any chunk pregeneration on this server, it has only been "organic" through player actions.
After that it always shows up soon after "[dynmap] Loading default resource pack", usually just 0-3 seconds after, but sometimes up to around half a minute.
The only other anomaly I see (which might actually be important!) is that on the first start up of the server it threw this error, ~5 minutes after dynmap's warning and ~25 seconds after the first player joined:
[Tuinity Chunk System Worker #0/ERROR]: Detected setBlock in a far chunk [-24, 3], pos: BlockPosition{x=-373, y=75, z=63}, status: minecraft:features, currently generating: ResourceKey[minecraft:worldgen/placed_feature / minecraft:large_dripstone]

gray plover
#

maybe check what happens if you go to that chunk?

tidal robin
#

I'll check the logs of another server I am running with mostly the same setup.

gray plover
#

that is some great tracability of those logs

tidal robin
#

Actually 3 occurences in that server's logs too. But that server has been running for a much longer time (many years), the one I noticed the problem on has 19 occurences in ~6 months.

gray plover
#

is that every time the same block? large_dripstone at that position?

#

then it means that mc is not able to put that structure there somehow

tidal robin
#

no idea, since the warning does not state which chunk it is. That is only mentioned in the one Tuinity error when the server was first started and never again. The other server has had no such error.

#

I'll try going there

gray plover
#

oh I thought you meant the tuinity error, my bad, sorry

#

I sadly cannot find where it states the chunk status error, so I cannot add other diagnostics

tidal robin
#

Maybe if I turn debug logging on (for Paper) it could help?

gray plover
#

could be yeah, I don't know where dynmap fetches this error from, its nowhere in the buildscope

#

huh strange, grep finds it, I shall code a debug addin

tidal robin
#

Nothing strange in-game or logged when I go to the Tuinity/dripstone location, seems all fine. Could try to regenerate the chunk maybe. (I'm actually not sure what is the proper way to regenerate a chunk though.)

gray plover
#

I know worldedit/fawe has a cmd for it

tidal robin
#

Hmm, maybe I will stay off that path to avoid risk of introducing other issues.

gray plover
#

can you maybe send over that world? I have a version ready that adds the xyz to that unown chunk status

tidal robin
#

Zip up the world folder? Yes, I can do that, and put it at an accessible place. Just need to clear the server of players first.

gray plover
#

I don't think you need to, you can do a save-all and copy the files over

tidal robin
#

Did anyway, just to be sure. 🙂

gray plover
#

👍

tidal robin
#

Since there was no chunk pregeneration or inheritance, the problem(?) should be in the area just around spawn.

gray plover
#

let's see if dynmap complains :D

tidal robin
#

~1.5GB

gray plover
#

download went ok, setting up server

#

100000 tiles went OK

tidal robin
#

Note (again) that the warning comes before the first player joins.

gray plover
tidal robin
#

I'll try that

#

Hah, now it did not throw the warning! 😮

gray plover
#

now that is inconvenient

tidal robin
#

I did some joining and moving around to provoke it, and when I then shut down the server, I got this error:
[22:17:30 ERROR]: [dynmap] Exception during render job: world=sep2023, map=null

#

It comes with a dump that starts with:
[22:17:30 WARN]: java.lang.NullPointerException: Cannot invoke "org.dynmap.MapManager.pushUpdate(org.dynmap.DynmapWorld, org.dynmap.Client$Update)" because "org.dynmap.MapManager.mapman" is null

gray plover
#

it is trying to update a tile while the mapmanager already is shut down

tidal robin
#

So after restarting, still no chunk status warning.

gray plover
#

that's very strange, it did every time before? I didn't and cannot have fixed this by just adding more diagnostics

#

maybe zipping it fixed something?

tidal robin
#

Every "[dynmap] Loading default resource pack" before, was followed by "[dynmap] Unknown chunk status: minecraft:full" immediately or soon after, now not so

gray plover
#

yeah you said so indeed,
the selected part is all I added

tidal robin
#

No, I must correct myself, sorry. Some times, the warning comes even before the "loading default" line

#

And now I got it, live, it was jsut delayed it seems!

gray plover
#

ah nice!

#

what did the block position say?

tidal robin
#

[22:26:23 WARN]: [dynmap] Unknown chunk status: minecraft:fullx: -512minecraft:fully: 80minecraft:fullz: 127921615

gray plover
#

ah I formatted it wrong

tidal robin
#

It took almost 5 minutes for that to come up, that is new.

#

that's a high Z

gray plover
#

but it is -512, 80, 127921615

#

yeah

tidal robin
#

plugin list, in case it could be something messing with the data and confusing Dynmap:
BetterSleeping4 (4.0.2), Chunky (1.3.136), ChunkyBorder (1.1.59), CommandTimer (8.5.5), CoreProtect (22.2), DeadChest (4.19.0), DeathCoordinates (1.12.1), DiscordSRV (1.27.0), DragonSlayer (0.12.15_Jeppa), Dynmap-EssentialsX (1.1-SNAPSHOT), Dynmap-GriefPrevention (0.90), Essentials (2.21.0-dev+75-76a513a), EssentialsChat (2.21.0-dev+75-76a513a), EssentialsGeoIP (2.21.0-dev+75-76a513a), EssentialsSpawn (2.21.0-dev+75-76a513a), GSit (1.8.0), Geyser-Spigot (2.2.2-SNAPSHOT), GriefPrevention (16.18.2-5-g614cca3), InventoryRollbackPlus (1.6.14), LuckPerms (5.4.121), OpenInv (4.4.3), PetMaster (1.12.5), PlaceholderAPI (2.11.5), PlayerHeads (5.20.2-SNAPSHOT), PlugManX (2.3.7), ProtocolLib (5.2.0-SNAPSHOT-679), ServerUtils (3.5.4), TAB (4.1.2), TimeIsMoney (1.9.9), TogglePvp (8.1), Vault (1.7.3-b131), ViaVersion (4.9.3), dynmap (3.7-SNAPSHOT-Dev), dynmapHider (1.2), floodgate (2.2.2-SNAPSHOT (b96-7f38765)) and spark (1.10.60)

#

Some of these are not really used on this server, just inherited from a standard setup I use.

gray plover
#

I don't know why dynmap accesses that position, there is nothing there according to mcaselector

tidal robin
#

Yes, it seems strange, no file in /region to match it either

gray plover
#

I see you have plugman, dynmap doesn't support reloading because of the webserver

tidal robin
#

I never reload that way

gray plover
#

the rest seems ok to me

tidal robin
#

(Just use Plugman to check for updates, not really useful for that either, but I was hoping it would improve the detection.)

gray plover
#

ahh yeah, then it is good, strange thing is that I don't see that message on my test setup

tidal robin
#

I went to the coords on the web map too, but of course nothing is there

#

I don't see 127921615 being some "magic" number either? like a max signed/unsigned integer of some bits, but it is not.

gray plover
#

no indeed, and it is nowhere near badlands either

tidal robin
#

Well, at least we know a little bit more now. Further mystery solving for me will have to wait sicne I have to do some real work now. At least it doesn't seem catastrophic!

gray plover
#

no indeed, and you have more diagnostics now :D

tidal robin
#

Thanks for your time!

gray plover
#

still find it strange I don't see it in my setup

#

np, have fun with the plugin

tidal robin
#

It is so good!

gray plover
#

it for sure is!

radiant fulcrumBOT
#

This support thread has been archived due to inactivity. Click the button below to reopen it.

radiant fulcrumBOT
#

This support thread has been archived due to inactivity. Click the button below to reopen it.

radiant fulcrumBOT
#

This support thread has been archived due to inactivity. Click the button below to reopen it.

radiant fulcrumBOT
#

This support thread has been archived due to inactivity. Click the button below to reopen it.

radiant fulcrumBOT
#

This support thread has been archived due to inactivity. Click the button below to reopen it.

radiant fulcrumBOT
#

This support thread has been archived due to inactivity. Click the button below to reopen it.

radiant fulcrumBOT
#

This support thread has been archived due to inactivity. Click the button below to reopen it.

radiant fulcrumBOT
#

This support thread has been archived due to inactivity. Click the button below to reopen it.

radiant fulcrumBOT
#

This support thread has been archived due to inactivity. Click the button below to reopen it.

radiant fulcrumBOT
#

This support thread has been archived due to inactivity. Click the button below to reopen it.

radiant fulcrumBOT
#

This support thread has been archived due to inactivity. Click the button below to reopen it.

radiant fulcrumBOT
#

This support thread has been archived due to inactivity. Click the button below to reopen it.

radiant fulcrumBOT
#

This support thread has been archived due to inactivity. Click the button below to reopen it.