Peroxide Script -

But as one modder put it on the forums: “Once you bleach, you never go back.” Author’s note: Peroxide Script is currently at version 0.9.2 (codename “Hydrogen Peroxide”). The 1.0 release is planned for Q4 2026.

archetype Player { health: f32, position: Vec3, inventory: List<Item> } system "damage_over_time" { query (mut health, @tag "burning") for each { health.current -= 5.0 * delta_time } }

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. Peroxide Script

But what makes it "peroxide"? The name hints at its core mechanism: . Let’s break it down. 1. The Bleach Operator: !> The headline feature of Peroxide is the Bleach Operator ( !> ). In traditional scripting, if you modify an object, all references see that change. In Peroxide, mutation is opt-in and temporary .

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 . But as one modder put it on the

Is it the future of modding? Possibly for multiplayer, competitive, or simulation-heavy games. For a simple UI script? Probably overkill.

Developed by independent game studio (and later open-sourced in early 2025), Peroxide Script ( .ps or .h2o2 ) was designed to solve a specific pain point: safe, concurrent mutation of game state without garbage collection stutter. It’s like Git for game variables

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 } } }