Content generated with AI — it may contain mistakes.

ExyliaClans/GuidesguideUpdated in v1.4.0

Tune deaths till raidable

Deaths till raidable: the pool, the freeze, the regeneration tick, and what going below zero opens up.

Page 8 of 294 min read

Set how hard it is for a clan to lose its land: deaths take DTR away, it regenerates on a timer, and a clan below zero is raidable, so its claim stops protecting it.

Before you start#

DTR only matters if clans can claim land. The dtr module must be on (it is by default), see Turn clan systems on and off.

Steps#

Pick the settings

Open plugins/ExyliaClans/config.yml and find the dtr section. The main knobs are death-loss (DTR lost per member death, shipped 0.9), frozen-duration-seconds (how long regeneration is paused after a death, shipped 600) and members-per-point (members needed per 1.0 of maximum DTR, shipped 3).

Exempt worlds where dying should be free

Add the lobby, event or practice world to no-loss-worlds, for example no-loss-worlds: [lobby]. A death there costs nothing.

Reload

Run /clanadmin reload.

Check that it works#

Let a member of a test clan die in a normal world. The clan is told who died and where its DTR stands, green at maximum, yellow below it and red below zero. Look at the clan's DTR and state in /clan (clan info). Wait a regeneration tick and the DTR rises once the freeze is over.

How it works#

  • Maximum: max(1.0, members ÷ members-per-point). With 3 per point a three-member clan has 1.0, a nine-member clan 3.0 and a thirty-member clan 10.0. A small clan never gets less than 1.0.
  • Loss: each member death costs death-loss (0.9) and freezes regeneration for ten minutes. A death during the freeze restarts it. The floor is min-dtr (-1.0).
  • Regeneration: every regen-interval-seconds (45 s) a clan that is not frozen and not at maximum gains regen-amount (0.1). Undoing one death takes about seventeen minutes with the defaults: ten of freeze, then nine ticks.
StateWhenDefault colour
NORMALDTR is at the maximum&a
REGENERATINGAbove zero but below the maximum&e
FROZENThe freeze from the last death has not run out&b
RAIDABLEDTR below zero and the freeze is over&c

Colours use the colour codes of ExyliaLib.

Going further#

What happens when a clan goes raidable#

When DTR crosses from zero or above to below zero, once:

  • The clan loses 50 EXP (levels.exp-actions.raided.exp-loss), see Levels.
  • Its claim stops protecting anything, see Claim land.

Crossing back above zero restores protection on the next regeneration tick.

What DTR blocks#

A clan whose state is not NORMAL cannot /clan disband or /clan unclaim, and /clan reclaim is refused while it is raidable. A clan cannot drop or dissolve its land to escape a raid it is losing.

Change a clan's DTR by hand#

Run /clanadmin setdtr <clan> <SET|ADD|REMOVE> <value>. It is clamped at the clan's current maximum, but has no lower clamp: SET -50 goes straight through, past min-dtr. It also clears the freeze.

Setting DTR by hand does not tell WorldGuard

Un-raiding a clan with setdtr does not reopen the protection: with protection-mode: WORLDGUARD a region opened by a raid keeps its BUILD=ALLOW until the next restart. With BUILTIN there is nothing to undo.

Turn it off#

With modules.dtr: false there is no regeneration, freeze, death broadcast or raidable state, which means no claim ever opens. Territory becomes permanent and disband and unclaim lose their DTR check. If your server has claims it almost certainly wants DTR too.

Technical details
yaml
dtr:
  no-loss-worlds: []
  death-loss: 0.9
  members-per-point: 3
  frozen-duration-seconds: 600
  regen-amount: 0.1
  regen-interval-seconds: 45
  min-dtr: -1.0
  color-normal: "&a"
  color-regenerating: "&e"
  color-frozen: "&b"
  color-raidable: "&c"

On a network every server runs the regeneration task, but each clan's row remembers when it last regenerated, so a clan gains regen-amount once per interval whatever the number of servers. A clan left above a new, lower maximum (after losing members) is brought down to it on the next tick it is not frozen for.

FROZEN is checked first, so a clan pushed negative reads FROZEN for the ten minutes before RAIDABLE, although its claim is already open: that depends on the number being below zero, not the label.

On every start with the module on, each clan sitting at exactly 0.0 with no freeze is set to its maximum and the count is logged. It catches clans created while the module was off, but it also tops up a clan you deliberately left at 0.0 with /clanadmin setdtr.

Something missing on this page? Tell us on Discord