Skip to content
microgames

The studio

12 crafts, 4 phases

Of the twenty-five roles in a real studio, 12 remain. The others were merged or left out for specific reasons, written out below.

These roles work inside MicroGames Engine. See the engine

Research

What is worth making: genre, platform, actual demand.

Scout

Searches the web for genres with real demand and little good supply, reading what players complain about in reviews.

Covers: User Acquisition · market analysis

Analyst

Weighs each signal on feasibility, platform, monetisation and how crowded the field is. Has a duty to say no, and to write down why.

Covers: Publishing Director · Brand Manager

Design

The design document: a day-by-day plan, gameplay, art to generate, story, rules, enemy logic.

Designer

Mechanics, rules, the core loop and the milestone plan.

Covers: Game Designer

Architect

Shapes space and pacing: levels, routes, where the tension sits and where the player gets to breathe.

Covers: Level Designer

Writer

Plot, dialogue, lore and on-screen text.

Covers: Narrative Designer · Lead Writer

Balancer

The numbers: health, damage, costs, progression curves. Checks that winning is actually reachable and that difficulty climbs without steps.

Covers: System Designer · Economy Designer

Art Director

Palette, style, the list of art to generate with prompts ready, and which existing assets to reuse.

Covers: Concept Artist · Character Artist · Environment Artist · Technical Artist

Sound Designer

Effects, music, and when they should play.

Covers: Sound Designer · Composer · Audio Programmer

Build

The game gets built milestone by milestone, checked at every step and re-released.

Builder

Writes the Godot code: controls, physics, logic, interface.

Covers: Gameplay Programmer · Engine Programmer · AI Programmer · UI Programmer

Fixer

Reads the error and makes the smallest possible change. Kept separate from the Builder because whoever wrote the code is the worst judge of their own mistake.

Covers: Gameplay Programmer (debug)

Tester

Hunts dead ends by reading the code: can you get stuck? fall off the map? is winning actually reachable?

Covers: QA Tester · Game Tester

Release

Builds for Windows, macOS, Linux and Android on top of the browser one, and store material.

Herald

The store page: description, selling points, tags, trailer script, and which platforms are worth shipping on.

Covers: Brand Manager · Community Manager · Marketing Specialist

Who is missing, and why

An agent with nothing to do is not thoroughness: it is one more place where the pipeline can break.

Rigging Artistno skeletons to rig: the games are 2D
3D Generalistwe do not produce 3D
Animator2D animation is sprite sequences, the Builder handles it
VFX Artistparticles in Godot are code: the Builder writes them
Network Programmerno multiplayer game is planned
Localization QAwe ship in Italian and English, with no voice acting
Producerthat is the Director, who plans milestones between blocks