Configure Rust Backpacks permissions and preserve stored items

~~CloudExa~~The ~~help~~uMod ~~guide.~~Backpacks plugin adds persistent inventory space with its own permissions and rules. Treat its stored contents as player property. Enabling a button, changing capacity and deciding what happens on death are separate configuration choices.

Protect the existing storage

Record the Backpacks version and preserve its configuration and complete plugin data directory. Include the active world and related inventory integrations in a consistent backup before major changes. Arrange a normal stop if necessary to copy state reliably. Keep the backup outside the live server, with its version and date recorded.

Inspect the current configuration rather than assuming an older tutorial matches. Modern capacity permissions and profiles differ from some legacy row-based examples. Do not delete a data directory to force the plugin to recreate it; that can remove the items you are trying to protect.

Enable a limited trial

Grant the base use permission to one verified account through the trusted server console:

oxide.grant user STEAM64 backpacks.use

The player can then try /backpack. The optional GUI button uses the separate backpacks.gui permission. Enable it only if that is part of your intended interface. A missing button does not by itself mean backpack storage is unavailable.

Check capacity and retention rules

Read the configured default size and registered permission sizes for the installed version. Grant only a capacity permission that actually exists in that configuration. Inspect all the player's groups if the resulting capacity differs from your expectation. Avoid experimental dynamic-size features while establishing a reliable baseline.

Review the configured death and wipe policies before placing valuable items inside. A keep-on-death exception is not the same as keeping items across a map wipe. Do not change those policies globally just to debug one player's access. Communicate the actual rules before players rely on the storage.

Verify with disposable items

Place a small, counted set of inexpensive items in the test backpack.
Close and reopen it, then reconnect and check the quantity.
Move the items back to ordinary inventory and confirm nothing duplicated or disappeared.
During a planned maintenance window, verify persistence after a normal save and restart.
If testing death behaviour, use a consenting test account and disposable inventory under controlled conditions.

Do not trigger a map wipe to test retention. Keep the live world's lifecycle unchanged. Features such as automatic gathering and retrieval add other requirements and interactions; leave them disabled until basic storage works.

Recover carefully

If a capacity reduction would leave occupied slots outside the new limit, stop and plan a supported migration with sufficient ordinary storage. Do not assume the plugin will safely dispose of excess contents. Restore the retained configuration if needed while preserving current player data.

Provide support with the plugin version, affected Steam64 ID privately, assigned permissions and relevant redacted errors. Never run erase or wipe commands to investigate a display problem. Where recovery requires restoring inventory data, coordinate it to avoid overwriting legitimate items acquired since the backup.