let enemy_health = 100 let preview = !> enemy_health - 20 // Creates a bleached copy print(enemy_health) // 100 (unchanged) print(preview) // 80

Zero GC spikes. This is a game-changer for fighting games, rhythm games, or any title requiring sub-millisecond frame consistency. 3. Native Entity Component System (ECS) Integration Peroxide isn’t general-purpose—it’s built for ECS. The language has first-class support for Archetypes and Queries .

// To commit the bleach back: enemy_health <-! preview // Stabilizes the change

For two decades, modding has been a war between accessibility and power. Lua is friendly but slow. C++ is fast but unforgiving. Peroxide Script, a new open-source embedded scripting language, claims to offer the best of both worlds—with a chemical twist.

This allows modders to simulate "what-if" scenarios (damage prediction, UI previews, network rollback) without cluttering the live game state. It’s like Git for game variables. Most scripting languages pause the world to clean up memory. Peroxide uses reactive reference counting with a twist: objects self-destruct when their last stable reference disappears. The Bleach Operator creates ephemeral references that vanish automatically after the current frame.

channel "UI_Events" -> (event_type: string, payload: any) spawn fn update_health_bar() { loop { match recv("UI_Events", timeout=0) { ("damage_taken", val) => animate_red_flash(val) _ => skip } } }

No locks. No deadlocks. Just data flowing one way. Because of the Bleach Operator, every script runs in a sandboxed revision . You can change a function, recompile the script, and the running game will automatically migrate live variables to the new version—as long as they’re stable.