Test keepInventory death handling before allowing server transfers

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

HuskSync gives special treatment to death snapshots and players who change servers while dead. With keepInventory, dropped-item assumptions can conflict with retained items. The maintainer documents a specific configuration and additional care for custom partial-retention plugins.

Record the starting point

Use a disposable account with counted low-value items and record keepInventory behaviour on each participating backend. Save the current HuskSync configuration and test-account snapshot. Check the server requirement for the documented ITEMS_TO_KEEP mode before changing it.

Work through the change

Read the current keep-inventory guidance and inspect synchronization.save_on_death. The documented arrangement uses ITEMS_TO_KEEP with save_empty_items and sync_dead_players_changing_server enabled; confirm it matches the installed release and supported Paper version.
Test a normal death and respawn on one backend. Compare inventory counts and the resulting snapshot before involving a server transfer.
Repeat a controlled death-screen disconnect and join the other backend through the normal route. Check the final alive state and inventory, then return to the first backend.
If a custom plugin keeps only selected items, review its supported HuskSync integration with its maintainer. A general keepInventory setting may not represent that plugin's item transformation.

Check the result

The test account should retain exactly the intended items with no extra death drops or duplicate recovery state. Record both the same-server and cross-server results. A successful ordinary respawn does not prove that changing servers while dead is safe.

If the result differs

If counts differ, stop the trial and compare snapshot contents, event ordering and the custom death plugin. The maintainer notes that advanced partial-retention setups may require a dedicated API hook. Avoid compensating items repeatedly while the source of duplication remains active.

Restore the saved test configuration if the change regresses death handling and recover only the disposable account's required state. Keep affected transfer behaviour restricted until verified. Do not delete all player snapshots or reset inventories to conceal an inconsistent test.

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