// Select a spell from the pool based on "cast_delay" and "reload_time" modifiers. // The more negative the modifier, the more likely a "god" spell appears. // - Arvi, 2020. "If it breaks the game, it's a feature." The code doesn't just pick spells. It picks combinations . A separate genetic algorithm runs during world generation, attempting to "breed" synergistic spells. The source records "interesting" combinations in a hidden cache. That's why you sometimes find a wand that fires a homing, acid-infused, ten-cast bubble burst—the algorithm found it amusing.
The true madness is CastSpell() in spell_interpreter.cpp . Spells are not hardcoded effects. They are . When you fire a wand, the game compiles the spell list into a small virtual machine that executes inside the simulation. This is why lag happens. A "Divide By 10" spell, followed by a "Spark Bolt with Double Trigger" literally causes the virtual machine to recursively invoke itself. The source has a hard-coded recursion limit of 64. Remove it, and your computer becomes a brick. noita source code
The most sacred relic is the . The source defines a Particle struct—humble, only a few dozen bytes. It holds a type (sand, water, fire, blood, polymorphine), temperature, velocity, and a handful of flags. But there are millions of these structs. // Select a spell from the pool based
And the source code? It is the grimoire that binds this chaos into a playable, just-barely-stable reality. At the heart of the noita.exe lies not a traditional game engine, but a highly modified, multithreaded beast written in C and C++ . The developers have been open about its lineage: it grew from a humble "falling sand" game prototype. The source code reflects this organic, almost fungal growth. "If it breaks the game, it's a feature
// WARNING: Do not touch this loop. The water will hear your thoughts. // Last modified by Arvi, 2019-10-13. "I think it works now. Please don't change it." The water solver uses a modified "shallow water" equation on a pixel grid. Because pixels can only hold one element, the code must handle "pressure" by attempting to swap particles with their neighbors. This is where performance dies—every frame, for every water pixel, the CPU screams. The solution? A and a chaotic update order . Instead of left-to-right, the source uses a pseudo-random permutation of pixel indices to prevent directional bias. It's inefficient, but it's fair —water doesn't flow faster to the right. Act II: The Alchemy of Spells - Wand Generation If the particle engine is the body, the wand-building system is the soul. The source code for wand generation is not deterministic; it is a probabilistic nightmare wrapped in a recursive function.