Resolve conflicting HuskHomes home limits across ranks

Applies to: HuskHomes; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

A player can inherit several home allowances through donor, staff and temporary groups. Changing the number in the main configuration may appear ineffective because an explicit numeric permission takes precedence. Check the effective allowance before touching any stored home.

Before you change settings

Record the player’s normal groups, context and existing home count. Choose a test account with the same memberships and no operator status. Save the relevant permission-group definitions; the home database is not the setting being repaired.

Follow the request through the plugin

Inspect effective permissions for the affected account using your permission manager. Look for every granted huskhomes.max_homes. numeric node, including inherited and contextual entries.
Compare the result with the installed HuskHomes configuration. The documented default selects the largest applicable allowance; enabling general.stack_permission_limits changes how numeric home limits combine.
Choose one deliberate policy: a total allowance for each rank, or additive allowances with stacking enabled. Remove only a redundant allowance grant after confirming other groups do not depend on it.
Test permission evaluation in the same world and server where the complaint occurred. Use a new harmless home name only if the test account has capacity; record whether the next home is permitted or refused.

Confirm the intended result

The ordinary test account should receive the intended total, and its existing home list should remain intact. Repeat after reconnecting and after removing any temporary rank. A successful administrator test alone does not show that a member’s inherited limit is correct.

If the test fails

An unexpected larger total usually means another applicable node remains or stacking is active. A smaller total can indicate a missing context or a negative permission. Changing limits is not a reason to delete homes that already exist above the new allowance.

Restore the saved permission definitions if access becomes inconsistent. Preserve the home records and ask support to inspect effective permissions with the player, world and time of the failed check.

Give a LuckPerms permission an expiry without leaving permanent access

Make a LuckPerms event rank expire while preserving other ranks

Limit a LuckPerms command permission to one Minecraft world

Keep a LuckPerms permission local to one network backend

Move a player along a LuckPerms track without replacing unrelated groups

Fix a LuckPerms prefix priority without changing chat formatting

Remove a direct LuckPerms exception without weakening its parent rank

Apply a small LuckPerms web-editor session to the correct server

Export LuckPerms data before changing its storage configuration

Find an inheritance cycle before it complicates a rank change

Keep default-player permissions separate from staff inheritance

Diagnose LuckPerms edits that reach one backend but not another

Check a player UUID before changing LuckPerms account data

Remove a staff member from one LuckPerms track without clearing their account

Give an EssentialsX rank a fixed home limit

Restrict one EssentialsX warp to an approved player group

Test EssentialsX teleport delay and movement cancellation

Add an EssentialsX cooldown to one utility command

Resolve an EssentialsX command alias conflict without removing either plugin

Check EssentialsX AFK kick exemptions for a staff role

Limit EssentialsX nickname changes without granting formatting control

Give staff a read-only EssentialsX player-information role

Recover from an accidental EssentialsX ignore setting

Restrict EssentialsX repair commands to the intended tool policy

Review EssentialsX command-disabled entries after a plugin change

Test an EssentialsX jail location without trapping a real player

Change the EssentialsX starting balance for new players only

Set EssentialsX maximum and minimum money limits with a boundary test

Change the EssentialsX currency symbol without changing stored money

Test an EssentialsX pay dispute using two controlled accounts

Review EssentialsX worth prices before enabling item selling

Explain an EssentialsX balance leaderboard that looks out of date

Trace an unexpected EssentialsX command charge

Back up EssentialsX money before a player-data migration

Verify a LiteBans temporary ban expires at the intended time

Test whether a LiteBans mute covers a private-message command

Build a LiteBans appeal-review role without punishment access

Check a LiteBans moderator’s maximum punishment duration

Find which plugin handled a ban command on a mixed-plugin server

Verify the server scope of a LiteBans network punishment

Investigate a LiteBans database connection failure without losing history

Reverse one appealed LiteBans punishment while preserving the audit trail

Test an AdvancedBan time layout before staff use it

Check AdvancedBan warnings without accidentally escalating a real player

Give an AdvancedBan helper access to history without ban powers

Check AdvancedBan storage before changing from local files to MySQL

Lift one AdvancedBan restriction after an approved appeal

Locate AdvancedBan correctly on a proxy network

Test SuperVanish visibility with separate staff and player accounts

Check whether a vanished SuperVanish moderator can pick up items

Verify flight is safe when a SuperVanish moderator reappears

Check silent chest inspection without changing container contents

Find a SuperVanish join or player-list information leak

Remove vanish access from a staff role without leaving a hidden account

Check PremiumVanish layered visibility after changing staff ranks

Verify PremiumVanish network vanish across Velocity backends

Check vanished staff interactions before a live investigation

Recognize the PremiumVanish API jar before installing an integration

Give GrimAC alerts to one observer without granting exemptions

Remove a GrimAC exemption and verify when checks resume

Collect a GrimAC prediction log for a false-positive report