Permissions
MasuHolograms checks permission nodes through Forge's permission API, so a permissions mod such as LuckPerms can grant or deny them per player or group. Admin commands use the vanilla operator level.
Admin Commands
All /mh hologram, /mh line, /mh page, /mh feature, /mh list, /mh plist, /mh near, /mh stats, /mh help, /mh reload and /mh version commands require op level 2. There is no separate permission node for them.
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.editbook |
Use /mh editbook command |
true |
masuholograms.lectern.guide |
Use /mh guide command |
true |
Lectern Hologram Limits
Control how many lectern holograms each player can have in a world.
| Permission | Description | Default |
|---|---|---|
masuholograms.lectern.bypass |
Unlimited lectern holograms | op (level 2) |
masuholograms.lectern.limit.1 |
Max 1 lectern hologram | op (level 2) |
masuholograms.lectern.limit.2 |
Max 2 lectern holograms | op (level 2) |
| ... | ... | ... |
masuholograms.lectern.limit.20 |
Max 20 lectern holograms | op (level 2) |
"op (level 2)" means true for operators and false for everyone else unless a permissions mod sets the node, so operators have unlimited lectern holograms. See the "Without a permissions mod" warning at the end of this page.
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.<maxLimit>(20 by default) down tomasuholograms.lectern.limit.1. The first match becomes the player's limit - Default - if no limit permission matches, uses
defaultLimitfrom 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
Only players with the my.server.vip permission will see this hologram.
Line-Level Permission
Only players with my.server.admin will see line 3 on page 1. Other lines remain visible.
Clearing Permissions
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 and sends the player the noPermission message from lang.json.
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 withmasuholograms.to becomemasuholograms.vip
Info
Permission strings used on holograms, lines and PERMISSION actions work with LuckPerms without being registered first.
Without a permissions mod
Without a permissions mod, Forge's built-in handler answers every node with its default. The lectern.use, getbook, editbook and guide nodes are then true for everyone, while hologram and line permissions, PERMISSION actions and the limit and bypass nodes are true for operators (op level 2) and false for everyone else. Install a permissions mod such as LuckPerms to grant them to other players or groups.