PrivateChest: Administration, Cleanup, and Container Limits

Maintaining balance on a multiplayer server requires controls over how many containers players can secure, alongside administrative maintenance utilities. PrivateChest provides configuration tools for staff and a tiered permission structure for container quotas.

Administrative Maintenance and Bypasses

Server operators and staff members are granted privatechest.admin, which allows bypassing player container locks and running administrative upkeep tasks. When modifying settings or updating localization phrases, administrators apply changes on the fly using /privatechest reload or the shorthand /pc reload.

Over time, player bases can accumulate orphaned records from removed blocks or departed users. Staff can clean up stale entries from the storage database by executing /clearchests. This purges invalid container references and keeps storage records streamlined without affecting legitimate active locks.

Configuring Tiered Container Limits

To prevent players from hoarding excessive protected storage blocks, administrators can enforce tiered allowances through permission nodes. By default, lock limits are set to false until granted to specific groups.

For general container protection, servers can grant privatechest.limit.unlimited for unrestricted locking, or restrict players to defined thresholds such as privatechest.limit.100, privatechest.limit.50, or privatechest.limit.25. Furthermore, quotas can be assigned per container type. Server owners can allocate privatechest.limit.chest.unlimited or privatechest.limit.chest.50 for standard chests, privatechest.limit.barrel.unlimited for barrels, and privatechest.limit.shulker_box.unlimited to govern portable shulker storage independently.