Hosting manual

The manual for EE Icarus Server Core 1.15.2.

Claim commands

This page goes through every /claim command in turn, with what it does and what it answers. The Commands page has the same commands as a one-line table, if you just want to look one up. Where this page says "managers", it means the server's owner and admins.

Selecting ground

You mark the ground you want before you claim it. /claim pos1 and /claim pos2 each set one corner of a rectangle where you are standing, rounded outward to a whole metre. If you would rather not walk the corners, /claim sel <w>x<d> makes a rectangle of that width and depth in metres, centred on you.

/claim sel on its own shows you the selection you have, with its size and what it would cost a day. /claim sel clear forgets it.

/claim select <id> makes an existing claim's area your selection, which is how you start resizing a claim. If you leave the name out, it uses the claim you are standing in; if you are not standing in one, it answers "You are not in a claim; /claim select <id> names one."

Making and changing claims

/claim name <id> claims your selection under that name. The server answers at once with something like "Requested: home, 30 by 30 m, 900 m², 1.8 Ren a day.", and a few seconds later the portal confirms with "Claim home made: 30 by 30 m, 900 m², 1.8 Ren a day." /claim name on its own answers Type /claim name <id> to make a claim.

Because the word name comes first, the name can be any word, even one that is also a command: /claim name list makes a claim called list, and /claim info list then shows it.

Claims used to be made with /claim <id>, without the word name. For now that form makes no claim and answers with a reminder, such as "Type /claim name home to make a claim." If a claim of that name already exists, the reminder says so and points you at /claim info for it.

/claim redefine <id> moves or resizes the claim to your current selection, under the same limits as a new claim.

/claim remove <id> ends your own claim. The Ren in its account comes back to you first, as Ren items in your backpack, and then the claim ends. You are told "Requested: remove kolb. Every whole Ren in its account comes back to you first as Ren items in your backpack, and anything under one Ren is forfeit." If the Ren cannot all reach you, because your backpack is full or you have left the world, the claim is not ended: what did not arrive stays in its account, and you can type the command again once there is room. A claim that owes Ren is ended with nothing to pay back.

/claim handover <id> <player> gives the claim to a player who is online, exactly as it stands. You answer "Requested: hand kolb to Foggy." and then "Claim kolb handed to Foggy.", and Foggy is told as well. You stay on the claim as a member.

Managers have two more. /claim define <id> <player> claims the manager's selection with an online player as its holder, and /claim end <id> <reason> ends anyone's claim with a short reason that goes into the record. It answers "Claim kolb ended."

Looking at claims

/claim info shows you the claim you are standing in. /claim info <id> shows the one you name. Either way you see its name, its holder, its members, its size, which switches are on, and whether it tells its holder who comes and goes. If it is your claim, you also see how much Ren is in its account, how many days that covers, and what will happen next. You are also told how many doors, chests and other objects have a level of their own ("3 objects have their own access level."), and which zones the claim has, each with its level ("Zones: counter (manager)."). With more than three zones it gives their number and points you at /claim zone list. On a claim held by the server, its managers are told these two things. Either one is left out when there is none. On a server that uses the on-screen notice, this answer comes up in the game's confirmation box, which you click away; otherwise it comes in chat like everything else.

On a claim held by the server, the holder is the faction and the answer lists the managers who look after it, for example "LZ, held by Norex; administrators: Dave, Foggy; members: none; ...". The server only knows the names of the managers who are online, so the others are counted: "Dave and 2 more administrators". There is never a balance, because such a claim has no account.

/claim info <id> select shows the claim and then selects its area for you.

/claim list lists your claims on this world, and tells you how many you hold on other worlds. A manager sees everyone's claims, and /claim list <player> shows a manager the claims of a player who is online.

/claim show puts up the outline of the claim you are standing in, the same orange bars you see while you select, and leaves it up. /claim show <id> does the same for the claim you name. If you are not standing in a claim and leave the name out, it shows your own claim; if you hold more than one, it lists them and asks you which. The server answers "Showing kolb's outline. /claim hide takes it down." The outline stays until you type /claim hide, leave the server, the claim ends, the server restarts, claims are turned off on the server, or the world changes.

You can have several outlines up at once. Each /claim show adds one and leaves the others where they are. If the claim you name already has its outline up, the server tells you so and changes nothing.

