Alice In Cradle -v0.26c2- -hinayua- May 2026

One late-0.26c2 enemy—a weeping, bird-like thing in the flooded hollows—does not attack unless you approach it from the front. From behind, it shivers. If you wait long enough, it falls asleep. There is no reward for waiting. No unique item. Only the quiet, ungameable knowledge that you didn't have to fight it. Version 0.26c2 is not complete. There are locked doors. Unfinished dialogue trees. A crafting system that hints at more recipes than exist. Normally, this would be a flaw. Here, it feels intentional —or at least, accidentally profound.

Each torn stitch reduces defensive capability. Each exposed area of pixel art becomes a target for enemies whose attack patterns are eerily persistent . The monsters in this Cradle do not fight to kill; they fight to hold . Grapple attacks are lengthy, repetitive, and rhythmically hypnotic. You watch the input prompt flash. You fail. You watch Alice struggle. You try again. Alice in Cradle -v0.26c2- -Hinayua-

In the sprawling landscape of indie action-RPGs, Alice in Cradle occupies a liminal space that feels almost cruel in its beauty. The current build, v0.26c2, subtitled Hinayua , is not a finished statement but a fragment—a splinter of a larger, darker mirror. And yet, even in this fractured state, the game hums with a singular, unsettling thesis: that innocence is not a shield, but a wound waiting to be reopened. One late-0

Then you enter the first combat encounter. The game’s mechanical core is built on a system of rupture . Alice has a stamina gauge, a mana pool, and a "corruption" meter that fills as she takes hits. This is standard fare, but the execution is anything but. When Alice’s clothes tear—a key visual and gameplay mechanic—it isn’t mere fanservice. In the logic of Hinayua , it is a mechanical confession : the game admitting that vulnerability is its primary language. There is no reward for waiting