Use console commands in the world where mistakes are reversible
- Step 1: Open a copied or disposable world, press F5, type
devcommands, and wait for the confirmation message before using another command. - Step 2: Enter one command such as
spawn [prefabName] [amount] [level], press Enter, and inspect the result in the world or inventory. - Step 3: Type
save, close the console, reload the copied world, and compare the result with the planned test before returning to the normal progression save.
devcommands
save
spawn [prefabName] [amount] [level]

After launching with -console, press F5 in a world and enter devcommands. Common commands are save to write the world, pos to print your position, goto x y z to move to coordinates, spawn <prefab> <amount> <level> to create an item or creature, and removedrops to clear nearby loose drops. kick <name/steamID> belongs to the server-admin command path. Commands can change or damage a save, so use a copied world for tests.
Console commands are useful for a controlled test, a recovery check, or a private experiment. They are not a substitute for normal progression, and the command result depends on the active world, permissions, syntax, and target name.
- Open a copied or disposable world before enabling
devcommands. - Use the smallest command that answers the question and inspect the world or inventory immediately.
- Save the test result, reload the copy, and keep the normal progression save outside the experiment.
Console test boundaries
| Need | Find first | Verify in the copy |
|---|---|---|
| Item | Item ID and the spawn parameter order | The expected object appears in the inventory |
| Creature or boss | Character ID and a clear test area | The expected entity appears at the intended level |
| Command | Command syntax and required parameters | The world or player state changes exactly once |
Confirm the result in game
The command, world, version, and resulting state are recorded before the save is reused.
If joining or applying the setting fails
- Stop issuing commands when the result differs from the plan.
- Restore the copied save or backup instead of trying several fixes at once.
- Keep developer testing separate from normal progression.