SquareMarkers

Players can create named areas without using commands.

1. Create one banner for every corner of the area.
2. Make sure all banners use the same base color.
3. Give every banner exactly the same name using an anvil.
4. Place a lodestone at each corner.
5. Place one of the named banners directly on top of every lodestone.
6. The area will automatically appear on squaremap.

Area behavior:

• The placement order does not matter.
• Only the outermost points are used to draw the area.
• Points inside the outer boundary are ignored when calculating its shape.
• Points can be added or removed at any time.
• Two aligned points create a circle.
• Two non-aligned points create a rectangle.
• Three or more points create an automatically calculated outer boundary.
• The default maximum area size is 512 blocks and can be changed in the
    configuration.

The banner name and base color identify which points belong to the same area.

Configure in-game area feedback independently for entering, leaving and staying inside a player-created area:

settings:
  feedback:
    area-on-enter: ActionBar # None, ActionBar, Title, Subtitle
    area-on-leave: ActionBar # None, ActionBar, Title, Subtitle
    area-presence: None      # None, ActionBar, BossBar

Travel through a Nether portal, End portals or End gateways to register it automatically.
  
When portal/gateway renaming is enabled, a renamed name tag can be used on a portal/gateway to give its marker a custom name.

Portal popups include a button for navigating to the corresponding Overworld, Nether or End coordinates on squaremap.

Set `only-show-named: true` to only show named Nether portal, End portal and End gateway on the web map.

Beacon markers are created automatically after a placed beacon becomes active.
The marker is removed when the beacon is destroyed.

1. Place a lodestone.
2. Place a sign directly on top of it.
3. Add text to the sign.
4. The sign and its text will appear on squaremap.

Editing the sign updates its marker. Removing the sign or lodestone removes the
marker.

End portals and End gateways are detected automatically and displayed on the
map.

No commands or manual configuration are required.

Lightning strikes are temporarily displayed on squaremap.

The marker lifetime can be configured in seconds.

SquareMarkers can show:

• Players in the Nether on the Overworld map
• Players in the Overworld on the Nether map

Coordinates are automatically converted using the standard 8:1
Overworld-to-Nether scale.

Spectators, invisible players, and players hidden through squaremap are not
displayed.

When Open Parties and Claims is installed, claimed chunks are automatically combined into colored claim areas.

Claim markers update when chunks are claimed, unclaimed, or changed. Claim names and colors are taken from Open Parties and Claims.

Main claims and individual subclaims remain separate, even when their names and colors match. Subclaims use their effective OPAC name and color, including inheritance from the main configuration.

This integration can be disabled independently in the SquareMarkers configuration.

Warp markers are displayed automatically after they are created.

The marker is removed when the warp location is deleted

Currently warps of Fabric Essentials, HuskHomes and Essential Commands are supported.

Important for HuskHomes: squaremap layers are visible to all map viewers. 
If you use permission-restricted warps whose locations must stay private, set `marker-settings.huskhomes-warps.enabled` to `false`; squaremap cannot apply per-player warp permissions here.

Waystones markers are displayed automatically after they are created.

The marker is removed when the waystone location is deleted, you can enable sharestones and undiscovered stones in the config file.

  waystones:
    enabled: true
    priority: 50
    include-sharestones: true
    include-undiscovered: false

Waystones by BlayTheNinth is supported.

Enable this to show the last death of each player on mapped worlds. The lifetime is in seconds (1–604800), defaulting to 30 minutes and can be set in the config file.

  deaths:
    enabled: false
    priority: 50
    # Marker lifetime in seconds.
    lifetime: 1800
    # UTC, Europe/Brussels, Europe/London, or a fixed offset such as UTC+01:00.
    timezone: UTC

Important: death markers are public, including for players hidden from squaremap’s live-player layer. Disable this feature or hide their death marker if required.

When World Border by Serilum is installed, SquareMarkers displays its enabled boundaries in a separate World Border (Serilum) layer.

Rectangular and off-center bounds are supported in the vanilla Overworld, Nether and End, matching the dimensions supported by that mod.

squaremap’s separate vanilla worldborder layer is left unchanged. If you only want the mod’s outline, disable the vanilla layer in squaremap’s config yourself.

marker-settings:
  world-border:
    enabled: true
    priority: 50
    # Loaded config checks in seconds, range 5-3600.
    refresh-interval: 30

/squaremarkers status
/squaremarkers status details
/squaremarkers marker list
/squaremarkers marker list “minecraft:overworld” nether_portals
/squaremarkers marker hide “minecraft:overworld” nether_portals “100:64:200”
/squaremarkers marker show “minecraft:overworld” nether_portals “100:64:200”

Status is a compact, color-coded summary: green for enabled/visible, yellow for disabled/hidden, and dark gray for not installed. `status details` shows individual integrations and layer counts per world.

These are console/gamemaster commands. Hiding only removes the marker from the public map, not its source object, and takes effect on squaremap’s next update.

The 19 player-feedback and 7 map-text templates are configurable under the root `messages` section. 
Customize marker creation/removal/rename/color messages, area-point messages, area entry/exit text and sign-marker feedback. 
Defaults are English, and missing templates are added without replacing existing settings.

messages:
  marker:
    add: “Added {type} marker”
    rename: “Renamed {type} marker to ‘{name}'”
    interact: “{name}”
    rename-failed: “Could not rename {type} marker”
    color: “Colored {type} marker”
    color-failed: “Could not color {type} marker”
    remove: “Removed {type} marker”
  area:
    create: “Created area: {label}”
    point-add: “Added point to area: {label}”
    point-add-failed: “Could not add point to area: {label}”
    remove: “Removed area: {label}”
    point-remove: “Removed point from area: {label}”
    enter: “[+] {name}”
    leave: “[-] {name}”
    presence: “{name}”
  sign:
    invalid-text: “Text should be a String array with a size of 4”
    add: “Added sign marker”
    edit: “Edited sign marker”
    remove: “Removed sign marker”

`{type}` represents a marker type, `{name}` its name or an entered/left area’s name, and `{label}` an area label for point operations. 
Text is plain text with the existing feedback colors.
Set a template to `””` to suppress that message; sound settings remain separate. 
Quote values containing `:` or `#` and reload with `/squaremarkers reload`. 

Death-marker text and portal button labels can also be translated in the web map:

messages:
  death:
    title: “{name}’s last death”
    position: “Position: {x}, {y}, {z}”
    time: “Time of death ({timezone}): {time}”
  portal:
    go-to-end: “Go to The End”
    go-to-nether: “Go to Nether”
    go-to-overworld: “Go to Overworld”
    go-to-end-gateway: “Go to End Gateway”

`{name}` is the player name; `{x}`, `{y}`, `{z}` are death coordinates.
`{timezone}` and `{time}` follow the configured death timezone. 
Empty death templates hide their line. These map texts apply independently of in-game feedback settings.

Area names support a limited and sanitized selection of HTML:

<b>Bold</b>
<i>Italic</i>
<u>Underlined</u>
<br>
<span style=”color: #RRGGBB;”>Colored text</span>

Unsafe HTML and scripts are escaped before being sent to the web map.