File Details
AdministratorControl-V3.0.0.mcaddon
- R
- Apr 2, 2026
- 171.57 KB
- 444
- 26.10+22
File Name
AdministratorControl-V3.0.0.mcaddon
Supported Versions
- 26.10
- 26.3
- 26.0.02
- 26.0
- 1.21.132
- 1.21.131
- 1.21.130
- 1.21.124
- 1.21.123
- 1.21.122
- 1.21.121
- 1.21.120
- 1.21.114
- 1.21.111
- 1.21.101
- 1.21.100
- 1.21.94
- 1.21.93
- 1.21.92
- 1.21.90
- 1.21.82
- 1.21.81
- 1.21.80
Changelog 3.0.0
- Added permanent saved owner support using world dynamic properties
- Updated owner data storage to include player xuid for better owner protection and matching
- Added owner sync so the saved owner can keep or regain the admin_owner tag
- Added owner transfer support with optional old owner tag removal
- Added Owner Player Management to the Owner Menu
- Added saved player history using world dynamic properties
- Added automatic player history saving when players join
- Added banned players storage using world dynamic properties
- Added ban player menu that can show saved offline and online players
- Added unban player menu for removing players from the banned list
- Added banned players list viewer
- Added saved players list viewer
- Added automatic banned player enforcement on join by kicking the player automatically
- Added repeating banned player checks while players are online
- Added owner protection so the saved owner cannot be banned
- Added self protection so the owner cannot ban themselves
- Added extra ban confirmation safety checks before saving a ban
- Confirmed player history and banned player data persist through reloads because they are stored in world dynamics
- Tested and confirmed bans keep kicking players after they join back
- Started spectator chest viewing system work
- Tested an on-screen spectator chest overlay approach
- Changed the design from overlay viewer to custom spectator chest form viewer
- Updated the spectator viewer plan so the viewer opens while looking at a chest in spectator mode
- Cleaned the chest viewer down to a single active system
- Built a Chest Admin Viewer for container contents
- Added Delete Slot option to remove individual chest slots
- Added Clear Chest option to wipe the full container
- Added Refresh option to reload the chest contents
- Added Spectator Chest View ON/OFF toggle in the OP Tools menu
- Made the spectator chest viewer toggle use a player dynamic property so each admin can control it for themselves
- Added double sneak support in Spectator mode to open the admin menu
- Updated spectator mode messaging to tell admins they can double sneak to open the admin menu
- Kept the spectator chest system and admin menu access working for owner admins, OP admins, and basic admins based on their existing permission routing
How the Ban System Works
- Every time a player joins, their player name and xuid are saved into a world dynamic player history list
- This saved player history allows the Owner Player Management menu to show both online and offline players
- The ban system stores banned players in a separate world dynamic list
- When the owner bans a player, the script saves that player’s name and xuid into the banned players list
- When the owner unbans a player, that player’s entry is removed from the banned players list
- The system checks banned players by both player name and xuid for safer matching
- The script also protects the saved owner and the current owner from being added to the banned list
- On every player join, the script checks whether the joining player is in the banned list
- If the player matches a banned entry, the script attempts to kick them from the server
- The script also keeps checking online players in the repeating system loop so banned players continue to be removed if needed
- Because the player history and ban list are both stored in world dynamic properties, they stay saved through reloads and server restarts
How Player Info Is Saved
- Player info is saved in world dynamic properties, not only in temporary script memory
- The saved player history stores:
- player name
- player xuid
- last seen timestamp, which is used to display how long ago the player was last seen
- The banned players list stores:
- player name
- player xuid
- who banned them
- when they were banned
- Since world dynamic properties are used, the saved player list and banned player list remain stored even after the world reloads or the server restarts
How the Spectator Chest Viewer Works
- While in Spectator mode, an admin can look at a container block and open the Chest Admin Viewer
- The spectator chest viewer can be turned ON or OFF from the OP Tools menu
- The chest viewer toggle is saved per player using a player dynamic property
- The Chest Admin Viewer now shows the full chest contents in one UI instead of splitting it into pages
- The viewer shows the block type, block location, and all chest slots in one form
- The viewer includes Delete Slot, Clear Chest, Refresh, and Close options
- Delete Slot opens a menu showing filled slots only, so one slot can be removed at a time
- Clear Chest asks for confirmation before wiping the whole container
- Refresh reloads the chest contents so the admin can re-check the container without reopening everything manually
How Spectator Menu Access Works
- Admins can still use the admin system while in Spectator mode
- Double sneaking in Spectator mode opens the admin menu for admins with permission to use it
- This works for players that already qualify under the script’s admin checks
- Owner admins still get their owner-capable menu flow
- OP admins still get their normal admin menu flow
- Basic admins still get their basic admin menu flow

