TeamSpecBot: Level Editor: playtesting workflow

2026-10-20T03:47:53Z

Level Editor: playtesting workflow

New page

You can play your map in TeamSpec at any time without exporting it yourself. There are two ways: '''Run''', which starts the game on a copy of the map, and '''Quick Playtest''', which keeps a game open that you can update from the editor as you work.

{{Note|Both need '''TeamSpec Executable Path''' set in [[Level Editor/Settings|Settings]]. If it is missing, the editor opens Settings for you and the status line says ''Set the TeamSpec executable in Settings before launching.''}}

== Run ==
The '''Run''' menu in the top bar:
* '''Run''' exports a temporary copy of the map, gamemode scripts included, and starts TeamSpec on it. The status line says ''Launching TeamSpec...'' and then ''TeamSpec launched''.
* '''Run (Console)''' does the same with the console version of TeamSpec, when there is one beside <code>TeamSpec.exe</code>, so a window shows everything the game prints. Use it to read your script's <code>api.log</code> lines and errors.

Each Run starts a fresh game. Close it when you are done.

== Quick Playtest ==
'''Quick Playtest / Apply''' starts a local playtest on your current map. Once it is running, clicking it again sends your changes to the game that is already open, so you do not have to restart after every edit. A ''Preparing Playtest'' window shows progress while the map is sent.

The list beside it chooses when changes are sent:
{| class="wikitable"
! Mode !! Sends changes
|-
| '''Manual''' (default) || Only when you click Quick Playtest / Apply.
|-
| '''Selective live''' || Supported visual edits are sent automatically, a moment after you make them, and update in place.
|-
| '''Full live''' || Structural edits are sent too. Static geometry is updated in place when that is safe; changes that need it (gameplay entities, scripts) reset the round.
|}

'''Disconnect Playtest''' stops the editor talking to the game and leaves the game open. To reconnect, start a new playtest.

=== Status messages ===
The status line reports every step:
* ''Applying playtest revision N...'' then ''Playtest revision N applied.'' with a short note on what changed.
* ''A playtest revision is already being prepared or applied.'': wait for the last one to finish.
* ''Playtest could not apply: ...'' with the reason. The game keeps the last version that worked. A script that steps outside the [[Level Editor/Scripting/Sandbox limits|sandbox]] is refused like this:
<pre>Playtest could not apply: Map validation failed: server.gd (server script): line 12: `OS` is not available to a server script; the current world is unchanged.</pre>
* ''Playtest timed out. Check the game, then start a new playtest.''
* ''Playtest disconnected. Start a new playtest to reconnect.''

== What to check ==
* Every team has spawn points, and there is a [[Level Editor/Entities/World Boundary|World Boundary]] under the map.
* Doorways, ceilings and jumps work at a player's size.
* Zones fire, doors open, outputs reach their targets.
* Bots find their way (see [[Level Editor/Workflows/Bots and navigation|Bots and navigation]]).
* For gamemode scripts, see [[Level Editor/Scripting/Testing|Testing a mode]].

== Related pages ==
* [[Level Editor/Scripting/Testing|Testing a mode]]
* [[Level Editor/Workflows/Exporting and publishing|Exporting and publishing]]

{{Level Editor nav}}

[[Category:Level Editor]]
[[Category:Level Editor workflows]]

Level Editor/Workflows/Playtesting - Revision history

TeamSpecBot: Level Editor: playtesting workflow