Issue Description: Dynmap spams the console with errors, "Error while raytracing tile" and "Index out of bounds" errors, with different blocks and in different biomes. The map itself looks fine, and it originally rendered fine.

Possible regression of:
#3388

• Dynmap Version: 3.4 Snapshot
• Server Version: Paper 1.19 build 28
• Pastebin of Configuration.txt: https://pastebin.com/CcmwHB6h
• Server Host (if applicable): Self-hosted
• Pastebin of crashlogs or other relevant logs: During Running: https://pastebin.com/KZzZ8r0E During Startup: https://pastebin.com/qBcwpe93
• Other Relevant Data/Screenshots: I'm not even using iso_S_90_lowres, I should be using iso_S_90_medres. custom-normal-hires.txt: https://pastebin.com/aYcmp0Q2. The world was fully pregenned on 1.19 (not updated to it), and the fullrender completed without error
• Steps to Replicate: Start the server, after the world has been edited

[ ] I have looked at all other issues and this is not a duplicate
[ ] I have been able to replicate this

Larger stacktrace during startup
https://pastebin.com/LZXUTXsv

Looks like some sort of off by one array error on this line

Update: It doesn't infact render fine at the places errors occur

E.g.

radiusrender at these locations produces the error again

Huh, nevermind apparently I am using iso_S_90_lowres

I shouldn't be.

My custom_normal_hires is working, since it successfully disables the caves map

Edit: worlds.txt must be overwriting it. Anyhow, that doesn't change the fact I'm getting an error with lowres.

Fixed by "Avoid ArrayIndexOutOfBounds during renders with bad block model" in version v3.4-beta-5