Sodium ArrayIndexOutOfBoundsException in Chunk Rendering (WorldSlice / ChunkStatusTracker)

What the log looks like

java\.lang\.ArrayIndexOutOfBoundsException[^\n]*\r?\n(?:\s+at [^\n]+\r?\n){0,2}\s+at me\.jellysquid\.mods\.sodium\.client\.(?:world|render\.chunk)\.
java\.lang\.ArrayIndexOutOfBoundsException:[^\n]*\r?\n\s+at me\.jellysquid\.mods\.sodium\.client\.world\.WorldSlice\.getBlockState\(
java\.lang\.ArrayIndexOutOfBoundsException[^\n]*\r?\n(?:\s+at [^\n]+\r?\n){0,2}\s+at me\.jellysquid\.mods\.sodium\.client\.render\.chunk\.ChunkStatusTracker\.areChunksAvailable\(

How to fix it

1. Update Sodium to the latest release built for your exact Minecraft version (for example, update from Sodium 0.1.0 to 0.2.0 or newer on Minecraft 1.16.4/1.16.5), where the WorldSlice and ChunkStatusTracker bounds bugs were patched.
2. Ensure your Sodium JAR matches your exact Minecraft version rather than an older minor patch (such as running a 1.16.3 Sodium build on 1.16.4).
3. Change your Render Distance from the title screen Video Settings menu before loading a world instead of adjusting it while in-game.
4. If you are stuck on an older modpack version and crash immediately upon joining a world in SmoothLightPipeline, temporarily turn Smooth Lighting off in Video Settings before entering the world.
5. Remove Not Enough Crashes if installed, because continuing gameplay after a chunk render crash leaves Sodium's chunk tracker arrays in a broken state.

Check your own log