Minecraft Admin Guide

This guide is for server administrators managing the GameDirector mod on Minecraft.

Admin Commands

These commands require operator status or specific permission levels.

Command	Permission	Description
/marketloc	Level 2	Sets the teleport destination for the /market command to your current location.
/bounty create	Admin	(If enabled) Create a new bounty for the server.

Configuration Options

GameDirector is configured via the gamedirector-server.toml file located in the world/serverconfig directory.

Feature Flags

You can enable or disable specific systems under the [features] section:

• global_chat: Overrides vanilla chat formatting and XP rewards.
• integration: Master switch for external Ignition services.
• commands: Enables or disables all GameDirector-specific commands.
• join_leave: Custom join/leave messages and first-join tracking.
• tab_list: Custom tab list formatting.
• bounties: Automatic bounty tracking.
• shops: Sign shop interactions and ownership tracking.
• ticks: Periodic systems like playtime rewards and level benefits.

Integration Settings

• socket_server: Controls the inbound socket server for receiving data from Ignition.
• incoming: Toggle specific inbound packet types (chat, cmd, poll, etc.).
• outgoing: Toggle specific outbound notifications (kills, payments, market logs).

Troubleshooting

Database Connection

GameDirector requires a connection to the Miralis MySQL database. If the connection fails:

1. Check the credentials in the source code or config (if exposed).
2. Ensure the MySQL server is running and accessible from the Minecraft server.
3. Check the server logs for "Connection to Miralis Database Successful".

Socket Server Issues

If Ignition cannot communicate with the Minecraft server:

1. Ensure the gdPort in the miralis.servertracking database table matches the port the server is listening on.
2. Check for firewall rules blocking the GameDirector port.

Sign Shops Not Working

• Ensure features.shops.enabled and features.shops.sign_interactions are set to true.
• Verify that the player is integrated with Discord.
• Check if the sign owner data is being correctly inserted into the signowner table.