How to support 1.18+ chunks in a 1.8 chunk loader.

[Bzdhyp]

Problem Description

When using ViaVersion to join a higher-version server from a lower-version client, chunks below Y=0 and above Y=255 are blocked. How can I modify this to prevent the cutoff and retrieve the full chunk information?

Solution Description

Solution Description:I would like to see an option to disable the hard-coded chunk clipping for sub-zero and post-255 heights. The current implementation blocks these chunks to prevent client crashes, but I propose a remapping toggle that allows us to either:Shift the world height (Offset $Y$ values) to fit the 0-255 range.Send the extra data via custom packets/tags for third-party mod processing.This would enable technical players on 1.8 to finally "see" and interact with the extended terrain of 1.18+ servers.

Alternatives

I have already attempted a manual fix by modifying ViaVersion and the networking/rendering layers in MCP, but I couldn't get it fully functional. I've realized this requires a more systematic architectural change that I'm currently unable to complete on my own.

Additional Info

Client Version: Minecraft 1.8.9 (Forge/Vanilla)
Server Version: Minecraft 1.18.2, 1.19.x, 1.20.x, or 1.21+
Proxy/Plugin Environment: ViaVersion (running on BungeeCord, Velocity, or Spigot)
Specific Target: Legacy clients using the standard 16-section (256 blocks) chunk format.