Skip to content

Making Your Own Scenario

How this page is sourced

Sourced from vendor documentation. Checked against its sources. Not yet reviewed by a person.

Making a scenario is four decisions and a lot of looking things up. This page is the decisions. The lookups are on Where Each Setting Lives, and the field detail is in the official documentation.1

  • You are editing, not authoring. Every scenario starts as a copy.12
  • Pick the donor for its shape. Closest beats most popular.2
  • Decide the demand before the settings. Otherwise you tune toward nothing.
  • Change one thing. A version that differs in five ways explains none of them.

You are always starting from someone else's scenario

There is no blank scenario. You download one, unpack it into its profiles, and replace the parts that matter.12

That makes the first decision a choice of donor. Pick the scenario whose shape is closest to what you want, not the one you have heard of. A donor that already moves targets the way you need saves you the hardest edit.

A scenario holds the challenge rules, the scoring and the tags, and links to a player character and a bot. The bot links to its own character profile, which carries target size, health and spawn, and optionally to a dodge profile, which carries how the target moves.Bassel Bakrhttps://github.com/Bassel-Bakr/aimScenarioChallenge · Scoring · TagsPlayer characteryour hitboxes and weaponsBotwhich character, which dodgeBot charactersize · health · spawnDodge profilehow the target movesrequiredoptional
What a scenario is made of, and which profile holds each decision.

Unpacking writes the scenario's profiles to your machine as separate files, which is why a scenario is several things rather than one.1

Four decisions

What should be hard? One demand, named in a sentence. If you cannot write the sentence, the design is not finished, and no amount of editing will finish it.

How hard? Hard enough that you fail in one identifiable way. A run that fails for reasons you cannot name is not measuring anything.

What should be quiet? Everything not under test. Random spread, a reacting bot and a cramped map all add movement to the score that did not come from you.

How will you know it worked? Decide the comparison before you build. Usually that is a scenario you already play, run in the same session.

Four numbered questions appearing one after another: what should be hard, how hard, what should be quiet, and how will you know it worked. Each carries a one-line note on what answering it means.Bassel Bakrhttps://github.com/Bassel-Bakr/aimBefore the editor opensfour answers, in this order1What should be hard?one demand, in a sentence2How hard?you fail in one nameable way3What should be quiet?everything not under test4How will you know?the scenario you compare against
Four answers, in this order. Each one is only answerable once the one above it is settled.
Two panels showing the same scenario under different settings. On the left a narrow spawn box and a slow dodge keep the target near the crosshair, so the run asks for small corrections. On the right a much wider spawn box and a faster dodge carry the target far past the crosshair, so the run asks for large repositioning.Bassel Bakrhttps://github.com/Bassel-Bakr/aimNarrow spawn, slow dodgesmall correctionsSpawn Offset Min and MaxDodge profileWide spawn, fast dodgelarge repositioningSpawn Offset Min and MaxDodge profile
Two settings, one scenario. Spawn spread and dodge speed set what the run demands.

Then do the edit

The mechanics are short, and the official pages carry them in full.12 In short, download a close scenario, edit it, unpack it. Change the profiles holding your demand. Name it on the Main and Challenge tabs, tag it, and save under a new name.

Two things reliably waste an afternoon. Profiles named only on Main never reach challenge mode.32 Changes made in the Session Manager are never saved.4

You do not have to save to test. With the editor open, Play applies profile changes immediately.1

Common mistakes

  • Opening the editor before you can say what the scenario should be hard at.
  • Picking a famous donor rather than a close one.2
  • Changing the demand and the noise in one edit, so the result explains nothing.
  • Keeping a scenario after the weakness it was built for stopped being your weakness.

In practice

Build in one session, train in the next. A scenario you keep editing has no history, and history is what turns a score into information.

Do this next. Write one sentence naming what your scenario should be hard at, then find the existing scenario closest to it.

Resources

References

  1. KovaaK's, Intro to Scenario Creation, KovaaK's Wiki · REF-79 ↩↩↩↩↩↩

  2. KovaaK, How to create your own scenarios and uploading to the Steam Workshop, Steam Community · REF-85 ↩↩↩↩↩↩

  3. KovaaK's, Edit Scenario Window, KovaaK's Wiki · REF-80 ↩

  4. KovaaK's, Session Manager, KovaaK's Wiki · REF-84 ↩