Gameplay
Gameplay
Game systems, controls, AI, saves, progression. From a throwaway prototype to a delivered, documented feature.
- C++ & Blueprints
- Systems
- AI
- Porting
Team & partnership — sold as a team, over time
We reinforce your production for a set duration, on PC as much as on mobile: gameplay, networking, engine, performance, interface, live-ops. Your tools, your rituals, your backlog — and one production contact who answers for the whole team.
Engines
On a proprietary engine, we start by reading your code
Platforms
A team that knows both economies, premium and mobile
Disciplines covered
Eight fields, taken on their own or as a batch, on PC as much as on mobile. If your need falls between two of them, say so: we would rather turn a job down than take it half way.
Game systems, controls, AI, saves, progression. From a throwaway prototype to a delivered, documented feature.
Local and online co-op, state replication, sessions and reconnection. The brick we built ourselves on Papy Crouton.
Work inside the sources: C++ modules and plugins, editor extensions, fixes forward-ported across versions, third-party SDK integration.
CPU and GPU profiling, memory and frame-time budgets, LOD, culling, load times, holding up on low-end configurations.
Screen flow, wireframes, mockups and engine integration. Design and code by the same team.
Seasons, events, additional content and post-launch fixes. Player feedback tracked and patch windows held.
Ad SDKs and mediation on PC and mobile: rewarded formats, interstitials, banners, and consent handling.
Tagging plan, third-party analytics SDK integration on PC and mobile, normalised events and dashboards you can actually use.
The sequence
We join a project at any of these milestones. What changes is what we ask for on arrival and what we hand over on the way out. Pick a milestone for the detail.
We pull the repository, build it, read it. Engine version, dependencies, branching strategy, naming conventions, build times and validation gates: we put your chain next to ours and list the gaps.
Game intent, core loop, references, target and platforms. We turn an idea into a document you can defend in front of a publisher or a financier, with the technical risks already named.
One question only: does it play. Deliberately throwaway code, placeholder assets. We measure how it feels with a controller in hand, not how clean the architecture is.
Vertical slice, asset pipeline, conventions and performance budgets. We settle now everything that would cost a fortune to change once production is running.
The bulk of the volume, at the pace of your sprints. The same people from the first milestone to the last, with a producer as the single point of contact answering for the whole team.
The game is complete in features, not yet in content. We stabilise, wire up analytics and the ad placements if there are any, and start measuring for real.
Content complete, bug hunting and balancing on real data. A regression pass on every candidate build, and the bug curve tracked until it comes down.
Compliance, terminology, certification checklists. We prepare the submission and work the platform’s feedback through to build acceptance.
Seasons, events, fixes and player feedback. And the day you take the code back, everything is documented for someone who was not in the room.
Contact
Reply within 48 working hours.