Peroxide Script Online

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.

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.

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

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

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 .

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

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