/claim hide takes all your outlines down and names each one: "Took down kolb's and dock's outlines." /claim hide <id> takes down only the one you name. If you have none up, /claim hide answers "Nothing shown."

Each outline is twelve bars, and your outlines count toward the 150 markers the server draws for any one player, along with the markers for your selection. That is room for twelve outlines. If one more would not fit, /claim show names it and asks you to make room: "dock's outline does not fit beside the 12 you have up; /claim hide one first." Your outlines are drawn first, so with many of them up there may be no room left for your selection's markers.

Switches and lines

/claim flag <id> <switch> on|off, with an optional audience word after it, turns one of the claim's switches on or off. The Switches page explains them all. The server answers "Requested: kolb, PvP blocked." and the portal confirms "kolb: PvP blocked." A switch the owner does not allow is refused with the reason.

/claim flag <id> greeting <text> sets the line people see when they walk into your claim, and farewell <text> the line when they walk out. Up to 200 characters, kept exactly as you type them. The word on its own, with no text, puts the server's own line back. The portal answers "kolb: enter line set."

/claim flag <id> notify on means you, and any managers who are online, are told "Foggy walked into kolb." and "Foggy left kolb." whenever someone crosses the edge. notify off turns it off again.

Doors and chests

While use or containers is blocked in your claim, strangers cannot open its doors or its chests. You can open one of them up, or lock one down tighter, without changing the switch for the whole claim, because each door, chest, bench or bed can carry its own level.

Say you want visitors to come in through your front door, but not through the door to your storeroom. Stand inside your claim, open the front door once, and then, within a minute, type:

/claim access everyone

Requested: Door Wood in kolb at everyone.

The server names the object by its kind, so a wooden door is "Door Wood". A few seconds later the portal confirms the change. From then on anyone can open that one door, and every other door in the claim still follows the use switch.

The command always works on the last thing you used, so use the object first and type the command straight after. If you have not used anything in the last minute, the server asks you to use the object first.

These are the levels, from the most open to the most closed. The server's owner and admins pass every one of them except a group level:

Level Who can use the object
everyone anyone at all
member the claim's members: you, your members and the members of your groups
user the server's members: anyone with the user role or above, on your claim or not
manager the server's owner and admins
owner the server's owner alone
g:<group> the members of that server group alone, by its name on the Groups page; you and the managers are shut out too unless you are in the group, and only the bypass passes

So a player who is not on your claim can open an object at everyone, one at user if they are a member of the server, and one at g:<group> if they are in that group. The bypass still lets the owner and the admins through, whatever the level says.

A claim held by the server is the exception. There the owner and the admins are treated like any other member of the server, and their bypass does nothing, on or off. They pass everyone and user, and member or g:<group> only if they are on the claim or in the group. Nobody passes manager or owner there, so an object at either stays shut until someone gives it another level.

/claim access on its own tells you the level of the last thing you used and what it means. Anyone can ask, so a visitor who is refused can find out why. /claim access clear puts the object back to the claim's normal rule. Only the holder and the managers can set or clear a level.

A level only counts while its switch is blocking: a door's while use is blocked, and a chest's while containers is blocked. A level never lets anyone pick the object up, which still follows the claim's normal rule. Creatures, and items lying on the ground, have no level.

Where the levels are kept

Levels may not be on yet on your server. Until the portal turns them on, setting one answers "Object levels are not on for kolb yet; the portal turns them on.", and every door and chest follows the claim's switch as it always has.

Once they are on, the portal keeps every level with its claim, and the claim's page on the portal lists them, each with a Clear button for the holder and the managers. The page does not set levels: you set them in game, by using the object. A level is tied to the object's kind and to where it stands, so it survives a restart, but if you pick the object up and put it down somewhere else, it comes back with no level. Deleting a server group on the portal clears every level that names that group.

Zones

A zone is a box inside your claim that only some people may stand in. It has a level of its own, one of the levels doors and chests use, and anyone below that level who walks, jumps or falls into the box is put straight back out. It works whether or not the rest of the claim is open to visitors.

