Skip to content
Dashpop
Log inLog in to create

Give your agent feedback it can use

You do not need a magic prompt. Tell your agent what the player did, what happened, and what you want to change. Your creative judgment gives the work direction.

By Dashpop2 min read
In this guide

Practical guidance for creating, playing, and shaping games with the agent-native Dashpop Game Engine. Each game has its own creative controls, artwork, and source.

Describe the result you want

“Make it better” leaves the creative decision open. “The keeper slides past the cottage after I release movement; make stopping more immediate” describes a visible problem. Add what to preserve: the top speed, the island layout, and the evening light.

For a new feature, explain what it adds to the player’s experience. A secret lantern is useful because it rewards exploring an overlooked corner. Your agent can choose an implementation while you keep ownership of that purpose.

A brief to make your own

Keep my island layout and evening light. Make the keeper stop more quickly when I release movement, without changing top speed. Try a short approach to the cottage, a full-speed approach, and a restart. Tell me what changed so I can compare it by playing.

Ask for understanding when that helps

An explanation and an edit are different requests. “Explain how this greeting is selected” can be the useful next step before rewriting it. Ask your agent to inspect the current game rather than reason from an old conversation.

Dashpop exposes game content, source, controls, and runtime feedback. Ask your agent to connect its explanation to what it actually inspected. For a repair, include the exact failed action and the reported error.

Give the next attempt a useful starting point

A successful build establishes a technical check. Your playtest establishes what happened during that attempt. Deciding whether the change feels better is still your creative judgment. Keep those observations distinct.

  1. Name the game and the version or saved change you tested.
  2. Describe the input sequence and what you saw.
  3. State the result you expected.
  4. Name the choices and behavior that should survive the repair.
  5. Repeat the original sequence after the change, then try one nearby case.

Keep making

Create a game with your agent

Build a creative partnership around a playable result, useful controls, specific feedback, and choices you want to preserve.

2 min read

Keep the Editor Handbook nearby as you work. Pick one change, test it, and keep what helps.