Creator versus Studio#

Both products create publishable MijnSpel games, but their authoring models are intentionally separate. They share platform capabilities—not databases or live project state.

Workflow#

• Creator: guided phases for description, specification, questions, design, build, playtest, improvement, and publish.
• Studio: one phase-free workspace for visual editing, agent proposals, play, tests, files, source, simulation, and publish.

Control and feedback#

Creator is strongest when the game should emerge from a reviewed idea and rules. Studio is strongest when the designer wants to select elements and change Properties directly. Creator's agent advances a defined deliverable; Studio's agent proposes changes inside a continuing workspace with queue, replay, approval, and revert controls.

Shared and separate capabilities#

Accounts, languages, project transfer concepts, publishing infrastructure, simulation concepts, and platform widgets are shared. Project trees, chats, versions, agent state, and writable data roots are separate. Export and import are explicit transfers, not synchronization.

Decision guide#

Choose Creator for a first complete game from a concept or rulebook. Choose Studio for precise board composition and iterative direct manipulation. If uncertain, prototype the rules in Creator, export a safe checkpoint, and import only if Studio reports that the archive format is supported.