EvonX

Evolve your game

Ask for changes to your game in plain language — a new obstacle, harder levels, a new look — and watch EvonX build and test them in your preview.

The first version of a game is never the final one. In this step you'll ask for your first real change to Crown Match and watch EvonX carry it from a sentence to a tested build in your preview.

Ask for a change

  1. Open your game's chat and describe the change while looking at the preview:

    Add ice as a new obstacle from level 9: a piece under ice needs two matches next to it before it breaks.

  2. Send it. EvonX reads what your game is made of and tells you how it will build the change — a tuning value, new levels, a new obstacle or a new system — and the one sentence it will be tested against.

  3. If the direction is off, say so before the work starts — steering early is cheap.

What happens while it builds

EvonX makes the change in its own workspace, generates any new art it needs, and checks every step before it goes live: the game is type-checked, built and played by automated playtests, and a screenshot of the screen it touched is looked at against what you asked for. See Automated testing.

Each finished step goes live in your preview, so you can play the new obstacle as soon as it lands.

Keep or change it

Play the change in the preview. If it is not quite right, say what to adjust in the same chat — "the ice should take three matches", "make it bluer" — and EvonX revises it. Your game keeps every version, so nothing you liked is lost. Details: Publishing changes.

Check your work

You've completed the core EvonX loop: describe → build → test → play in the preview. Every future change to your game, small or large, follows this same shape.

Next step

Time to share it: Publish your game. To go deeper first, read Effective prompting on EvonX.

Last updated: October 11, 2026