Demo Territory
Base protection built on the vanilla flag pole, with a raid alarm that tells your group when the base is hit. Claim a flag and share its code with your group. Members can build inside the circle and everyone else can't. Put a powered alarm inside and a raid sounds a siren, pops up for every member who's online, and can post to Discord.
- Claim a flag and get a 6-character share code. Friends join by typing it at the flag.
- Protection while the flag is up: outsiders can't build, place items or lock your walls inside the circle.
- Your territory on the map, drawn as a circle only you and your members can see.
- Owner tools: kick and ban members, lift bans, name the territory.
- Territory Alarm. Runs on a generator, a Demo Power battery bank or a truck battery. Raids sound a 2-minute siren that also draws the infected.
- Raid alerts for damaged or destroyed walls, explosions, dismantling, code lock raids, the flag being lowered and the alarm being sabotaged.
- One raid, one conversation. An opening alert, updates no faster than once a minute, and a summary when it's over.
- Discord through a channel webhook, or DMs to each member.
The numbers on this page are the defaults. Servers can change most of them.
Items
| Item | What it is |
|---|---|
| Territory Alarm Kit | The alarm, boxed. Heavy, carried in both hands. Deploys into a Territory Alarm |
| Territory Alarm | Siren unit. Heavy, carried in both hands. Plugs into a generator or a Demo Power battery bank, or runs on a Truck Battery |
Territories use the vanilla Flag Pole and any flag. The mod adds no flag items of its own, but it shrinks every flag pole to a fifth of its vanilla size so it's easier to fit inside a base.
Getting started
- Build a flag pole, attach a flag and raise it.
- Look at the pole and use Claim Territory. A popup shows your share code, for example
K7MPX3. - Give the code to your group. Each of them walks up to the flag, uses Enter Territory Code and types it in.
- Open the map. Your territory is a circle around the flag.
- Find a Territory Alarm Kit, deploy it inside the circle and give it power (see The alarm).
Territories
Claiming
- Claim Territory appears on an unclaimed flag pole that has a flag attached.
- The circle reaches 60 m from the pole in every direction. It covers everything inside it, at any height and underground.
- You can own 1 territory and a territory holds 16 people, owner included.
- A new territory needs space. You can't place a Flag Pole Kit, or claim a pole, within 120 m of another territory's flag (twice its radius). On servers that allow overlapping territories the pole only has to stand outside every other circle (see Overlapping territories).
Joining and leaving
- Stand at the flag (within 10 m) and use Enter Territory Code. Codes aren't case sensitive.
- Leave Territory at the flag takes you off the list. The owner can't leave: a territory lasts as long as its flag.
- Each flag shows you one territory action, whichever fits who you are: Claim, Enter Code, Manage (owner) or Leave (member).
Managing (owner)
Manage Territory at the flag opens the Territory window. The title shows the name, if you've set one, and the share code.
- The MEMBERS tab lists you, your members and anyone you've banned. A DM tag shows who will get Discord DMs.
- Kick removes a member and bans them. Without the ban they could simply type the code again.
- Banned players are greyed out with an Un-ban button.
- Kick and Un-ban only work while you're standing at the flag.
- The ALERTS tab holds the alert settings (see Alert settings).
Protection
While the flag is up, people who aren't members can't do these things inside the circle:
| Action | Blocked for outsiders |
|---|---|
| Build parts | Yes |
| Place or deploy items (crates, tents, kits, fireplaces) | Yes. The hologram turns red. Explosives and traps are always allowed |
| Attach a combination or code lock | Yes |
| Dismantle parts | No. Raiding works the vanilla way |
- Nothing tells you when something is blocked. The action just doesn't appear, or the hologram turns red.
- Protection stays on until the flag is lowered into the bottom tenth of the mast. Below that, anyone can build and place.
Losing a territory
A flag that reaches the bottom of the mast deletes its territory. That includes its members, code, name and alert settings. The pole survives and anyone can claim it again.
- Anyone can lower any flag. Getting to your flag and running it down is how a territory is raided.
- Vanilla flags also lower themselves slowly as their refresher runs out (a fully raised flag lasts about 40 days). Raise yours from time to time.
- Destroying or dismantling the flag pole deletes the territory too.
The map
Only territories you belong to are drawn.
| Colour | Meaning |
|---|---|
| Gold | You own it |
| Green | You're a member |
| Grey | Its flag is low and protection is off |
| Yellow edge | An older territory overlaps yours here, see below |
Overlapping territories
Some servers let circles overlap. Where they do, the older territory rules the overlap: building, protection and alerts there belong to it. Your circle is drawn cut short along a yellow edge. When the older territory goes, the cut disappears and the ground becomes yours.
The alarm
Setting it up
- Deploy the Territory Alarm Kit inside a territory you belong to. The hologram turns red anywhere else.
- Give it power, either way:
- Cord: pick up the alarm, look at a power source and use Plug in, then place the alarm where you want it. The cord is 30 m. It plugs into:
- a vanilla Power Generator,
- a Demo Power Battery Bank with its Power Inverter attached, or a Power Strip plugged into one (on servers that run Demo Power).
- Battery: attach a Truck Battery to the alarm. A car battery doesn't fit. A full truck battery runs it for about 5 days.
- Cord: pick up the alarm, look at a power source and use Plug in, then place the alarm where you want it. The cord is 30 m. It plugs into:
- Use Territory Alerts on the alarm. The status line at the top of the ALERTS tab should read Alarm deployed, powered, flag raised — armed.
With a cord plugged in, the battery isn't drained, so you can leave one on as a backup.
There's no on/off switch. To move the alarm, unplug it and take the battery off, then pick it up and Place it somewhere else. It can't be picked up while either is connected.
No alarm, no alerts
A territory only raises alerts while a powered alarm stands inside it. Without one, nothing is sent: no popup, no Discord message and no siren. One powered alarm covers the whole circle. Extra alarms add sirens and spares.
Killing the alarm doesn't silence it:
- Shooting it, blowing it up, unplugging it or pulling its battery all raise an alert, even if the alarm then has no power. This alert can't be switched off.
- Grace period: a territory whose alarm just lost power keeps alerting for 5 minutes.
The siren
- Every powered alarm in the territory sounds when a raid starts, and again when it escalates (see How alerts arrive). It doesn't sound for updates or for the closing summary.
- It wails for 2 minutes and carries about 500 m. Everyone hears it, the raiders included.
- It draws the infected like a grenade going off, every few seconds for as long as it wails.
- It only sounds while the flag is up, except for critical alerts (see What triggers an alert), which sound it whatever the flag is doing.
- Cutting the power stops it.
- Owners can't turn the siren off.
Battery warnings
While an alarm runs on its battery, members get an in-game notice when:
- the battery drops to 20%,
- it goes flat, or is ruined,
- it's taken off, and the alarm has no cord.
These are maintenance notices. They don't sound the siren and don't count as a raid. They reach Discord without a ping, if a channel is set up.
Raid alerts
What triggers an alert
Alerts are for people who aren't members of the territory. Things that members and server admins do never alert.
| Event | Severity |
|---|---|
| Structure damaged: a fence, watchtower, wall or tent hit by a player | Warning |
| Structure destroyed: a panel shot off, blown off or sawn off, or a tent ruined | Critical |
| An explosion damages a structure | Critical |
| A part dismantled, or a structure folded into a kit | Warning |
| A code lock being sawn (each step), or cut open | Warning. Cut open is critical |
| A code lock destroyed by gunfire or explosives | Critical |
| A code lock opened, removed or changed | Warning |
| The flag lowered a step, or all the way (the last alert the territory sends) | Critical |
| The alarm attacked, destroyed, unplugged or its battery pulled | Critical, can't be switched off |
- Infected, animals, vehicles and the weather damaging your walls don't count. Explosions always count, because a charge can't be traced to whoever planted it.
- If an explosion or a collapse can't be traced to a player and one of your members is within 30 m of it, it's treated as their own work and doesn't alert. This doesn't apply to the flag or the alarm.
- Code lock alerts need the CodeLock mod on the server. Wrong code attempts aren't detected.
How alerts arrive
A raid is one conversation, not a flood:
- The first event sends an alert straight away and sounds the siren.
- Further events are collected. An update goes out at most once a minute, with a tally such as 3x structure damaged, 1x part dismantled.
- The first critical event of each kind skips the wait and goes out at once as an escalation, and restarts the siren if it has stopped. Later ones of the same kind join the tally, except that the alarm being attacked, a lock being cut open and the flag reaching the bottom always go out at once.
- After 10 minutes of quiet, a closing summary says how long the raid lasted and what happened.
A territory sends no more than 12 alerts an hour. After that, everything waits for the summary. Escalations and the summary still go out.
Where alerts go
| Channel | Who gets it | Setup |
|---|---|---|
| Siren | Everyone within about 500 m | Powered alarm, flag up |
| In-game popup and chat line | Every member who's online, anywhere on the map | On by default |
| Discord channel | Whoever reads the channel | The owner pastes a webhook URL. The server must have Discord delivery on |
| Discord DM | Each member who has linked their account and hasn't opted out | The server must run Discord delivery through its relay |
The popup reads like RAID — Hilltop with structure damaged at grid 042/089 underneath. The grid matches the in-game map's 100 m squares. Popups fade after a few seconds, but the same line stays in your chat.
Alert settings (owner)
Use Territory Alerts on the alarm, or open the ALERTS tab in the Manage Territory window. Changes save as you click.
The top of the tab says whether the alarm is armed and what's missing if it isn't, and whether Discord delivery is working.
| Setting | Default | What it does |
|---|---|---|
| Territory name | the code | What alerts call your base. Up to 24 letters, numbers and simple punctuation. Type default to go back to the code |
| Alerts enabled | On | Master switch for this territory |
| Triggers | All on | One switch per event in the table above, except the alarm tamper alert. Turning off Structure damaged doesn't turn off Structure destroyed |
| Session window | 600 s | Quiet time before a raid counts as over. 60 to 3600 |
| Minimum gap | 60 s | Shortest time between two alerts. 10 to 900 |
| Max alerts per hour | 12 | 1 to 120 |
| Notify online members | On | The in-game popup and chat line |
| DM me when raided | On | Your own Discord DMs |
| Discord DMs to members | On | DMs for the whole group |
| Discord webhook | Off | Post alerts to a channel |
| Webhook URL | empty | The channel's webhook. It must start with https://. Only its last few characters are ever shown. Type clear to remove it |
| Ping the channel on a raid | No ping | Click to cycle: No ping, @here (people online in the channel), @everyone (the whole Discord) |
SEND TEST ALERT sends a test through every channel that's set up: popups, the siren (if the alarm is armed) and Discord. It says Alert test rather than RAID, and doesn't count toward the hourly limit. Reopen the window to see whether Discord accepted it.
Members who aren't the owner see a single setting on the ALERTS tab: DM me when this territory is raided.
Discord DMs
For the bot to DM you:
- Type
/linkin the game chat. You get a code. - In the server's Discord, use
/link <code>. - Allow DMs from server members: in Discord, User Settings > Privacy & Safety, and the same switch in that server's privacy settings.
- Leave DM me when raided on (it's on when you join).
DMs need the server to run Discord delivery through its relay. If the ALERTS tab says Discord delivery is not set up on this server, only the in-game alerts and the siren work.
Troubleshooting
| Problem | What to do |
|---|---|
| Can't claim territory: This flag is too close to another claimed territory | Build the pole further away |
| You already own the maximum of 1 territory(ies) | You already own one |
| That code doesn't match this territory | Check the code with the owner. You must be at the right flag |
| You've been removed from this territory and can't rejoin | The owner kicked you. They can un-ban you from the MEMBERS tab |
| This territory is full | The territory has hit its member limit |
| Can't deploy the alarm, red hologram | You must be inside a territory you're a member of |
| Can't pick the alarm up | Unplug it and take the battery off first |
| No alarm deployed — alerts will NOT fire | Deploy an alarm inside the circle |
| Alarm has NO POWER — alerts will NOT fire | Plug it in, or fit a charged Truck Battery |
| …but the flag is DOWN | Alerts still go out, but the siren waits until the flag is raised |
| Webhook switched on — now set the URL below | Paste the webhook URL into the box and press SET |
| No DMs | Go through Discord DMs again. The most common cause is DMs from server members being blocked in Discord |
| Kick does nothing | Stand at the flag |