DirkScripts
Config Studio
Every dirk script on the server is configured in one panel. There is no
per-script settings file and no per-script menu — a script registers its
settings with dirk_lib, and they appear here alongside everything else.
Settings save to the dirk_scriptConfig database table and apply live — no
resource restart, no SQL edits, except for the handful of values marked
Restart required.
#Opening it
/dirk_config— opens the Studio on an overview. Pick a script from the rail on the left./<resource_name>— e.g./dirk_lib,/dirk_fishing. Opens the same Studio with that script already selected. Every registered script gets its own command automatically.
Who is allowed to run those commands is covered in Access Control.
#What is in the rail
The left-hand rail is grouped. Scripts at the top is one entry per installed
dirk script — each one's own settings. Below that are the sections that belong
to dirk_lib itself and apply everywhere.
| Section | What it covers |
|---|---|
| Basic | Language, debug, and the handful of library-wide switches |
| Appearance | The palette every dirk NUI inherits |
| Groups | Defaults for the dirk_groups system |
| Logger | Where log lines are kept, and any external logging service |
| Logs | Reading those lines back, the config audit trail, and redirects |
| Admins | Who can open the Studio, and what they may do in it |
| Bridging | Which third-party resources dirk_lib talks to |
#💾 Saving, history and reset
Every section above sits behind the same save bar, which appears along the bottom of the panel as soon as you change something. Nothing you touch is live until you press Save — edits are staged, so you can change ten things across four sections and commit them in one go, or walk away and lose none of it.
| Control | What it does |
|---|---|
| Save | Writes the staged changes. Only what you actually changed is stored — the rest keeps following the script's defaults, so an update can still move them. |
| Discard | Throws the staged changes away and puts every field back to what the server currently has. |
| Undo / Redo | Steps back and forward through this session's edits, before you save. |
| Change history | Every saved edit, who made it, and the old and new value. Any line can be reverted — which stages the change like any other edit, for you to review and save. |
| View or import JSON | The whole config as JSON, to read, copy out, or paste back in. Useful for moving a tuned setup between servers. |
| Refresh from server | Pulls the current config again, for when someone else has been editing at the same time. |
| Factory reset | Puts one script back to how it shipped. You have to type the resource name to confirm, and it still only stages the reset — nothing is lost until you save. |
Fields carry chips that tell you where a value came from and what it costs:
- Modified — this one no longer follows the default. Back to default on the field clears the override.
- Restart required — the value is read at startup, so it takes a restart of that resource to take effect.
- Server only — the value never leaves the server. View-level admins do not receive it at all; webhook URLs and service credentials are the usual case.
Last updated on 30 September 2026