Skip to content

Visibility & Range

MasuHolograms controls hologram visibility per-player based on distance, permissions, and enabled state.

Display Range

The maximum distance (in blocks) at which a player can see a hologram.

/mh hologram setdisplayrange myHolo 64
  • Default: 48 blocks (configurable in config.json)
  • Range: 1-256 blocks
  • Measured from the hologram's origin, in the same dimension only

When a player moves beyond the display range, the hologram's fake entities are removed from their client. When they move back within range, the entities are re-spawned.

Update Range

The maximum distance at which placeholders and animations update for a player.

/mh hologram setupdaterange myHolo 32
  • Default: 48 blocks (configurable in config.json)
  • Range: 1-256 blocks

Info

Setting update range lower than display range means distant players see the hologram but with static content. This can reduce server processing for holograms with many placeholders.

Update Interval

How often (in ticks) placeholders refresh for this hologram.

/mh hologram setupdateinterval myHolo 40
  • Default: 20 ticks (1 second)
  • Range: 1-1200 ticks
  • Animations advance on their own speed, regardless of this setting
  • Values below 1 in a hologram file are raised to 1 when it loads
Interval Frequency Use Case
1 Every tick (50ms) Real-time data (not recommended for most cases)
20 Every second Standard - good for most placeholders
100 Every 5 seconds Low-priority info (reduces load)
1200 Every minute Very static data that rarely changes

Visibility Checks

The server performs visibility checks every 20 ticks (1 second) for each player and hologram combination. The check evaluates:

  1. Is the hologram enabled? Disabled holograms are invisible
  2. Is the player in range? Same dimension and within the display range
  3. Does the player have permission? If a permission is set, the player must have it
  4. Show/hide state: if the player should see it but doesn't, spawn the entities; if they shouldn't see it but do, remove the entities

A player who joins is checked at once; after a respawn or dimension change, at the next check. Line permissions are re-checked on the hologram's update interval.

Permission-Based Visibility

Hologram Permission

/mh hologram setpermission myHolo my.server.vip

Only players with my.server.vip see the hologram. Permission changes are detected at the next visibility check (within a second). See Permissions for how permission strings are checked.

Line Permission

/mh line setpermission myHolo 1 3 my.server.admin

Only line 3 is hidden - other lines on the page remain visible.

Clearing Permissions

/mh hologram setpermission myHolo
/mh line setpermission myHolo 1 3

Omit the permission argument to make it visible to everyone again.

Enable/Disable

/mh hologram enable myHolo
/mh hologram disable myHolo

Disabled holograms retain all their data but are completely invisible. Use this for maintenance or seasonal holograms.

Teleport Visibility Update

By default, teleporting does not trigger an immediate visibility recheck. Enable this in config.json:

{
  "updateVisibilityOnTeleport": true
}

When enabled, a player who moved far within one tick (a teleport) gets the visibility check on the next tick, so holograms near the destination show at once instead of within a second.