Scenarios:

Settings

  1. Bots: build your map and test bots properly to avoid any issues with movement or collisions. If your scenario uses only static bots uncheck "Enable bot movement" in your bot profiles to further improve performance.
  2. Scenario Settings: set your scenario type properly to avoid any confusion (tracking, clicking, etc.), and try to avoid setting your scenario time limit too high. Avoid fov locking as much as possible.
  3. Description: keep the description short (<75 characters). (a description is not required)
  4. Multipliers: avoid extra multipliers unless necessary. On clicking scenarios you should use reload on your weapon while on tracking scenarios you don’t need to do anything.
  5. Third person: should always be enabled for most scenarios if it doesn’t make the scenario exploitable, make sure there is enough space behind the player so that third person works well.
  6. Name: the scenario name must have less than 32 characters.

Maps

Before uploading to the workshop, make sure your map follows these requirements:

  1. Spawning: spawns should be placed with grid snap enabled and in order.
  2. Simmetry: all map blocks should be above the map editor grid and should be aligned with the “default” grid theme. Use the grid to center your character view and make sure all sides of the map are symmetrical.
  3. Skybox: bots should always have a wall behind them to avoid visibility issues.

Map Alignment examples:

Walls and floors not aligned to the Default theme.

Map_Bad_Alignment.jpg

Walls, floors and the crosshair, are aligned to the Default theme correctly.

Map_Good_Alignment.jpg

Tags

Use this table to choose the tags for your scenarios (put them in order from 1 to 4 so its easier for us to verify that tags are ok)

You can add more tags at the end but they shouldn't interfere with these tags

1 2 3 4
Author (put your nickname or another name to identify all scenarios made by you or your group) "micro" if scenario is to train micro corrections If scenario uses possession mode add "possession If scenario uses the human bot type add "human
Scenario type (tracking, switching, clicking, reflex, hybrid) if hybrid also add all the aiming types involved if possible If fov lock is enabled add "fov locked If scenario is tracking / switching add "low ttk" or "high ttk If scenario is made to train smoothness add "smoothness", if its made for reactivity add "reactivity
"flick" if reflex or flick heavy scenario If scenario is a movement based scenario add "movement If scenario uses reload on the weapon to prevent autoclickers add "reload If scenario is made for specific game(s) add the name of the game aswell (apex,overwatch,csgo,valorant,fortnite,...)