Permissions

MasuHolograms uses a flexible permission system that integrates with LuckPerms when available. Without LuckPerms, permissions fall back to operator status (op level 2).

Admin Permissions

Admin commands require op level 2 by default. With LuckPerms, you can grant these to non-op players.

Permission	Description	Default
`masuholograms.admin`	Access to all admin commands	Op only

All /mh hologram, /mh line, /mh page, /mh feature, /mh list, /mh plist, /mh reload, and /mh version commands require admin permission.

Player Permissions

These permissions default to true — all players have them unless explicitly denied.

Permission	Description	Default
`masuholograms.lectern.use`	Place hologram books in lecterns	`true`
`masuholograms.lectern.getbook`	Use `/mh getbook` command	`true`
`masuholograms.lectern.guide`	Use `/mh guide` command	`true`

Lectern Hologram Limits

Control how many lectern holograms each player can create.

Permission	Description	Default
`masuholograms.lectern.bypass`	Unlimited lectern holograms	`false`
`masuholograms.lectern.limit.1`	Max 1 lectern hologram	`false`
`masuholograms.lectern.limit.2`	Max 2 lectern holograms	`false`
...	...	...
`masuholograms.lectern.limit.20`	Max 20 lectern holograms	`false`

How Limit Resolution Works

When a player places a hologram book, the limit is resolved in this order:

Bypass check — if the player has masuholograms.lectern.bypass, they have unlimited holograms
Limit scan — scans from masuholograms.lectern.limit.20 down to masuholograms.lectern.limit.1. The first match becomes the player's limit
Default — if no limit permission matches, uses defaultLimit from config (default: 3)

LuckPerms Examples

# Give a player 5 lectern holograms
/lp user Steve permission set masuholograms.lectern.limit.5 true

# Give a group unlimited holograms
/lp group vip permission set masuholograms.lectern.bypass true

# Deny a player from creating lectern holograms
/lp user Griefer permission set masuholograms.lectern.use false

Hologram View Permissions

You can set a permission on any hologram or individual line to control who can see it.

Hologram-Level Permission

/mh hologram setpermission vip_hologram my.server.vip

Only players with the my.server.vip permission will see this hologram.

Line-Level Permission

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

Only players with my.server.admin will see line 3 on page 1. Other lines remain visible.

Clearing Permissions

/mh hologram setpermission vip_hologram
/mh line setpermission my_hologram 1 3

Omitting the permission argument clears it, making the hologram/line visible to everyone.

Click Action Permissions

Use the PERMISSION action type to gate click actions:

/mh page addaction myHolo 1 RIGHT PERMISSION:my.server.vip
/mh page addaction myHolo 1 RIGHT MESSAGE:&aWelcome, VIP!

The message only shows if the player has the my.server.vip permission. The PERMISSION action stops the action chain if the check fails.

Permission String Format

MasuHolograms accepts permission strings in two formats:

Dotted notation (e.g., mymod.feature.vip) — the first segment is treated as the mod ID, the rest as the node name
Single word (e.g., vip) — automatically prefixed with masuholograms. to become masuholograms.vip

Info

Dynamic permission strings (like those used on holograms and lines) work with LuckPerms without needing to be pre-registered. The mod bypasses Forge's permission registration system and queries LuckPerms directly.