Control public HuskHomes listings without deleting private homes

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

A total home allowance and a public listing allowance solve different problems. Increasing one does not necessarily increase the other. Check publication permissions and limits before treating an inability to publish a destination as a missing or damaged home.

Before you change settings

Ask the player which existing home they want to publish and confirm that its coordinates are suitable for public visitors. Record current privacy states and numeric permissions. Use a test home away from private builds when checking the visitor experience.

Follow the request through the plugin

Inspect huskhomes.max_public_homes. numeric grants separately from total home allowances. Check inherited group limits and the configured stacking policy rather than changing every allowance together.
Confirm that the member has the documented home-edit and privacy permissions. The ability to create a home does not prove that every edit subcommand is available.
In game, use /edithome with the home name and the documented privacy action to change only the chosen test home. List public homes from another ordinary account.
Visit the new public listing with that second account and check the destination. Then return the test home to private and confirm it no longer appears as an available public destination.

Confirm the intended result

The public list should change for the selected home while other private homes stay private and remain in the owner’s personal list. Record how the public allowance is counted after reversing the test so the player understands which entries occupy a public slot.

If the test fails

If publication fails despite spare total capacity, recheck the public allowance and privacy permission. If the entry appears to the owner but not a visitor, distinguish the owner’s personal list from the shared public list before changing data.

Restore the test home’s original privacy and the saved numeric grants. Avoid deleting and recreating homes to free a listing slot; that can lose descriptions, ownership context and the original location while leaving the underlying policy unresolved.

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