🚸Signs

An overview of signs that can be used in AT.

AdvancedTeleport has a feature that allows players to set up signs that carry out different functions.

Setting up signs

To set up signs, you need to have permission to create those signs. For the majority of cases, this is at.admin.sign.<type>.create, e.g. at.admin.sign.warp.create.

Then, you are able to place a sign of any type. On the first line, type the sign you want, e.g. [Warps]. If the sign was successfully made, the first line of text should turn a blue and bold colour. Otherwise, the text will not change at all, and the sign will not respond when clicked.

Using signs

In order to use signs, players will need a permission to

Sign Types

[Warps]

The [Warps] sign simply runs the /warps command on players' behalf to show what warps they can teleport to. It is only set up by having [Warps] on the first line.

• Permission to create: at.admin.sign.warps.create

• Permission to use: at.member.warps.use-sign

• Required feature: use-warps

An example of the [Warps] sign.

[Warp]

The [Warp] sign teleports the player who clicks it to the specified warp. On the first line is the [Warp] identifier, but on the second line is the warp name, e.g. MySpecialWarp, with it being case-sensitive.

The player also needs an extra permission, at.member.warp.sign.<warp> (e.g. at.member.warp.sign.myspecialwarp), but this is often provided by default via at.member.warp.sign.*.

Note how the warp name in the permission at.member.warp.sign.myspecialwarp is all in lowercase, despite its name having some uppercase characters - if you add the permission with uppercase characters, then the permission will not work/be picked up.

• Permission to create: at.admin.sign.warp.create

• Permission to use: at.member.warp.use-sign and at.member.warp.sign.<name>

• Required feature: use-warps

An example of the [Warp] sign.

[Spawn]

The [Spawn] sign teleports the player to either a specified spawnpoint, or the resulting spawnpoint that is selected for the player.

If the second line is empty, then the spawn is selected just like how /spawn would run. For more information on how the destination of this is chosen, check the spawnpoints page.

If a spawn or world name is specified on the second line, then the spawn is selected just like how /spawn [ID] would run.

• Permission to create: at.admin.sign.spawn.create

• Permission to use: at.member.spawn.use-sign

• Required feature: use-spawns

[RandomTP]

The [RandomTP] sign teleports the player to a random location in the world. If there is a world specified on the second line, then the player is teleported to that world.

• Permission to create: at.admin.sign.randomtp.create

• Permission to use: at.member.randomtp.use-sign

• Required feature: use-randomtp

[Bed]

The [Bed] sign teleports the player to their bed. Costs, warm-ups and cooldowns are taken into account when the player interacts with the sign. If the player does not have a bed home, then the sign does not respond.

• Permission to create: at.admin.sign.bed.create

• Permission to use: at.member.bed.use-sign

• Required feature: use-homes

[Home]

The [Home] sign teleports the player to their main home. If the player has no main home but has several normal homes, then the sign picks the first one to send the player to. If the player has no homes, the sign does not respond.

Unlike signs such as [Warp] and [RandomTP], there is no second line specified for this sign.

• Permission to create: at.admin.sign.home.create

• Permission to use: at.member.home.use-sign

• Required feature: use-homes

[Homes]