VARDYN
How it works Ways to Play Bestiary Servers Pricing For players Player Handbook Streaming Kit For owners Setup Manual Roadmap Fleet Status Contact Get Started

For server owners

How Vardyn actually works

No signup, no demo call. This page shows what the bot reads, what it does about it, what it genuinely cannot do, and every system you can switch off. All of it is interactive — poke at it before you decide.

Start a 7-day trial See the player tutorial

1 — The loop

Vardyn watches your server, decides something should happen, and makes it happen. That is the whole product. Press Run the loop to walk one cycle.

Your SCUM server writes events as they happen Vardyn reads kills, joins, chat, positions Vardyn decides your switches, your dials Vardyn acts in your game, in Discord and the world changes

A worked example of one cycle, not a live feed.

2 — What it can and cannot do

SCUM ships no remote-console API. Everything any bot does on a SCUM server is built on the game's own admin commands, and that sets hard edges. Here they are, plainly.

Vardyn can

  • Read every event your server logs — kills, deaths, logins, chat, positions, squads, vehicles
  • Place puppets, animals, armed NPCs, vehicles and items at chosen coordinates
  • Message one player privately, or the whole server
  • Move a player, heal them, give in-game money, adjust fame
  • Read and write your server settings, and hold them across restarts
  • Track who owns what: bases, vehicles, squads, territory
  • Run all of it on a schedule, with no admin logged in

Vardyn cannot

  • Write new AI — a spawned NPC behaves exactly as SCUM makes it behave
  • Add items, weapons or creatures that are not already in the game
  • Touch netcode, physics, rendering or anything client-side
  • Require your players to install anything — they join normally
  • Do anything at all while your game server is down
  • Exceed SCUM's own ceilings on characters and puppets alive at once
  • Know what happened before you turned it on
The honest question, answered. Yes — underneath, these are the game's own admin commands. The work is everything around them: getting a command to run when no admin is online, knowing where the ground is at any coordinate so a spawn does not land in the sea or 800m in the air, deciding who has earned what, and keeping the whole thing upright unattended for weeks. The mechanism that lets commands execute with nobody at a keyboard is ours and stays ours. What it produces is on this page in full.

3 — Try the difficulty model

Difficulty is not one server-wide slider. It is worked out per player and per squad from what they have actually done — and the player gets a say too: anyone can type !difficulty beginner and meet no armed NPCs at all until their Fame says otherwise. Drag these and watch it move.

Fame sets how dangerous. Squad size sets how many. Holdings only ever lift a squad the bot has no combat record for — and never past the fourth rung.

Marked a typical encounter for this squad
puppets 0 armed 0 elite 0

Illustrative. Your own dials move every number here.

4 — Every system, and its off switch

This is the real list, straight out of the bot. Each one is a switch in your Discord panel. Click any of them.

5 — How much of it you control

0
systems with an off switch
one Discord panel
0
live tuning dials
no restart needed
0
SCUM settings, editable
grouped in plain English
0
button that stops everything
works even if the bot is stuck
Change a setting in-game and it sticks. If you edit something from the admin console or the server's own config, Vardyn notices and adopts your value rather than writing its own back over the top. That was a real bug once. It is not one now.

6 — What your players type

The real command list, searchable. / is Discord, ! is in-game chat.

Admin commands are hidden from players automatically, and switching a system off silences all of its commands at once.

7 — Your first week

Day 0 · 15 minutes
You hand over two things

Your server's file access and an invite for your Discord. A wizard walks you through both. You install nothing on your game server, and your players install nothing at all.

Day 0 · same sitting
The bot reads your world

It finds your players, their squads, their bases and their vehicles from the logs you already have. Your website goes up on your own subdomain with a map, a garage, a bestiary and leaderboards.

Day 1
You turn things off

Everything starts on except three. Most owners spend day one switching off what does not suit them — PvE servers kill the raid window, low-loot servers turn on low-loot waves, quiet servers cut the animals.

Day 2–3
Players notice

Patrols on the roads, garrisons at named places, a hunter that comes back for someone. This is the part you do not have to run. It happens whether or not you are awake.

Day 4–6
You tune it

Too many spawns, too few, too far away, too rich. Eighty dials, live, no restart. Most owners touch about five.

Day 7
You decide

The trial ends. If you stop, your server keeps every setting the bot wrote and simply stops receiving events. Nothing is held hostage.

Still have a question?

Ask it directly. We would rather answer a hard one now than sell you something that does not fit your server.

Start the free trial Ask a question Join the Discord
© 2026 Vardyn — watch over your island · How it works · Bestiary · Setup manual · Streaming kit · Pricing · Privacy · Terms · Refunds · Roadmap · Contact · Discord · Get started · Staff
Vardyn is a monthly software subscription and a product of Odin The Red Developments. Support & billing: support@vardynbot.com
🔒 Credentials are sent over TLS and encrypted at rest. We never sell your data.