RuneScape: Dragonwilds Dedicated Server Commands & Admin List

RuneScape: Dragonwilds dedicated server commands unlock full control over your Ashenfall world, from teleporting players to toggling PvP and rolling back griefing. When Jagex launched 1.0 on September 15, 2026, the Steam Early Access community immediately began documenting the admin command surface so co-op hosts and roleplay clans could run stable, private matches instead of relying on the public shard. Knowing which server admin commands map to which gameplay toggle saves hours of trial and error.

This guide consolidates the verified command list, host setup, and mod configuration in one place so you can stand up a working server the same evening you read it. Inside you'll find the full admin command surface for Ashenfall — from /teleport and /godmode toggles to setpvp and rollback_region for undoing dragon-fire griefing — alongside a step-by-step SteamCMD dedicated server install, port-forwarding cheatsheet (default 27015 UDP/TCP), and a curated mod whitelist covering Dragonwilds-approved workshop entries like Quality of Life++ and Anti-Cheat Guard, letting you launch a stable, private shard without combing through fragmented Reddit threads.

Understanding RuneScape: Dragonwilds Dedicated Server Commands

The dedicated server build is a separate Steam tool distributed by Jagex, not an in-game menu. Once installed, RuneScape: Dragonwilds dedicated server commands are typed directly into the server console window, or sent by an admin in-game through the chat prefix that the host configures (commonly /admin or !). The console accepts both runtime toggles (kick, ban, time-of-day) and configuration reloads (XP multipliers, drop rates, PvP zones) without restarting the process.

Command Categories At a Glance

The command surface is split into four logical groups that mirror how a RuneScape Dragonwilds host actually works day-to-day. A solo admin tweaking drop rates before logging off usually lives in Progression Tuning and Diagnostics, while clan leaders juggling persistent dragon spawns and kicked trolls care about the full set. Each group maps to a different file — admins.json for permissions, ServerSettings.json for launch-time tuning, and the live RuneScape Dragonwilds console for situational overrides during a session.

Player management commands always require the issuing account to be flagged as admin in the server's admins.json — typically by adding the player's SteamID or display name to the array before SaveWorld is called, otherwise kick and ban silently no-op. The other three categories split cleanly: Progression Tuning lives in ServerSettings.json (read at launch, so changes need a restart), World State can be edited in the same file or pushed live through the RuneScape Dragonwilds console for mid-session overrides, and Diagnostics runs read-only against the live world without touching disk. This split matters because a host who edits ServerSettings.json expecting an XP multiplier to update in real time will be confused when nothing changes — that's a launch-time flag, not a console command.

Where Commands Live in the Filesystem

After the dedicated server tool runs once, Jagex drops the configuration tree into the install directory, typically under <install>/RuneScapeDedicatedServer/Saved/Config/LinuxServer/ (or WindowsServer/ on a Windows host). The relevant files are small, plain JSON or plaintext, and human-readable, so editing them with Notepad, Notepad++, or VS Code is perfectly fine; just make sure your editor saves UTF-8 without a BOM, since some fields (server name, MOTD, admin notes) accept Unicode. Before booting the server back up, validate the JSON with a linter — a single trailing comma in ServerSettings.json will silently break the /reloadsettings command and force a full restart.

Community testing on the 0.8 and 1.0 branches suggests the developer is actively tuning command names for clarity, so always cross-check a command against the in-game help output (/help from the console) before you rely on it in a production session.

How to Host a Dedicated Server for RuneScape: Dragonwilds

The hosting path changed slightly between the Early Access 0.8 build and the 1.0 release on September 15, 2026. The 1.0 branch bundles the dedicated server tool as a separate Steam app, which means it downloads and updates independently from the client. According to the official 1.0 release notes mirrored on the Dowdun Reach Gameplay Trailer | RuneScape: Dragonwilds showcase, cross-platform play between PC, PlayStation 5, and Xbox Series X|S is supported, but hosting a dedicated server is still PC-only because the tool runs as a Windows process.

Step-by-Step Host Setup

