Deployments
Manage players and worlds for testing
Use Players and Worlds in the deployment dashboard to prepare repeatable gameplay tests. Management actions require owner or editor access and an appropriate running server state.
Inspect players
Section titled “Inspect players”- Open the deployment and select Players.
- Search for the player you want to inspect.
- Check online status, Minecraft identity, operator/whitelist/ban tags, and available gameplay details.
- Open the player’s actions for management controls.
Details can include gamemode, world/location, health/food, and experience level when the server can provide them. The server software, player status, and available telemetry determine which details you can view.
Configure the whitelist
Section titled “Configure the whitelist”The whitelist limits joining to allowed players when enabled.
- Check the dashboard’s Whitelist setting.
- Find the intended Minecraft player.
- Choose Add to whitelist.
- Confirm the player can connect with the correct account and version.
- Use Remove from whitelist when access is no longer required.
If changing the global whitelist setting, wait for the updated state. Enabling the whitelist and adding a specific player are separate actions. A player can also be blocked by a ban even when listed on the whitelist.
Use your exact Minecraft Java username in profile settings to help Buildryn resolve the correct UUID. Project roles govern Buildryn access; the whitelist governs game access.
Test as an operator and as a normal player
Section titled “Test as an operator and as a normal player”Use Set as operator to grant operator status and Remove operator to revoke it. Verify the tag changes before running the test.
Test ordinary commands as a non-operator first when that is the intended audience. An operator can pass permission checks that a normal player cannot, hiding a configuration bug.
For an administrator feature, also test that a normal player is denied and receives the requested explanation. Granting operator status for convenience is not a substitute for checking your plugin’s permission nodes.
Kick, ban, and unban
Section titled “Kick, ban, and unban”- Kick player disconnects a current player. They may reconnect if access otherwise permits it.
- Ban player blocks future access for that player.
- Remove ban reverses the ban; it does not automatically add the player to an enabled whitelist.
Read confirmations and verify the resulting state. These controls are useful when testing moderation features or access rules, but ensure your own testing account can still reconnect.
Reset one player’s data
Section titled “Reset one player’s data”- Record the player and test state you want to reset.
- Open their actions and choose Reset player data.
- Read and confirm the reset.
- Wait for completion, reconnect if disconnected, and check the initial state.
- Repeat the feature test.
Plugin-specific data may be stored separately from Minecraft’s player data. If your feature tracks first-join or cooldown state in a plugin file, use its documented reset command or configuration as well. Do not assume a player reset clears every plugin’s private storage.
Reset all player data
Section titled “Reset all player data”Use the per-player reset to reset each tester who needs a fresh state. Check separately for any data saved by the plugin, mod, or datapack.
Inspect worlds and dimensions
Section titled “Inspect worlds and dimensions”- Select Worlds.
- Search for the desired world.
- Inspect the dimension, player count, difficulty, time, and seed where available.
- Use that world’s actions to create the conditions you need.
Availability varies by server software. Wait for the dashboard to finish loading world data before checking the list.
Set weather and time
Section titled “Set weather and time”Use Clear weather, rain/thunder actions, Set day, or Set night where the selected dimension supports them. The actions operate in the selected world’s context.
For a feature activated at night or during rain, test both the triggering condition and the opposite condition. Check that the effect ends correctly when conditions change.
Test: set night → feature activates → set day → feature stops.Repeat with a second player and after a server restart.Build a repeatable test setup
Section titled “Build a repeatable test setup”Record the artifact, player role, whitelist state, dimension, time/weather, and any resets. Share those details with the next tester so they can repeat your setup.
Use console monitoring during tests.