Create and improve games with PlayDrop Cloud

Open Create and sign in. Explain what the player does repeatedly, what makes the game challenging, and how a round ends. A small, specific first version is easier to test than a request for many unrelated systems.

Include the genre, controls, goal, visual direction, and target devices. For example: “Create a top-down collecting game. Move with the arrow keys or a touch joystick, avoid moving hazards, and collect 10 gems to win. Use bright, readable shapes and a restart button.”

When creation finishes, play a full round. Try starting, moving, winning, losing, and restarting. Look for unclear instructions, blocked progress, and controls that fail on your intended device. A working desktop version does not prove that the touch controls work.

Return to the creation conversation. Explain the observed behavior and the desired change. “After losing, the restart button keeps the old score; reset the score to zero” is more useful than “fix the game.” Tell Cloud which parts to preserve when asking for a visual or gameplay change.

Test after each meaningful change. If several things are wrong, fix the problem that prevents playing first. Then improve difficulty, feedback, and presentation.

Creation, updates, and remixes are paid in credits. Review plan limits before launching several tasks: Basic runs 1 task at a time, Plus 5, and Pro 10. Generating assets may have its own credit cost.

Give the game a title and description that match what players can actually do. Check the images and the language inside the game. Add only listing translations that accurately describe the published version. Follow publishing and sharing when the game is ready.

The selected effort sets the price of a task: Light 100, Medium 200, High 400, and Max 1,000 credits. The composer shows the price before you start, and a failed task is refunded to the balances it used. One game may need several creation and update tasks, so check your balance before a series of changes.