Peroxide Script ❲VALIDATED — PICK❳

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

let enemy_health = 100 let preview = !> enemy_health - 20 // Creates a bleached copy print(enemy_health) // 100 (unchanged) print(preview) // 80 But what makes it "peroxide"

No more manual component lookups. The compiler optimizes queries into linear memory access patterns automatically. Mods often break when two scripts touch the same data. Peroxide enforces channel-based communication . Instead of shared memory, you send bleached copies through named pipes. In Peroxide, mutation is opt-in and temporary

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.

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