Permission Reference
Home Limit Priority
When LiricHomes calculates how many homes a player is allowed to create, it checks permissions in the following order and stops at the first match:liric.homes.bypass— if the player holds this node, they have unlimited homes (internally treated as 999).liric.homes.vip.<N>— LiricHomes scans allliric.homes.vip.*nodes the player holds and uses the highest number found. This means you can safely assign multiple tiers to a player and the largest limit always wins.default-home-limitinconfig.yml— the server-wide fallback for players who hold novipnode.
Home limit permissions are only evaluated when
home-backend: PLUGIN is set in config.yml. In ESSENTIALS mode, limits are controlled by EssentialsX’s own essentials.sethome.multiple.<group> permission system.Dynamic Home Limits with liric.homes.vip.<N>
The <N> suffix is a plain integer — there are no predefined group names. Any number you put there becomes the limit for players who hold that node. Common examples:
Because LiricHomes always selects the highest value, you do not need to remove a lower-tier node before assigning a higher one.
Setting Limits with LuckPerms
Use the following commands to assign a home limit to an individual player or a group:Admin Permission Notes
liric.adminhomes.use grants access to all /adminhomes subcommands, including reload and settings. If you want to allow trusted moderators to manage homes but not touch backups or run migrations, grant liric.adminhomes.use while keeping liric.adminhomes.backup and liric.adminhomes.migrate restricted to administrators.