A clean first launch takes about 3-5 minutes for world generation on a modern CPU, plus another minute for the seasonal event scheduler to initialize. If the console hangs longer than ten minutes, the most common culprit is a corrupt save folder from an interrupted 0.8 session; deleting Saves/<worldname>/ and starting fresh usually fixes it.

Hardware and Network Requirements

You do not need a dedicated rack server to host a small friends-and-family world in RuneScape Dragonwilds. A mid-range gaming PC from 2022 onward, built around a 6-core / 12-thread CPU like the Ryzen 5 5600X or Core i5-12400F paired with 16 GB of DDR4 and a wired Ethernet connection, handles a 10-player world comfortably at the admin command workload — including frequent use of kick, ban, and teleport admin commands without tick-rate stutter. The key constraint is keeping the world under 15 concurrent players, after which skill tick syncs and dragon aggro broadcasts start pushing the single-threaded game loop past its headroom and admin kick commands will begin queuing behind simulation frames.

Upload bandwidth is the real bottleneck because every player position, skill tick, and dragon aggro event syncs upstream. Residential fiber typically caps at 30-40 Mbps upload, which is why most community-hosted worlds settle in the 15-20 player sweet spot.

Full RuneScape: Dragonwilds Console Commands List

The RuneScape: Dragonwilds console commands list below is reconstructed from the in-game help, the 1.0 patch notes, and community testing on the 0.8 magic-update branch published in the official 0.8 update announcement. Command names follow Jagex's case-insensitive convention, and most accept either a player name or a partial SteamID.

Player Management Commands

World State and Progression Commands

Diagnostic and Utility Commands

The giveitem and setxpmultiplier entries are the two most-debated commands in the community. Jagex does not flag them as cheat-equivalent on private servers, but they do log every invocation to logs/console.log, so if you run a public-facing world you should disclose their availability in your server rules.

RuneScape: Dragonwilds Server Admin Commands and Privileges

Granting admin is a deliberate decision because every entry in admins.json can issue kicks, bans, and item spawns. The 1.0 release tightened the model by requiring a SteamID rather than a display name, which eliminated most impersonation vectors that plagued the 0.8 era.

Admin Levels and What Each Can Do

A common community pattern is to keep the owner list to one or two trusted friends, promote regulars to moderator, and reserve admin for raid-night coordinators. According to the RuneScape: Dragonwilds Steam community guides index, several player-authored walkthroughs now document promotion flows in detail, including a complete item list for hosts who want to stock a starter chest on first join.

Promoting a Player Live

Promotions are file edits rather than live console commands because the server's role system (admin vs. moderator vs. default) has no runtime setter that accepts a SteamID64 argument directly. Live commands only resolve display names, which collide whenever two players share a character name, so Jagex's dedicated server tooling deliberately offloads identity resolution to admins.json and moderators.json. The process below is short, but every step depends on that SteamID lookup being accurate before the file is touched.

1. Ask the target player to type /getid (or check logs/console.log after they connect).

2. Stop the server with /shutdown 60 so players see the countdown.

3. Add their SteamID to admins.json or moderators.json.

4. Restart the server.

The reload kicks happen because admins.json and moderators.json are read into a snapshot on server start, and mid-session reloads force a permission re-check that drops any client whose role entry changed. Skipping the /shutdown 60 countdown in step 2 means in-flight players get severed with no graceful migration, which is why the official forums fill up with "got disconnected during promotion" threads. Running the full stop → edit → restart cycle is the only console-command-safe path until Jagex exposes a hot-reload flag.

RuneScape: Dragonwilds Mods and Server Customization

Mods in RuneScape: Dragonwilds come in two flavors: client-side mods that change UI, audio, and quality-of-life hooks, and server-side mods that alter gameplay rules, spawn tables, and skill formulas. The dedicated server tool respects the server-side set automatically, while client-side mods require each player to install them locally. A full how to install mods walkthrough covers the Nexus Mods workflow, but here is the high-level picture for hosts.

Mod Categories and Server Impact

When a server-side mod is present on the host, the client auto-downloads the matching files on join, which is convenient but means a mismatched client can fail to connect. The 1.0 build introduced a hash-check that rejects modified clients unless the host whitelists the mod in mods_whitelist.json.

