Your first useful session in Dashpop
Create a distinctive playable with your agent, discover its own Editor, and leave with one change you want to keep.
Search game design, playtesting, and Editor workflows for the part of your game you’re working on.

50 guides
Create a distinctive playable with your agent, discover its own Editor, and leave with one change you want to keep.
Describe the experience, preserve choices you love, and give your agent a change you can judge by playing.
Navigate your game’s Editor, adjust real content, inspect its artwork, and return to Play to judge the result.
Use the Dashpop Editor’s Code and Tools views to connect visible behavior to the project and operations that create it.
Use Play, restart, screen previews, and actual device checks to give a Dashpop game a useful playtest.
Keep your game’s source, artwork, and creative choices together. Use saved edits and undo to explore changes in the Dashpop Editor.
Understand the agent-native engine that brings a playable game, its own Editor, and your creative choices together.
Build a creative partnership around a playable result, useful controls, specific feedback, and choices you want to preserve.
Build a reusable Unity collectible, understand prefab overrides and trigger events, and test repeated contact, duplicate instances, and restart.
Plan a small Three.js game with input, state, timing, pickup rules, glTF assets, restart, and browser checks. A practical workshop beyond the first render.
Learn to design for curiosity, discovery, and mastery. Play a pattern experiment, examine a courier game, and write a testable promise for your own game.
Design meaningful choices with goals, tradeoffs, readable consequences, and uncertainty. Test route decisions and repair dominant or arbitrary options.
Understand how game rules interact, how feedback loops change a game over time, and how to prototype an economy without mistaking a simulation for player evidence.
Design a first level that introduces, varies, and combines ideas. Learn about readable cues, safe practice, difficulty, recovery, and testing whether players understand.
Choose the right game prototype for your question, set a useful scope, separate design evidence from technical evidence, and write a practical experiment brief.
Run a useful first playtest, separate observation from interpretation, diagnose design problems, and compare revisions without coaching players toward your preferred answer.
A Crossy Road game-design deep dive into timing, safe spaces, readable hazards, character collecting, and small-team scope. Includes an original playable traffic experiment.
A Block Blast game-design analysis of spatial planning, piece order, satisfying clears, and fair puzzle generation. Play an original packing puzzle with undo and a worked solution.
A Flappy Bird game-design analysis of timing, readable failure, tiny goals, and the limits of learning from a viral hit. Includes an original playable timing experiment.
A Balatro game-design deep dive into scoring, Joker combinations, uncertain upgrades, and building a strategy from what a run gives you. Includes an interactive scoring experiment.
A Vampire Survivors design analysis of automatic attacks, positioning, experience pickups, upgrade choices, and power growth. Includes an interactive movement experiment.
A Celeste game-design case study about coyote time, jump buffering, readable failure, and the difference between precision and punishment. Includes an interactive timing-window experiment.
A Baba Is You design deep dive into movable rules, readable consequences, puzzle constraints, undo, and testing surprising solutions. Includes an original rule-changing experiment.
Connect a compatible AI client to Blender through MCP, choose Astra, Fable, or another model, and work from scene inspection to a tested game asset.
A practical plan for making games with GPT-6 Astra: choose an engine, write a brief, test changes, and keep a working project.
Compare GPT-6 Astra and Claude Fable 5.1 on your game project with repeatable tasks for creation, debugging, revisions, cost, and play.
Understand character images, 3D meshes, rigs, animation, and engine integration before choosing an Astra and Blender workflow.
Plan an Astra-assisted Roblox workflow with Luau scripts, explicit script placement, server-owned game rules, and multiplayer testing.
Plan a Unity game workflow with Astra, including C# scripts, scene references, prefabs, input settings, and focused debugging.
A practical asset handoff guide covering scale, orientation, materials, collisions, animation, and reimport in your game engine.
Start with a playable rule, write a useful brief, test the result, and revise your game without losing the version that worked.
Turn a game idea or design document into a first playable prototype by choosing an action, a consequence, and a question to test.
A plain-language game prompt worksheet with examples for mechanics, controls, feedback, visual direction, and useful revision requests.
Compare visual tools, templates, AI assistance, and learning a little code. Choose a first project you can understand and change.
A practical exercise for escaping game-development tutorial hell by changing a known mechanic, predicting the result, and finishing a small original loop.
Build a puzzle around a meaningful decision, define move order and end states, and test a small board before adding progression.
Plan a first platformer around a readable route, useful jump tests, checkpoints, and clear feedback before adding more levels.
Define merge order, collision behavior, spawn rules, and overflow for a small physics puzzle, then test the awkward cases.
Debug AI-generated game code by separating build errors, scene setup, state bugs, and design problems. Keep repairs small and reproducible.
Create a small art-direction sheet and check palette, shape, perspective, light, and readability before producing more game assets.
Run a small playtest, observe confusion and choices, ask useful questions, and turn feedback into one clear revision.
Understand the difference between playing on a phone, exporting a game, hosting a browser build, and releasing a native app.
Plan and test mobile game controls for simultaneous input, thumb coverage, release behavior, visual feedback, and readable play areas.
Tune response, anticipation, contact, and feedback in a small game. Compare changes on a fixed play route rather than adding effects blindly.
Test turn order, choices, and resource rules with paper pieces. Learn what paper can answer and when you need a digital prototype.
Keep recoverable game revisions, record what a change is meant to improve, and verify that source, scenes, assets, and restart behavior stay together.
Use Claude Fable 5.1 for game-development tasks with clear project context, focused revisions, and evidence from the running game.
Estimate an AI game-development session by separating access, model usage, asset production, repairs, and human time.
Plan a small game jam around one playable loop, early builds, clear ownership, and a cut list that protects the core idea.
Use Sunleaf Sprint to explore how moving platforms changes a playable route, then apply the lesson to your own game.