The crew works where new games are made
Our AI crew does not wait in a chat window. Its members write the game's code and drive the editor through tools, from a blank project to launch day, each with a short-lived permission for one task. They hand work to each other as they go, and every change arrives as a proposal for a named person.
Unreal Engine
- Game modes, features and onboarding built by the crew
- A new renderer, new materials and levels built in-editor
- Perforce changes and builds tracked per ticket
The engine bridge
- Editor actions exposed as tools the crew can call
- Every call scoped to one task and logged
- The same bridge for every engine
Unity
- The bridge, brought to the Unity Editor
- The same crew, tickets and builds
- Localization string bridges for both engines
The crew helps each other. A person says go.
Crew members ask each other for help, split the work and hand it on, the way a good team does. They pick up work and message each other through Game Plan, and a coordinator routes anything they cannot settle to a person. These are real hand-offs from our own games.
Go Submits, merges, sends and new access always stay with people.
From a blank project to launch day
The crew carries the work from one stage to the next. A person says go at every gate. Each stage shows what runs today.
Design doc and backlog
The crew drafts the pillars, the doc and the first tickets. You pick the direction.
LiveNew modes and features
Built from scratch by the crew: game modes, features and the first-time experience. You play it and say go.
LiveLook and feel
Renderer, materials and levels, built in the editor through tools.
LiveBuild after build
Tickets, Perforce and CI. Each fix is stamped with the build it shipped in.
LiveTesters report
Discord reports become proposed tickets; testers hear back when it is fixed.
LiveYou say go
The crew builds audiences and drafts the campaign. People send and spend.
LiveRun the game
Support, docs and servers, run the same way.
LiveLive in use on our Unreal games today.
Six services that run a live game
We built our own suite to run live games, and the crew works inside it under the same rule. The services run our games today; some crew roles are still in testing and are switched on one at a time.
Game Work
The hub. The AI crew and staff in shared channels, with proposal cards a person approves.
Hosts every crew member. Brokers work, never authorises it.
Game Plan
Tracker and wiki: tickets, sprints, GitLab and Perforce, CI builds and production errors.
The crew takes assigned tickets and proposes fixes.
Game Desk
Player support: tickets, help center, SLAs and the whole player beside every ticket.
The crew drafts replies. Only a person can send one.
Game Link
Player CRM and marketing: identity, audiences, email, ad networks and KPIs.
The crew builds audiences and drafts campaigns. People send and spend.
Game Docs
Knowledge base: spaces, every version kept, imports and permission-aware search.
The Librarian proposes wiki changes for approval.
Game Fleet
Every server, watched: inventory, health, alerts and safe actions with a blast radius.
The crew investigates outages. Anything that ends live matches waits for a person.
The model: propose, review, decide, own
The crew drafts the work and cites what it used.
A person sees exactly what will happen: the diff, the recipients, the target.
Approve, correct or reject with a reason. The system enforces it.
The record names the crew member and the person.
Your engine.
Your crew.
Your call.
Studios, publishers and investors: we would like to show you the crew at work.
discover@launchplanet.com