A
Admincraftβ€’6mo ago
π’Ÿπ‘œπ“‚π’Ύπ“ƒπ’Ύπ’Έ

Ignoring heightmap data for chunk xx warning in console

So basically, the server logs will get spammed by the following: 
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 28], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 29], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 29], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 29], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 29], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 1], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 1], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 1], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 1], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 0], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 0], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 0], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 0], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, -1], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 28], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 29], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 29], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 29], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 29], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 1], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 1], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 1], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 1], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 0], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 0], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 0], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, 0], size does not match; expected: 37, got: 52
[21:19:05] [Server thread/WARN]: Ignoring heightmap data for chunk [23, -1], size does not match; expected: 37, got: 52
Fabric 1.21 Does anyone know whats up with this? I might have added a mod that increases build limit before, but even after removal, the warnings are still here
2 Replies
Admincraft Meta
Admincraft Metaβ€’6mo ago
Thanks for asking your question!
Make sure to provide as much helpful information as possible such as logs/what you tried and what your exact issue is
Make sure to mark solved when issue is solved!!!
/close !close !solved !answered
Requested by _.dominic#0
π’Ÿπ‘œπ“‚π’Ύπ“ƒπ’Ύπ’Έ
π’Ÿπ‘œπ“‚π’Ύπ“ƒπ’Ύπ’ΈOPβ€’6mo ago
From the very few matching issues that I can find on Google, it seems like the chunk data is now corrupted? The server isn’t crashing per se, but is there like a way to revert this change entirely so the logs don’t get flooded with this error I do have a world backup made automatically just a few hours prior to this warning, so the files there should be uncorrupted if it must be, i can restore a backup Seems like adding a few jvm flags used when migrating versions to force update and clear cache did fix it (?) No longer seeing the console spam

Did you find this page helpful?