PC · Unity · In development
Death-game horror thriller
Gameplay development for an independent client
A first-person horror thriller built around a death-game premise. The greybox and vertical-slice milestone are delivered; production continues.
RYKOSTUDIOUNITY · UNREAL ENGINE · GODOT
A playable build tells you more than a design document. We build greyboxes, first playables and vertical slices, so you can judge the feel, show a publisher or an investor, and decide what to fund next.
The right build depends on the question you need answered and on who has to be convinced.
PC · Console · Mobile · Web
The core loop with placeholder art: movement, the main mechanic, a way to win and a way to fail. Enough to answer one question: is it fun?
One short section of the game at the quality of the finished product: final-look art, interface and polish. This is what publishers and investors usually ask to see.
A stable build for a pitch meeting, a showcase or a store demo, with the rough edges a live audience would hit taken out first.
Small games built quickly with AI tools in the workflow, for when the goal is to try several ideas rather than polish one.
When the prototype earns a green light, the same team carries it on: architecture, save systems, performance, art and release.
A prototype exists to answer a question. We start by agreeing which one.
Is the core loop fun? Does the mechanic read? Will this run on a phone? We agree what the build has to prove before anything is made.
Deliverables, budget and acceptance criteria for each milestone, approved by you before work on it begins.
You play the game as it takes shape and steer it, instead of waiting for a reveal at the end.
Take the build and its source to your own team, or keep going with us into full production.
Editable source files, clear documentation, and third-party licences recorded as part of the handover.
Prototypes and slices we have delivered, and a full game built the same way.
PC · Unity · In development
Gameplay development for an independent client
A first-person horror thriller built around a death-game premise. The greybox and vertical-slice milestone are delivered; production continues.

PC · Unity · Coming to Steam
The full game codebase, for Studio Paper
A cozy fantasy management game, coded end to end by our lead developer: gameplay systems, tools, UI and the performance work behind its look.
View on SteamSmall Unreal Engine games built with AI tools, with the results used to train and improve those tools.
Damage calculation, ability systems, AI behaviours and balancing in a readable combat simulation.
“An absolutely amazing team member. Their communication was consistently clear, proactive, and incredibly helpful throughout our collaboration. I highly recommend them and would gladly work with them again.”
The questions we hear before a prototype starts.
A prototype shows that the idea is fun, with placeholder art. A vertical slice shows that the finished quality can be reached. To decide whether to keep going, build a prototype. To pitch a publisher or an investor, you will usually need a slice.
Yes. A paragraph, a design document or a few reference games is enough. We turn it into a scope you can approve before any production starts.
The one the full game will use, when that is already decided. If it is not, we work in Unity, Unreal Engine and Godot and will recommend one for your game and say why.
Yes, if we plan for it. Prototype code is normally written to be fast, not to last. Tell us at the start that the build has to grow into the product and we put it on a foundation that can.
Yes. Say so in your inquiry and we sort it out before you share anything confidential.
It depends on the question it has to answer and the level of polish. Share your budget, even a rough one, and we will say what fits in it before you commit to anything.
Share the concept, where it stands and who you need to convince. If something is undecided, mark it “To discuss”.