Looking for quality Plugins? Restore Monarchy - Simplicity over Complexity!
Login
uScript Documentation

Getting Started

Set up uScript and ship your first server script quickly

This guide covers the original loader install flow, the expected folder structure, script-specific and global commands, and a few practical tips that make the first setup smoother.

uScript2.zip Package
.uscript Script Extension
/script reload Reload Command
On Startup Auto Load

Install uScript

Start with the loader package and let uScript generate its server folders after the first restart.

  1. Download uScript2.zip from the Discord loader-download channel or from the direct package link.
  2. Extract uScript2.zip into the root directory of your Unturned server.
  3. Restart the server so uScript can finish its initial setup.
  4. Open the generated Servers/YourServer/uScript directory in your server files.

Create Your First Script

uScript keeps the first iteration loop simple: create a file, save it in the script folder, reload, then test in-game.

  1. Create a new file with any name you want, but make sure it ends with .uscript.
  2. Save that file inside Servers/YourServer/uScript/Scripts.
  3. Use /script reload after adding or editing scripts.
  4. Verify the script loads correctly before moving on to larger changes or shared dependencies.

Install Compatible Modules

Some setups depend on DLL-based helper modules. Those belong in the dedicated module folder, not next to individual script files.

  • Place compatible module DLLs in Servers/YourServer/uScript/Modules.
  • Keep third-party module versions organized so script issues are easier to debug later.
  • If a script expects a module, install that dependency before assuming the script itself is broken.

Commands and Workflow

The basic workflow is intentionally lightweight and favors fast iteration on live server files. Anything in square brackets [] is optional.

  • /script load [scriptName] loads one specific script when you want to bring in a single file.
  • /script reload reloads all scripts without restarting the full server.
  • /script reload [scriptName] reloads only one script, which is useful when you want a tighter edit-and-test loop.
  • /script unload [scriptName] unloads one script without touching the rest of the active script set.
  • Scripts inside the Scripts directory are loaded automatically when the server starts.
  • Global reloads are especially useful after changing multiple scripts, while script-specific reloads are better when you are working on one file repeatedly.

Practical Tips

Small workflow improvements and editor setup details that are useful in day-to-day scripting.

  • If you use Notepad++, import npp_lang.xml via Language > Define Your Language > Import from the documentation package or from this syntax-highlighting archive.
  • Use /script reload instead of full restarts whenever you only changed script logic and do not need a cold boot.
  • You can configure multiple servers to share the same script, module, and data directories when you want one maintained source for several environments.