Creative Space
Turn a Story into a Playable 3D Game Chapter

İçerik

Provide: Story/characters/world in text/images; desired player actions, visual style, web/desktop target, playtime. Existing models, animation, audio, or projects are welcome.

Receive: A runnable web or macOS/Windows game with beginning, quest progression, ending; editable Unity project/source, models/textures/animation, asset inventory, controls, playtest record, known issues.

Plan first

Guide decisions with options/reasons rather than asking users to invent from a blank page:

  1. Genre: story exploration (default), puzzle adventure, micro RPG, open world.
  2. Three designs per genre; story exploration examples: delivery journey, care/companionship, memory puzzle.
  3. One-page story (world, protagonist's desire, obstacle, NPCs, ending), converted into player tasks across opening, development, turn, climax, ending.

The user selects/changes each stage; see . Default to one complete chapter: one explorable area, start-to-ending quest chain, 5–10 minutes. This is a complete small game, not a demonstration fragment. Add chapters after approval.

Prerequisites

  • Local-operating agent (e.g. Claude Code) able to install software, run commands, open browsers; web chat alone cannot execute this workflow.
  • Unity editor/build modules through Unity CLI; Web builds require the Web module. The user logs in and determines Unity Personal eligibility; never accept terms for them.
  • User-owned Tripo account/credits, billed independently of Flova. State expected credits and obtain confirmation before each generation.
  • Blender for model inspection/cleanup; Flova for concept/reference/UI/audio, consuming its quota.
  • Explain fees/limits before optional paid plugins (e.g. Auto-Rig Pro) or third-party accounts (Mixamo), then obtain agreement.

If Unity cannot be installed, explain the weaker visual/project capabilities and offer Three.js web delivery with the same gameplay/asset workflow.

Responsibilities and references

  • Agent: guided planning, story/quests/dialogue, code, editor/build control, playtesting, fixes.
  • Flova: scene concepts, consistent T-pose character views, props, UI/icons, NPC portraits, voices/music/effects; optional cutscenes/trailers.
  • Tripo: reference-to-model/textures, auto-rigging, preset idle/walk/run actions.
  • Blender: scale/orientation/materials, grip/contact/intersection fixes.
  • Unity: scene, controller/camera/collision, NPC/dialogue/quests/saves/UI/audio/build. Use official docs and inspect actual tools; pitfalls are in the build reference.
  • Optional Teardown — retrieve and read the full “Break Down a Reference Video into an Interactive Report” inspiration through Flova MCP by name: mechanics, camera, art, UI from supplied game/video/screens.
  • Optional Character Studio method: detailed character profile/appearance/multi-view assets.

Read at steps 1–2; at 4–5 (Flova → Tripo generation/rig/actions → Blender → GLB); at 3/6/8.

Boundaries

Use user-owned/authorized stories and characters; verify adaptation rights. Borrow mechanics/methods, not another game's art/characters/text. Models/actions/fonts/music/effects need appropriate commercial rights; record sources/licenses. Users decide paid generation/plugins/accounts/payments; do not pay or accept terms for them. Build success, screenshots, and previews do not establish completion: actually play beginning to ending. Remind users to follow publication-platform AI-art/audio disclosure rules.

Workflow

Genre/design → story/tasks → placeholder gameplay → visuals → assets → engine integration → sound/UI/cutscenes → playtest → build/delivery. Confirm the first five stages and playtest.

  1. Genre/design: Retain existing ideas; offer options/reasons from game-design. Confirm style/platform/playtime and Unity/Tripo/Blender availability. Scope one chapter.
  2. Story/tasks: Confirm one-page story, quest chain, dialogue; write docs/gdd.md including map/asset inventory and Tripo-versus-engine-built choices.
  3. Placeholder gameplay: Before art, use cubes/capsules for the whole walk/talk/item/ending/restart chain. Let the user test fun, story coherence, scope. Art cannot rescue invalid gameplay.
  4. Visuals: Flova scene concepts, T-pose multi-view characters, key props, UI style. Confirm consistency before spending Tripo credits.
  5. Assets: Follow pipeline; generate/check protagonist appearance, riggability, animation first. After approval, batch NPCs/props. Build floors/walls/fences/huts directly in-engine where practical. Quote credits before each submission.
  6. Engine: Replace placeholders individually; connect animation/dialogue/quests/UI. Import GLB characters following unity-build.
  7. Sound/UI/cutscenes: Generate Flova music/effects/voices and bind events. UI uses the user's language; add opening/ending cutscenes if needed.
  8. Playtest: Follow unity-build's checklist from start to ending; record/fix/retest. Show actual recording/screens and known issues for confirmation.
  9. Build/deliver: Requested target, project/source/assets, inventory with sources/licenses/generation records, controls, tests/issues. For publication, provide official hosting/store instructions; the user publishes.

Project directory

game-<name>/
├── docs/        gdd.md, asset inventory, playtests, known issues
├── concept/     Flova concepts, multi-view and UI references
├── assets/      tripo-out (originals), engine-source (clean GLB), audio
├── blender/     Inspection/correction .blend
├── unity/       Unity project
└── builds/      Web and desktop targets

Material process

Flova produces reference images → Tripo generates models, rigging, and actions → Blender checks → organizes them into GLB → engine. The original downloaded file remains unchanged, and any modifications are saved as new files.

Flova produces reference pictures

  • Character: Uniform T-pose multiple views (front, side, back), full body, white or solid color base, even light, arms and legs apart, no holding things. For multiple views of the same person, show the front view first, and then show other angles after confirmation.
  • Props: A single piece, with a white background and a slightly downward view from the front so that the shape can be seen clearly.
  • Scene: The concept drawing is only used to determine the style, color matching and layout, and the scene structure is built in the engine.
  • The style of painting is unified throughout the film, and it is written as a unified setting, which can be reused verbatim for each request.

Tripo

Document: https://developers.tripo3d.com/en/docs/cli. The commands, model versions and prices are subject to the documentation and actual results after connection. A few things that are easy to step on:

  • Check balance and estimated cost first: Submit after user confirmation. The estimated deduction may be different from the actual deduction. The balance will be checked after each submission and recorded in the resource list.
  • Make a protagonist first: After generation, check the appearance and whether the bones can be bound, then bind the bones and set the actions; confirm that the entire link is OK, and then make NPCs and props in batches.
  • Multiple views are more stable than single front views: The back and side structures are more complete.
  • Bone binding and action export to GLB: One GLB can contain multiple action clips (standby, walking, running) together.
  • In-place clips: Different hip offsets can cause jumps. Anchor horizontal translation to the bind pose; retain vertical motion/rotation. Download helper ZIP (1,243 bytes; SHA-256 3741bf44ed942fe717d895404ea3804c6346e8bb6f5badc8f182963204ba60b8), verify, then extract. Run python3 3d-game-helpers/scripts/normalize_hip_offset.py <input.glb> <output.glb>. Assumes mixamorig:Hips; change it in the script if different. Use only for hip-offset jumps; retest transitions.
  • The downloaded original file is placed as assets/tripo-out/, and the modified one is placed as assets/engine-source/. The engine only reads the latter.

Blender Check

Use background Blender to import GLB, render four images from the front, back, and both sides, and extract a few frames of action:

  • The appearance is consistent with the reference picture, there are no missing limbs, broken faces, or arms glued to the body;
  • Size and orientation (note the height and scale it uniformly in the engine);
  • Are there any obvious distortions, molding, or slippage in the movements;
  • Material: Tripo's materials are often too bright and plasticky. Make a note of them and lower the highlights and metallicity in the engine without changing the original file.

Only inspections and minor repairs, no model redoing in Blender. Problems e.g. gripping and contact between hands and props can be fixed in this step or solved by using hanging points in the engine.

Alternative character rigging route

If you are not satisfied with the effect of Tripo's automatic bone rigging, you can use the Blender plug-in Auto-Rig Pro to rig the bones, and then take the action from Mixamo. Auto-Rig Pro is a paid plug-in. Mixamo requires an Adobe account and has regional and humanoid character restrictions; inform users before using it.

Use GLB uniformly

Characters and props are delivered to the engine in GLB. Converting to FBX is prone to problems (the action track cannot be exported silently by default, and the scale and skin are wrong), so it is not the default.

Record

Each generation task is recorded in the resource list: task ID, input map, parameters, actual deductions, product files, and inspection conclusions.

gameplanning

The planning is divided into three steps. Each step gives the user several options for the user to choose or change, preventing the user from starting from scratch:

Choose a genre → Choose a plan → Write stories and tasks

Use the parts that the user has already thought about clearly and only fill in the gaps.

1. Select type

GenreWhat it feels like to playSuitable story
Plot Exploration (default)Walk slowly, see the scenery, chat with people, the story unfolds little by littleWarmth, healing, growth, journey, memories
Puzzle AdventureObservation, thinking, trial and error, and "it turns out" after solving the problemSuspense, ruins, secret rooms, detectives
Micro RPGAccept commissions, fight monsters or do things, become stronger, and get rewardsAdventure, fantasy, small town life
Open WorldWalk freely, discover things everywhere, and decide where to go firstThe setting of the world itself is very attractive

When the user is unsure, recommend one based on the story he gave and give a reason.

2. Options

Three options are given for each type, and the user chooses one (or a mix). Write down each plan clearly: the core gameplay loop, the structure of a chapter, and typical tasks.

Plot exploration
SolutionCore LoopStructure of a ChapterTypical Tasks
Delivery JourneyAccept the entrustment → walk over → hand it over to the person → hear the responseOne thing to be delivered connects three or four peopleSend letters, send flowers, and bring messages
Care and companionshipDiscover needs → Find things → Take care → See changesA place changes from desolate to aliveWatering, repairing, feeding, lighting
Memory PuzzleFind objects → trigger memories → spell out the pastSeveral memories gradually reveal a secretCollect tokens, dialogue and question, return to old places
Puzzle Adventure
SolutionCore LoopStructure of a ChapterTypical Tasks
Mechanism RemainsObserve → Infer the rules → Operate the mechanism → Open a new pathThree mechanisms from easy to difficult, the last one uses the rules of the first twoPull rods, alignment patterns, light path reflection
Escape RoomSearch → Get props → Use in combination → Get outA room, several layers of nested locksFind keys, passwords, puzzles
Detective InvestigationQuestion → Find clues → Testify → IdentifyThree witnesses, one contradictionQuestion, collect evidence, point out lies
Micro RPG
SolutionCore LoopStructure of a ChapterTypical Tasks
Town CommissionAccept the commission → Complete → Get reward → Unlock new commissionThree or four commissions, the last one leads to the main lineRunning errands, collecting, driving
Dungeon ExplorationEnter → Fight or dodge → Get treasures → Defeat bossesTwo or three rooms plus one bossClear monsters, open treasure chests, and defeat bosses
Growth PracticePractice → Challenge → Failure or Success → Become StrongerThree challenges with increasing difficultyPractice skills, compete, and pass the test
Open world
SolutionCore LoopStructure of a ChapterTypical Tasks
Collect and exploreSee something in the distance → Walk over → Discover collectibles or secretsA map, several landmarks, scattered collectiblesCollect, climb to the top, find hidden places
Gathering and ConstructionGather → Synthesize → Build → Unlock new areasExpand from a campCut down trees, mine, build bridges
Travel to multiple placesTravel between several areas, each area has its own storyThree areas with different styles, connected by a main lineComplete one thing in each area and return to the starting point

A chapter in the open world must also have a clear main line and end point, and freedom is only reflected in the sequence and branch lines.

3. Write stories and tasks

Story one page

Write a confirmation letter to the user, no longer than one page:

  • World: Where, what era, and in one sentence explain what is special about this world.
  • Protagonist: Who he is, what he wants (the goal of this chapter), what he lacks in his heart (what changed at the end of this chapter).
  • Hinder: What stands between the protagonist and the goal. There is no story without obstacles.
  • NPC: 1–3, each has its own wishes and plays a role in the task: giving tasks, giving clues, creating obstacles or people to help.
  • Ending: Whether the goal was achieved, what happened to the protagonist, and what final scene the player saw.
Break the story into tasks

Arranged according to "beginning → advancement → turning → climax → ending", each paragraph corresponds to one or two tasks. Each task requires the player to do one thing, not just watch:

ParagraphWhat happens in the storyWhat the player does
BeginningThe protagonist knows what to doWalk to someone and listen to him
AdvanceThe protagonist starts to actGo somewhere to get something or find someone
Turning pointSomething happened unexpectedlyThe original plan doesn't work, so we need to find another way
ClimaxUse what you learned to solve the problemComplete the most difficult step
EndingResults and changesReturn to the starting point or reach the end point and see the ending screen

Example: "Finding color for the withered garden" - Beginning: The gardener said that the flowers in the garden are not blooming; Progress: Go to the hut to get a kettle; Turn: The well is dry, and you have to go to the mountain to find spring water; Climax: Bring the spring water back to water the oldest flower; Ending: The flowers bloom, and the gardener gives the protagonist a letter.

Dialogue
  • Each dialogue should be within three or four sentences, with one meaning per sentence.
  • NPCs have their own tone of voice when speaking, not just giving out tasks.
  • Key information (where to go, what to do) is stated again in the mission prompts, so players will not get lost even if they skip the dialogue.
  • Written in the user's language, the interface and dialogue are in the same language.
Let the scene tell the story
  • Place some details on the mission route that can be understood without dialogue: an old photo, a fallen tree, a series of footprints.
  • Landmarks let players know where to go: distant towers, lit lights.
Submitted to the production list

After the story and missions are confirmed, they are organized into docs/gdd.md: one sentence, map layout (coordinates and overhead sketches), characters and NPCs, mission chain (entry conditions for each step, trigger method, changes after completion), dialogue, ending, material list (which ones are handed over to Tripo, which ones are built directly in the engine).

Rules for task chains

  • You cannot skip steps: you cannot skip tasks by taking props in advance, pressing interaction when you are too far away, or by repeating interactions.
  • The current target is always displayed on the screen; a prompt appears when you are close to something interactive.
  • Ability to restart: Characters, props, tasks and NPC statuses are all reset.

One chapter size

Duration: 5–10 minutes; an area (approximately 30×30 to 60×60 meters); 1–3 NPCs; 3–6 main steps; models to be generated: 1 protagonist, 1–3 NPCs, 2–5 key props; the protagonist’s actions are at least standby, walking, and running. When exceeding the limit, discuss with the user first what to cut.

Unity and Playtest Acceptance

Use official docs and local unity --help: https://docs.unity.com/en-us/unity-cli/use-unity-cli. These are common pitfalls, not a replacement manual.

Pitfalls

  • Control the editor through Unity CLI, not deprecated editor MCP or similarly named third-party tools. Controlling a running editor requires Unity 6+ and its Pipeline package installed in the project.
  • The user handles login, license eligibility, and terms, including first-launch terms.
  • Import character GLB directly with official glTFast; use Legacy animation. Measure scale from bind-pose meshes. Put scale/orientation on an extra parent so animation does not override them.
  • Web builds may strip indirectly referenced components, e.g. dynamically created colliders. Preserve them with link.xml or disable stripping.
  • Make scene/build editor-script entrypoints rerunnable after changes.

Playtest

Build success/screenshots/model previews are insufficient. Play every delivery target start to finish; record in docs/试玩记录.md:

  • Quests: every step required/completable, correct ending, full restart reset.
  • Story: dialogue/hints explain destination/actions; turns/ending are apparent.
  • Controls: move/run/camera/interact work.
  • Character: natural animation changes; no foot sliding, position jumps, intersections; plausible hand/prop contact.
  • Collision/camera: no wall penetration, trapping, camera clipping, lost character.
  • Performance/errors: acceptable frame rate/loading; no console errors; warnings listed as known issues.

Automate testable quest-state/reset checks and also record manual playtest results.

Yaratıcı süreç

  1. Flova

    Flova

    Generate game assets

    Create character, scene, and prop references, plus interface and audio assets.

  2. Tripo

    Tripo

    Generate character models

    Turn character references into 3D models and add basic animations.

  3. Blender

    Blender

    Prepare models and animation

    Adjust scale, materials, and animations for import into the game.

  4. Unity

    Unity

    Build a playable game

    Add exploration, dialogue, and quests, then export the game and project.