Realistic Waves

Whitecap 2.4.0

Shader packs keep the waves on every version

• Iris shader packs no longer flatten the sea on Fabric 1.20.1, Fabric 1.21.11 and 26.2. On these versions Whitecap paused under an Iris shader pack, so with Complementary, BSL or any other pack the sea lay flat and it looked as if the mod did nothing. Now they do what the 1.21.1 versions and Forge 1.20.1 do: the shader pack draws the water, with its own colour, reflections and light, and Whitecap moves it. The swell, the surf, the foam of the breaking waves and the wash running up the sand go into the pack's own water, and boats, floating items and the ocean's sounds follow the waves under the pack as they do without it. Tested under Complementary Reimagined and BSL with Iris 1.7.6 and Sodium 0.5.13 on Fabric 1.20.1, Iris 1.10.8 and Sodium 0.8.14 on Fabric 1.21.11, and Iris 1.11.4 and Sodium 0.9.2 on Fabric and NeoForge 26.2. Where a pack's water cannot take the waves (a pack whose water program will not build with them, an Iris of another shape), Whitecap still pauses under it, and the chat line says why; /whitecap status has a line on what the shader pack's water is doing. On 1.21.11 and 26.2 Waves under shader packs, Foam under shader packs and Wave shading under shader packs are in the settings, as on 1.21.1; on Fabric 1.20.1 shaderPackWaves and shaderPackFoam in config/whitecap.json switch the waves and the foam (all on).

Fixes

• /whitecap status no longer says "DRAWING NOTHING" under a shader pack on 1.21.1. On NeoForge and Fabric 1.21.1 the status ended in "DRAWING NOTHING because: an Iris/Oculus shader pack is active" while the pack's water was moving with the waves. Only the text was wrong: it now says the shader pack's water is moving and over how many tiles, and a line says what the pack's water is doing with the waves, and why when it lies flat.

Forge 1.20.1 stays at 2.3.0: nothing in this update is new for it.