The shop counter is the example. The Trading Post, a claim called shop here, has three kitchen corner benches in a row, and they are its counter: staff work behind them and customers stand in front. To stop customers jumping the counter:

  1. Stand on the floor at the front corner of the first bench, as close to it as you can get, and type /claim zone pos1.
  2. Walk to the back corner of the last bench and type /claim zone pos2.

    Zone corner 2 set at 1629.5, 1925.4 m: 3 by 0.9 m, 3 m tall.

  3. The zone runs 3 metres up from the floor where you typed pos1. That is one storey of the building grid, so with the benches on a floor it reaches the floor above. For another height, type /claim zone height <m> before the next step, for example /claim zone height 2.5.

  4. Type /claim zone make counter manager.

    Requested: zone counter in shop at manager, 3 by 0.9 m and 3 m tall.

A few seconds later the portal confirms it. From then on nobody can stand on the benches or anywhere in the box above them. That includes the owner and the admins, because shop is held by the server, where neither their role nor their bypass gets them past a level. A customer who jumps the counter from the front lands on it and is put back where they stood, in front, and told "counter in shop: not for you."

Someone who comes in through a side goes back to where they last stood outside. Someone who was already inside when the zone appeared, who logged in there, or who dropped into it from above, goes out through the nearest side. A zone lower than a standing player can also lift them out over its top. A player on a mount is judged at the height the mount carries them, and goes out with the mount.

The zone ends a hand's width inside where you stood: 25 cm in from your corners on every side. A customer who stands right against the counter stands about where you stood, so they are not moved for leaning on it. It also means your corners need to be at least a metre apart each way. Past that there is no rounding to whole metres. The zone only reaches from the floor you stood on to its height, so a player upstairs, on the floor above the counter, is not touched, and neither is anyone on the floor below. It never reaches past its claim either: if the claim is made smaller, the part of a zone left outside it stops counting.

The portal keeps every zone with its claim, and the claim's page lists them, each with a Remove button for the holder and the managers. Zones are made in game; the page does not make them. Deleting a server group on the portal removes every zone at that group's level. If the claim is made so small that a zone lies wholly outside it, the zone stops counting and the server forgets it, so /claim zone remove no longer finds it; the claim's page marks it as outside the claim, and Remove there takes it away. Until it is removed its name stays taken, and it counts again if the claim grows back over it.

Pick the level with care. A zone's level lets in the same people as a door's, from the table above, so on your own claim a zone at manager keeps you out too unless you are a manager, while member lets in you, your members, the members of your groups, and the owner and the admins. The bypass still lets the owner and the admins through a group level. On a claim held by the server, a zone at manager or owner keeps everyone out, and the bypass lets nobody through.

/claim zone list shows the zones of the claim you are standing in, with their levels and sizes. Anyone can ask. /claim zone remove <name> takes one away. /claim show draws each zone as a smaller outline of its own inside the claim's, standing on the zone's own box.

Only the holder and the managers can make or remove a zone, and on a claim held by the server any manager can. Zones need the portal's side too: until the portal turns them on for a claim, make answers "Zones are not on for shop yet; the portal turns them on."

Clearing ground

/claim raze <id> clears the site: every plant, rock and tree inside a claim, so you can build on clean ground. That means bushes, rocks and trees, and also ferns, saplings, seedlings, cacti, the breakable rocks, and the sticks and loose stones lying about. Only burnt trees are left, and loose items lying on the ground (a lump of coal, say), because raze cannot tell the world's own from something a player dropped.

Raze also clears the ore deposits: the big mineable rocks that give coal, copper, salt and the like. A claim has no height, so raze takes everything above and below it too, the ore deposits in a cave under the claim included.

Stand inside the claim and type:

/claim raze kolb

Razed kolb: removed 14 bushes, 3 rocks, 2 trees and 9 other plants.

There is no ask and no confirm: the one word clears the whole claim. On a big claim the first part goes at once and the rest follows on its own over a few seconds, and you are told when it is done:

Razing kolb: removed 40 bushes and 20 rocks so far, and the rest of the claim follows on its own within about 10 seconds; you will be told when it is done.

Razed kolb: removed 142 bushes, 31 rocks, 6 trees and 88 other plants in all. Of these, 2 other plants will not come back through resource respawn.

An ore deposit is cleared only when nobody has mined any of it. Raze looks at each one twice, a little over ten seconds apart, and clears it only if nothing about it changed in between. So the ore deposits go a few seconds after the plants, and the closing line counts them:

