Debug Commands

Debug commands are powerful tools designed for testing and resolving issues. To prevent accidental use, these commands are hidden and disabled by default.

Enabling Debug Mode

Before you can use these commands, you must enable debug mode in your config.yml. This toggle acts as a safety gate for advanced administrative operations.

# Enabling debug mode allows administrators to access advanced troubleshooting commands.
debug: true

# Enables profiling for TNT Run events to measure execution time.
# Recommended for identifying lag or slow external plugins.
event-profiling:
  enabled: true
  # If enabled, logs every event execution with timing details to the console.
  verbose: false

Timer Command

Administrators with the tntrun.debug.timer permission can manually override the active game timer. This is particularly useful during testing to skip long waiting periods.

If used without an arena name, the command targets the arena you are currently in. Providing an arena name allows you to adjust the timer for a specific match remotely.

/tntrun debug timer [arena] <time>

Example

/tntrun debug timer factory 60

Join Command

Administrators with the tntrun.debug.join permission can use this powerful command to instantly set up a test environment. Unlike the standard join command, this version bypasses the usual waiting phases and allows you to simulate a full game scenario with specific players.

When executed, it forces test joins into the specified arena. You can optionally bring other players with you by using the players flag.

/tntrun debug join <arena> [--players=p1,p2,...]

Options

--players=name1,name2: Automatically pulls the specified online players into the arena with you.

Example

/tntrun debug join factory --players=mrdespi,mSquid_

Component Command

Administrators with the tntrun.debug.component permission can use this command to preview chat formatting and component parsing in real-time. Instead of constantly reloading configuration files to see how a message looks, you can test colors, hex codes, and placeholders directly in-game.

The plugin will parse direct MiniMessage input using its internal chat manager and send the resulting component back to you, exactly as it would appear in a game message or announcement. You can also use the --path flag to preview a message from messages.yml. If the configured message is a list, every line in that list will be parsed and sent.

/tntrun debug component [message] [--path=message.path]

Example

/tntrun debug component <gradient:red:gold>Test Message!</gradient>
/tntrun debug component --path=you-eliminated

Dump Command

Administrators with the tntrun.debug.dump permission can generate a comprehensive performance report of the plugin’s internal events. This command is directly tied to the Event Profiling system in the config.yml.

When executed, the plugin will send a timings report to the sender, detailing how long various event listeners took to process. This is the primary tool for diagnosing “server lag” or identifying conflicts with slow external plugins.

/tntrun debug dump

Details

Prerequisite: event-profiling must be enabled in config.yml for meaningful data.