WATCH IT
BE BUILT.

Planar reflections work by rendering the scene from a mirrored camera below the water plane, then projecting that render onto the water surface. The result is a water surface that reflects the actual scene — sky, terrain, objects — in real time.

This was the last major visual feature needed to call LIQUIDITY's core rendering complete. Shore interaction and buoyancy are next.

The key architectural decision: runtime EntityIDs are temporary and never written back to SIR. When you exit Play Mode, the authored world is restored exactly as you left it — no runtime mutations leak back.

This is the foundation for Edit on the Fly — the future feature that will let you modify the runtime world and choose to apply or discard those changes.

SIR is the canonical authored project truth. It is never mutated at runtime. PersistentID gives every authored entity a durable identity — a UUID that survives serialization, undo, redo, and reimport.

Human UI and future AI agents use the same semantic command layer. There is no privileged path. There is no screen-scraping. There is only the command.

This sounds simple. It is not. Getting the command system, SIR serialization, and editor state all working together took longer than expected. But it works.

The editor is built around semantic commands from day one. Every user action — add entity, set property, delete — goes through the command layer. This is what will eventually let AI agents operate the editor.

LIQUIDITY started as a question: what would it take to build a convincing planetary ocean without a third-party water plugin? The answer is: a lot. But it's working.

The ocean uses a wave-normal distortion approach with Fresnel/GGX response. Planetary curvature is handled by offsetting the water mesh based on distance from the planet center.