Play the change you mean to judge
A useful playtest starts with a known version and a question. Otherwise you can spend twenty minutes carefully judging yesterday’s jump.
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.
Make the comparison fair
Open Play and check the current game. Restart before comparing a change so your starting state is consistent. Choose one question: can you spot the lantern, can you reach the action on a phone, or does stopping now feel right?
Try the same route and input sequence before and after the change. If you also changed the layout and the speed, you can still decide which version you prefer, but the comparison cannot tell you which adjustment caused the difference.
A screen preview is a starting point
Preview different screen sizes to inspect the camera, text, and control placement. Then try an actual target device. A narrow browser viewport cannot tell you how a phone performs or how a thumb covers the scene.
Open your game’s phone preview and scan the QR code. Try a complete attempt with touch controls, including a restart. Return to the Editor with one observation to act on: a button under your thumb, a path that is hard to read, or a jump that needs a little more room.
A useful five-minute attempt
Record what happened, what the player said, and your hypothesis separately. “Walked past the lantern twice” is an observation. “I thought it was scenery” is a report. “It needs more contrast” is a possible next change.
- Start without explaining the goal and watch what the player tries.
- Play the main interaction through its outcome.
- Try an ordinary failure and restart.
- Check that the important state resets together.
- Repeat the affected moment on the screen and input that matter.
Keep the Editor Handbook nearby as you work. Pick one change, test it, and keep what helps.