Razed kolb: removed 142 bushes, 31 rocks, 6 trees, 88 other plants and 4 ore deposits in all.

An ore deposit that Resource respawn has brought back is looked at a full minute apart, so a claim with one of those takes about a minute to finish. A deposit that someone has been mining is left standing, and the answer says so:

2 ore deposits were left standing, since someone has been mining them or they could not be checked.

Raze used to ask first and wait for /claim raze kolb confirm. A confirm typed after the name out of habit is accepted and changes nothing: the claim is razed once.

A razed tree leaves no stump, unlike a felled one.

Only the holder and the managers can raze, and on a claim held by the server any manager can. You have to stand inside the claim, because raze only clears ground near a player. Anything further from every player is left alone and counted in the answer. A plant counts as inside when it grows inside the claim's edge, so a bush that only leans over the line from next door is left alone.

While a raze of a claim is running, typing it again says it is already running. You can run one raze at a time: a raze of another claim is refused until yours is done, so type it again then. The raze stops early if the claim ends, claims are turned off or the world changes, and tells you what it removed. If you leave the server, it stops too, without a word.

What comes back

What you raze comes back through Resource respawn like anything gathered, after its usual time, unless something has been built on its spot by then. So clear the ground, then build. That covers the bushes, rocks and trees (the loose stones count as rocks here), and the other plants: wild crops and fibre (flax, jute, kiwi and the like), saplings, seedlings, sticks, cacti and ferns. Each kind comes back only while its box is ticked on the Settings page, under Resource respawn.

Razed ore deposits come back the same way. They count as rocks: they need the Rocks box, they take the usual time for rocks, and one does not come back while something is built on its spot. One thing is different for now. A razed ore deposit comes back only after the server has restarted at least once since you razed it, and the answer tells you:

The ore deposits come back with resource respawn once the server has restarted.

Only razed ore deposits come back. One that a player mines out by hand stays gone, as it always has.

Two things do not come back through Resource respawn: the breakable rocks (scoria, clay, obsidian, permafrost and cobalt), which never do, and any kind whose box is off on your server. The answer always says what will not come back. The game also regrows the sticks on its own, within about an hour on a test server, and may regrow some saplings, seedlings and cacti; Resource respawn leaves a plant the game has already put back alone.

On a server that has just been updated, the other plants start coming back after its next restart; until then the answer says they will not.

Raze works whether or not Resource respawn is on. With it off, nothing you raze comes back through it, and the answer says so. Razed ore deposits are remembered all the same, so they come back if Resource respawn is turned on later.

Resource respawn can only remember so many razed ore deposits at a time. If its list is full, raze leaves the rest of the ore deposits standing and says so; raze the claim again a minute later.

Teleport and spawn points

Stand inside your claim, on the ground, and type /claim flag <id> teleport here to set its teleport point there. /claim flag <id> teleport on its own removes it. The same two forms with spawn set and remove the claim's spawn point, which is where a member who dies inside the claim comes back to life. It suits an arena: whoever falls inside comes back at the same spot.

Your own spawn point

You can also have a spawn point of your own, which catches your death anywhere on the map, not only inside a claim, and comes before your bed. Stand on the ground inside a claim you hold or are a member of, and type:

/claim spawn here

Your spawn point is set at 1629, 1925 m in kolb. A death anywhere brings you back here, ahead of your bed.

You have one. Typing it again somewhere else moves it, and /claim spawn on its own clears it, so you come back at your bed again, or at a drop point if you have no bed.

When you die, the server looks in this order:

  1. If you died inside a claim that has a claim spawn point for you, you come back at that point.
  2. Otherwise, if you have a spawn point of your own and it still counts, you come back there.
  3. Otherwise the game's own rule: your bed, or a drop point.

Your own point stops counting while its claim is in grace or reserved, once the claim has ended, once you are no longer its holder or a member, and once the claim has been changed so that it no longer covers the spot. You come back at your bed then, and the server tells you why once, in chat. It counts again if things change back, since the point is kept, except after the claim has ended: then the point is removed once you have been told. You cannot set one in a claim that is in grace or reserved. On a claim held by the server for a faction, such as the Norex Landing Zone, only the claim's listed members can set one there. Other server members cannot, and that includes the owner and the admins unless they are on the list.

