Skip to main content
Use this tutorial after you connect a server with the PLUGIN method.

Choose the matching artifact

Download the current JAR for your runtime from Downloads. Choose Minecraft, then the file that matches your runtime:
  • Spigot, Paper and Folia (gamecart-spigot)
  • BungeeCord (gamecart-bungeecord)
  • Velocity (gamecart-velocity)
  • Fabric 1.21.4, 1.21.11, or 26.1
Integrations > Servers also links to Downloads. For Fabric, install the matching Fabric API line as well:
  • gamecart-fabric-1.21.4: Fabric Loader 0.19.3+ and Fabric API 0.119.4+1.21.4
  • gamecart-fabric-1.21.11: Fabric Loader 0.19.3+ and Fabric API 0.141.4+1.21.11
  • gamecart-fabric-26.1: Fabric Loader 0.19.3+ and Fabric API 0.145.1+26.1

Install and configure the executor

  1. Copy exactly one matching JAR into plugins/, or into mods/ for Fabric.
  2. Start the server or proxy once to generate its configuration.
  3. For Fabric, open config/gamecart.properties. For plugin and proxy runtimes, open the configuration in the platform data folder.
  4. Set your server token and restart the runtime.
Copy the server token from Integrations > Servers. Keep it secret.
Minecraft server connection row with its masked token highlighted

Use the masked token from the exact Minecraft connection you are configuring.

Set pollIntervalSeconds to a value from 5 through 600. Unless you are testing on loopback, apiUrl must use HTTPS. With debug=true, the executor logs sanitized state and status information. It does not log tokens, commands, player identifiers, HTTP bodies, buyer data, or order data.

Understand where commands run

Spigot, Paper, Purpur, Folia, and Fabric run commands on the local server console. BungeeCord and Velocity run them on the proxy console and do not automatically forward them to backend servers. Folia support covers the Gamecart adapter. It does not guarantee that arbitrary third-party commands are safe on Folia.

Operate the executor

Run gamecart status to check whether the executor is connected. After you edit its configuration, run gamecart reload to apply it. If the executor can’t reach Gamecart, it keeps retrying on its own and waits up to a minute between attempts. When Gamecart is reachable again, it reconnects without a reload. The console logs one line when the connection drops and another when it comes back. If it keeps retrying with a 401 or 403 error, Gamecart is rejecting the server token. Check serverToken and apiUrl in the configuration, then run gamecart reload.
If a command ran on your server but Gamecart never received the confirmation, resending it can deliver the purchase twice. Check the outcome in the Gamecart dashboard before you resend.