Sinn Studio is an XR developer and the creator of Swordsman VR, a console VR best-seller, along with titles like Battlegrounds (VR) and Guardian of Realms (MR). In 2025, the studio shifted its focus toward free-to-play VR, a move that demanded “significantly shorter development cycles, quicker prototyping and feature iteration, and rapid content cadence post-launch.”
In August, Sinn began development on ZOMBONK, a free-to-play VR game with Gorilla movement set in a post-apocalyptic zombie world. To support that pace, Sinn partnered with Aura at the start of ZOMBONK’s development cycle. Five months later, the team was preparing for a full early access launch.
This article summarizes Sinn’s case study and extracts operational practices that Unreal Engine teams can apply when evaluating an Unreal AI Agent or Unreal AI Assistant for production.
Aura was adopted to increase throughput and reduce rework in a small team operating on shorter cycles.
Sinn explicitly notes that this was done “without any changes to our team,” and that artists were “empowered to focus on hero assets and premium cosmetics.” In practice, Aura was used to protect specialist time and expand what the team could ship in a fixed schedule, rather than reducing the team.
For teams evaluating tools like this, it’s worth being explicit internally: the target is schedule risk and production bottlenecks, not replacing craft. The case study points to a division of labor where artists stay on the highest value work and use the tool to accelerate the lower-leverage tasks that usually consume time late in production - it is also Aura’s operating philosophy at - to empower smaller studios to achieve impossible things.
Art production and sourcing at scale
For short-cycle projects, getting from concept to release requires producing or sourcing significant volumes of art. Sinn had relied heavily on marketplace assets, but noted that doing this well is time-intensive. Asset packs need to converge on a consistent style, then be processed and optimized.
Knowledge transfer in a small team with frequent context switching
As cycles shortened, specialization became less practical. Developers needed to cover a wider range of features, and time spent re-familiarizing with code and systems became a recurring cost.
Aura was introduced as an Unreal AI Agent and Unreal AI Assistant to reduce time spent in both areas: content throughput and developer ramp time.
“Aura and I rapidly iterated to meticulously craft a vision for the game. We make VR games, so coming up with an idea and then seeing it come to life in 3D just a few minutes later was game-changing for me.”
They also described a division of labor that preserved specialist time without adding headcount. Artists focused on “hero assets and premium cosmetics,” while developers and designers used Aura to prototype environments, props, and feature assets, many of which were incorporated into the final game. This allowed the team to shape the game’s style and feel during development rather than late in the pipeline.
On many teams, artists get pulled into work that is necessary but not the best use of their expertise: assembling placeholder sets, searching marketplaces, adapting inconsistent packs, and doing early iterations that will be replaced anyway. Sinn’s workflow used Aura to compress those iterations and reduce the number of “throwaway” passes, so artists could spend more time on the work players notice and pay for: signature assets, premium cosmetics, and quality bar.
This is a meaningful distinction for production leaders. When the goal is to ship faster, the temptation is to ask specialists to do more. Sinn’s case study suggests the opposite approach: reduce the volume of low-leverage art tasks, so the same artists can deliver higher-impact content on schedule.
They also emphasized the value of codebase indexing for teams that frequently context switch:
“Aura indexed our project in real-time and was the most knowledgeable programmer on our team when it came to the bulk of the codebase (what’s where).”
In one example, they described spending 30 minutes attempting to locate how to change a pricing model for an in-game shop, then asking Aura and receiving the answer “in just a few seconds,” with the location matching where Aura indicated.
Aura helps teams ship on time and scale their Live Ops
All of this helps reduces the cost of returning to a system after days or weeks and helps developers unblock themselves without pulling another teammate off their work.
Over a live-service roadmap, that effect compounds. Fewer interruptions, less ramp time per feature, and fewer bottlenecks, more time to GSD.
Sinn summarized the primary outcome as a reduction in overall project timelines:
“Projects that would typically take us 8-12 months to develop, we were able to do in 4-5 months using Aura.”
They also reported improvements across three measurable production areas:
A structured rollout reduces risk and makes the impact visible. Teams typically see the clearest measurement in:
Sinn’s approach provides a repeatable model: keep artists focused on hero assets and premium cosmetics, while using AI-assisted workflows to accelerate prototypes and supporting assets that unblock level and feature development.
If your team context switches frequently, the ability to quickly locate systems and understand how they connect can reduce ramp time materially. Sinn reported knowledge transfer improving from ~4 hours to 20–30 minutes on new features, which is the kind of gain that compounds across a live-service roadmap.
Sinn’s ZOMBONK case study describes a practical production pattern: use an Unreal AI Agent and Unreal AI Assistant to accelerate asset throughput, support structured system scaling, and reduce time lost to context switching. Sinn reported compressing typical project timelines from 8–12 months to 4–5 months, supported by quantifiable gains in environment sourcing, prop creation, and developer knowledge transfer.