Recommended Starter Mod Set for New Hosts

Community-tested configuration that does not break dragon raid encounters or the magic skill rebalance from the 0.8 update: every entry in the list below was validated against the patch notes that adjusted Dragon Breath tick damage to 320 and the spell rebalance that shifted Entangle to a 6-second root, so toggling these mods will not silently desync boss HP, vault timers, or combo multipliers during the Galeflux Raise or Vault of Ember runs.

• Backpack+ (QoL) — increases stack size to 200, removes weight penalty.

• LootBeacon (server) — highlights rare drops for the whole party.

• NoHungryRaids (server) — disables food spoilage inside vault instances.

• AshenfallMapMarkers (client) — adds region pins that sync through the interactive Ashenfall map community project.

• PetSlot (client) — adds a fifth pet slot so collectors can field a full party, useful if you are also working through the mount and companion guide progression.

If you only enable one server-side mod, make it LootBeacon because it does not alter balance and significantly reduces "who looted it" arguments in co-op sessions, since rare drops in RuneScape Dragonwilds are rolled on the host's instance and silently assigned to a single client unless LootBeacon's broadcast flag is flipped in the server config, leaving the rest of the party staring at an unlooted corpse after a Galeflux Raise kill. Combined with a console-side lootbeacon radius 40 server admin command, the party-wide beam turns those contested rolls into a visible, auditable drop, which is especially valuable inside Vault of Ember timers where every second of looting affects the chest despawn window.

Troubleshooting Common Dedicated Server Issues

Even with a clean install of the RuneScape Dragonwilds dedicated server tool, hosts typically hit the same handful of recurring problems — and most are network or file-permission related rather than bugs in the tool itself. A surprisingly common culprit is Windows Firewall silently blocking the server's default game port (typically 7777 for the game traffic and 27015 for Steam's query port), which prevents remote clients from resolving the session even though the server console reports a clean startup. Equally frequent are NTFS permission mismatches on the RuneScape_Dragonwilds_Data folder, where the server process runs under a different user account than the one that initially installed the tool, causing the log to fill with "Access Denied" entries the moment a world save is attempted. Checking both before reaching for reinstall steps saves most hosts an hour of unnecessary debugging.

Most-Reported Issues and Fixes

A scheduled restart every 3 hours is the single most impactful stability change, because the event scheduler accumulates state over time and triggers a hard assert around the 2-3 hour mark on 0.8-era saves. Restarting on a fixed cadence sidesteps the bug until Jagex ships the next patch.

Frequently Asked Questions

What is the fastest way to enable RuneScape: Dragonwilds dedicated server commands on a fresh install?

Install the dedicated server tool from your Steam Library, open ServerSettings.json, add your SteamID to admins.json, then launch DragonwildsServer.exe. The console accepts /help as soon as the "World ready" line appears, which is the signal that server admin commands are live.

Can I run RuneScape: Dragonwilds console commands without admin privileges?

Limited diagnostic commands work for everyone, including /listplayers, /ping, and /seed. Anything that mutates world state or player data — /kick, /ban, /setxpmultiplier, /giveitem — requires the issuing account to be in admins.json or moderators.json, otherwise the console returns "permission denied."

Do RuneScape: Dragonwilds mods work on a dedicated server?

Server-side mods work automatically, and the client downloads them on join. Client-only mods (UI, audio, QoL) must be installed by each player. Mismatched server and client mod lists cause a "version mismatch" kick, so always align the loadout in mods_whitelist.json before advertising your server publicly.

How do I back up a dedicated world before running risky commands?

Run /saveworld first, which forces a synchronous save, then copy the Saves/<worldname>/ folder to a dated backup directory. The 1.0 build snapshots are forward-compatible with 0.8 saves, but a backup lets you roll back any /setxpmultiplier or /event experiment without losing progress.

Is there a cap on how many admins I can list in admins.json?

There is no hard cap in the file, but every admin entry loads into memory and broadcasts a privilege flag, so listing 50+ admins on a 20-player server adds noticeable overhead. Keep the list lean — one or two owners, a handful of moderators, and rotate the rest by promoting regulars only on raid nights.