Project Rabbit, a newly announced extraction soulslike developed by a focused independent studio, leverages the surrealist aesthetic of Alice in Wonderland to deliver a high-stakes, systemic combat experience. By blending punishing melee mechanics with persistent-world extraction loops, the title aims to challenge established genre norms through non-linear environmental storytelling and procedural asset generation.
As of May 25, 2026, the gaming industry finds itself in a peculiar cycle: the “soulslike” subgenre has moved past mere imitation of FromSoftware’s design language and into a phase of thematic subversion. We saw this with Lies of P, which weaponized Pinocchio’s narrative architecture to refine the parry-heavy combat loop. Project Rabbit is not just another iteration. It’s a technical experiment in how procedural extraction mechanics—typically reserved for shooters like Escape from Tarkov—can coexist with the rigid, frame-perfect timing required by high-fidelity action RPGs.
The Technical Architecture of Procedural Despair
At its core, Project Rabbit is betting on a hybrid engine approach. While the developers have remained tight-lipped regarding their specific middleware, industry signals point toward a heavily modified version of Unreal Engine 5.4. The integration of Lumen for real-time global illumination is not just an aesthetic choice; it is a gameplay mechanic. In a soulslike, lighting is the primary information vector for telegraphing enemy attack animations. By utilizing dynamic light-bouncing, the game forces players to manage their own visibility within the shifting geometry of “Wonderland,” creating a tangible risk-reward loop during extraction.
The “extraction” element introduces a significant technical hurdle: server-side state synchronization. Unlike a traditional single-player RPG where the game state is local, an extraction game requires persistent, low-latency tracking of player inventory and environmental triggers. This necessitates robust client-server reconciliation to prevent “rubber-banding” during high-intensity boss encounters where frame-perfect dodges are mandatory.
“The industry is obsessed with the ‘Soulslike’ label, but the real innovation here isn’t the difficulty—it’s the inventory management overhead in a hostile, non-linear space. Integrating extraction mechanics means the game must treat ‘loss’ as a systemic failure rather than a narrative reset. That requires a depth of server-side data integrity that most indie studios struggle to maintain.” — Dr. Aris Thorne, Lead Systems Architect at Nexus Simulations
Ecosystem Bridging: The Shift from Static to Dynamic RPGs
Project Rabbit exists in a broader market context where players are increasingly fatigued by “open-world bloat.” The shift toward smaller, high-density, procedural maps signifies a pivot in how developers are utilizing Vulkan and DX12 API capabilities. By constraining the play area, the studio can push higher polygon counts and more sophisticated physics simulations, ensuring that every piece of the environment is a potential hazard or asset.
This approach mirrors the “less is more” philosophy currently gaining traction in Silicon Valley’s software development circles—prioritizing efficient compute cycles over brute-force rendering. If the developers can successfully implement a robust anti-cheat framework that doesn’t rely on invasive kernel-level drivers, they might just set a new standard for indie-level competitive integrity.
The 30-Second Verdict: What to Watch
- Systemic Risk: The extraction mechanic will likely be the point of failure. If the netcode doesn’t support sub-50ms latency, the soulslike combat will feel unresponsive.
- Asset Reuse: The use of surrealism allows for procedural generation that doesn’t feel “cheap.” Expect the game to lean heavily on non-Euclidean geometry to hide procedural seams.
- The “Alice” Hook: It isn’t just window dressing. The narrative is expected to be integrated into the items themselves, following the environmental storytelling blueprint established by the genre’s pioneers.
Infrastructure and the “Extraction” Bottleneck
The biggest risk for Project Rabbit isn’t the art direction; it’s the backend. Traditional soulslikes are functionally single-player experiences with asynchronous multiplayer (bloodstains, messages). By moving to an extraction model, the studio is effectively building a live-service platform. This requires a transition from local saves to cloud-synced database management, which introduces the risk of data loss or manipulation by bad actors.
| Feature | Traditional Soulslike | Project Rabbit (Extraction Soulslike) |
|---|---|---|
| State Management | Client-Side / Local | Server-Side / Persistent |
| Death Penalty | Currency Loss | Full Inventory Wipe |
| Environment | Static / Hand-Crafted | Procedural / Semi-Dynamic |
| Latency Sensitivity | Low (Single Player) | High (Competitive Extraction) |
As we monitor the beta rollout scheduled for the coming weeks, the focus should remain on the stability of their matchmaking infrastructure. Any deviation from a smooth, ISO-compliant data security protocol for player inventories will likely result in a “dead on arrival” scenario for the competitive community. The developers have promised a “ruthless” experience, but in the realm of tech-heavy gaming, the most ruthless opponent is often a poorly optimized network stack.
Project Rabbit is clearly attempting to bridge the gap between the methodical pacing of the soulslike genre and the high-adrenaline stakes of extraction-based looting. If they can balance the technical load of persistent servers with the precise combat requirements of an action RPG, they may well redefine the genre for the 2026-2027 fiscal cycle. However, until we see the real-time telemetry from the beta, keep your expectations tempered. In this industry, the distance between a compelling trailer and a functional build is measured in millions of lines of code—and that is where most projects lose their way.
