Hosting manual

The manual for EE Icarus Server Core 1.15.2.

Priority

If you have used WorldGuard, you know that its regions can overlap and that it needs priorities to decide which region wins. Claims here never overlap, so there is nothing to decide between two claims. What this page explains instead is the order in which the mod decides whether to stop a particular player doing a particular thing.

Claims never overlap

Every claim has a one-metre buffer around it, and two buffers may touch but never overlap. So any spot on the ground is inside at most one claim, and only that claim's switches apply there. If you try to make a claim too close to another one, the command refuses and tells you which claim is in the way.

The order of the checks

When a player hits something, places something, uses something or takes a step inside a claim, the mod asks four questions in this order and stops at the first one that settles it:

  1. Does this player hold the bypass, and is it on? The owner and the admins hold it. If it is on, nothing stops them and nothing puts them out, whatever the switch's audience says. That includes the damage switch, so an admin with the bypass on can take down a building inside any claim a player holds. On a claim held by the server, such as the Norex Landing Zone, this question is skipped: the bypass does nothing there, and the owner and the admins go through the other questions like any other member of the server.
  2. Is the claim active? Only an active claim, or one in its grace period, is enforced. A claim that has gone into reserve is loaded but ignored.
  3. Is the switch on? Each switch is on or off for this claim, within what the owner allows.
  4. Is this player in the switch's audience? A switch set to strangers does not stop a member; a switch set to everyone stops the holder too. A claim held by the server has no holder here, and the owner and the admins count as its members only if they are on its member list. A hit on a building or a deployable while damage is off skips this question: it is stopped for everyone, the holder and the members included. The pvp, mobs and weather switches are not asked about buildings at all.

Turning your bypass off

An admin who wants to play the game properly, under the same claims as everyone else, types /claim bypass off. For the rest of that visit their hits are judged like a visitor's, and a claim that is closed to visitors puts them out like anyone else. /claim bypass on restores it, and so does logging out and back in. Under Claim settings, the owner can make "off" the starting state for every bypass holder. On a claim held by the server it makes no difference either way.

Note

The bypass also lets its holder ignore the size and count limits when making a claim. That part is separate: turning the bypass off in the game does not bring the limits back, because the privilege itself has not changed.

When a different world is loaded

A claim belongs to the world it was made on. If the server loads a different prospect, the claims on the old one are kept, but they are not enforced and not charged until that world is loaded again.