Skip to content
BlogStart for free

Deployments

Use the server console and metrics

The deployment’s Console shows server output and, for authorized members on a running server, accepts commands. Use it while you test to connect a player action to what happened on the server.

  1. Open the running deployment and select Console.
  2. Wait for startup output and the live stream.
  3. Perform one test action in Minecraft.
  4. Check the corresponding log lines.
  5. Record the deployment/build number and relevant timestamp if behavior fails.

The console shows timestamps in UTC. Convert them to your local time zone when comparing them with your notes.

During provisioning, commands or metrics may not be available yet. Wait until the server is online before checking command or metric availability.

Use Search visible log output to locate a command, player name, warning, or exception. The search operates on visible/loaded output; it is not necessarily a search of every historical server log.

Use the controls to scroll to the next failure, jump to the top or bottom, and enter fullscreen. Expand grouped repeated lines when you need the full sequence.

If the visible excerpt is insufficient, use Download full server log. A downloadable captured log can be more useful for startup failures than the currently visible tail.

  1. Confirm the deployment is online and you have owner/editor access.
  2. Enter a supported Minecraft/server command in the console input.
  3. Submit it and inspect the response.
  4. Verify the resulting state in Minecraft or the dashboard.

In the console, omit the leading / unless the command requires it. Run the actual command names available in your project.

list
say Testing the new build now

A command from the console does not have the same sender or permissions as a normal player. Test player-only commands in the game as the relevant player role. Check that the plugin explains why a player-only command cannot run from the console.

The available quick actions can save worlds, enable/disable/reload the whitelist, and clear weather. Choose the action, wait for its result, and verify the changed state.

Use save before a restart when your test requires checking world persistence. Whitelist actions affect who may join; use the player controls for individual membership.

For a specific dimension’s weather or time, use Worlds so the intended scope is clear.

Metric How to use it
CPU Look for sustained load when triggering your feature.
RAM Watch usage while loading content and running repeated tests.
Disk Check whether stored world or runtime data is growing unexpectedly.
Player count Compare load with the number of connected testers.
TPS on Paper Check tick performance; 20 ticks per second is the normal target.

Metrics depend on the server and available telemetry. TPS is requested for Paper, not Vanilla or Fabric. An unavailable metric is not a zero reading and does not by itself identify a fault.

Compare performance before and after you use the feature. One brief CPU spike during startup is different from sustained load after every command.

  1. Reproduce the issue once with clear steps.
  2. Note the action and player role.
  3. Copy the exception and the first useful cause, including referenced files or classes.
  4. Download the full log if surrounding context matters.
  5. Return to the project chat and request a focused fix.
On deployment #<number>, artifact/build <identifier>, a normal player runs
<command/action>. Expected: <result>. Actual: <result>.
Console excerpt: <relevant error>.
Fix the cause while preserving the existing configuration and stored data.

Review the repair, rebuild, and deploy a new artifact. Repeating a failing command on the old server cannot test a source fix that has not been deployed.

Check status and remaining time. A stopped session can show saved output but cannot run commands. If the live connection drops, reopen the deployment and check its actual state before assuming the server stopped.

See support for help reporting startup, gameplay, and connection problems.

Not an official Minecraft product. Not approved by or associated with Mojang or Microsoft.