If a point's claim has ended and you do not come back within a week, the point is removed without a word, so you will find no point set the next time you look.

/claim teleport <id> moves you to the claim's teleport point straight away, facing the way you were facing, and says "You are at kolb." You, your members, the managers and the admins can use it, once every 30 seconds. If the claim is closed to visitors, a manager who is not a member is refused. If you are dead, in the dropship, sitting down, on a mount, on a ladder, in a trap or still loading in, you are told why and you stay where you are.

Members

/claim addmember <id> <player> makes a player a member of your claim, and removemember takes them off again. The player has to be online, and you use their name as the game shows it. If nobody of that name is online, the answer is "No player called X is online." You are never a member of your own claim; you are its holder.

/claim addmember <id> g:<group> and removemember <id> g:<group> do the same for a whole server group, by its name on the portal's Groups page. Everyone in the group is a member of the claim for as long as they stay in the group. Someone who is on the claim only through a group cannot be removed by name; the answer is "Foggy is on kolb through the group Builders.", and you would take the group off instead.

/claim removemember <id> all takes every member and every group off in one go. If there is nobody to take off, it answers "kolb has no members."

Ren

/claim deposit <id> <ren> moves Ren from your account into the claim's account, in steps of 15, while you are in the world. /claim withdraw <id> <ren> takes whole Ren back out; they arrive as Ren items in your backpack, and an Orbital Exchange Interface sends them up to your account. /claim withdraw <id> all takes out every whole Ren at once and leaves anything under one Ren in the account. The Claiming page explains how the money works.

A claim held by the server costs nothing to keep and has no account, so both commands answer "Norex's claim has no account." for it, whoever types them.

/ren balance tells you how much Ren your account holds, for example "Your account holds 1,230 Ren." If the server's copy of your balance is out of date, it asks you to try again in a few seconds.

The bypass

/claim bypass tells an owner or admin whether their bypass is on. /claim bypass off and on set it for the rest of the visit. Anyone else who types it is told "You do not hold the claims bypass."

The bypass does nothing on a claim held by the server. There the owner and the admins are treated like any other member of the server, on or off. To get at something there, change its level, its zone or the claim's switch instead.

Why a command might refuse you

What it says What it means
Claims are off on this server. The owner has not turned claims on.
Claims are not loaded on this server yet; try again in a minute. The server has just started. Wait a minute.
Your role cannot hold a claim on this server. You are a guest. Ask the owner to change your role.
One claim command every 10 seconds. You typed two claim-changing commands too close together.
The claim's balance is less than 1 Ren, so there is nothing to withdraw. You typed /claim withdraw <id> all on a claim with less than one Ren in its account, or one that owes Ren.
The balance of X is above 100,000 Ren, the most one withdrawal moves; withdraw some of it first with /claim withdraw X <ren>. One withdrawal moves 100,000 Ren at most, so withdraw <id> all and remove both stop here. Take some out by number first, then type the command again.
Use the object first (open the door or the chest), then type /claim access within a minute. /claim access works on the last thing you used, and you have not used anything in the last minute.
The raze of X is already running; you will be told when it is done. You typed the raze again while it was still clearing the claim. Wait for the closing line.
Your raze of X is still running; raze Y once it is done. You can run one raze at a time.
Object levels are not on for X yet; the portal turns them on. The portal has not turned object levels on for that claim yet. Nothing about the claim has changed.
Object levels start working at the server's next restart. The server is still running the older mod for doors and chests. It picks the new one up when it restarts.
Set the zone's corners first: /claim zone pos1 and /claim zone pos2. You typed /claim zone make without both corners, or more than ten minutes after you set them.
Both corners of a zone must be inside the same claim. One of your corners is outside the claim, or in another one.
Zones are not on for X yet; the portal turns them on. The portal has not turned zones on for that claim yet.
Type /claim name <id> to make a claim. You left out the word name, or the name after it. Nothing was made.
That area is within 2 m of the claim X; claims keep 2 m apart. Your selection is too close to another claim.
Your Steam id could not be read; try again in a moment. The server has not matched you to your Steam account yet. It usually sorts itself out in a few seconds.