Cartcord Minecraft and Rust agents - setup preview Availability The protocol-1 control plane and plugins are a verification preview. New game product activation requires Cartcord's server acceptance gate, a recent agent heartbeat, verified game account linking and an active Pro-or-higher store plan. Installing a plugin, checking an acknowledgement or copying a command example does not enable game sales. No FiveM or Roblox payment integration is included. Server requirements Minecraft: Java 21 and Paper 1.21.8 API compatibility. Direct online-mode=true authentication is required; offline-mode/proxy forwarding is not accepted by this first agent. LuckPerms is needed for group delivery. Item delivery uses Bukkit inventory APIs and requires the target player to be online with room. The JAR is built for this API; other versions/mod combinations need validation. Rust: a compatible Rust dedicated server with Oxide/uMod. The preview source was reference-compiled against Oxide 2.0.7839 and current server assemblies. Strict Steam authentication (server.strictauth_steam true) is required. This is a source plugin: put CartcordRust.cs in oxide/plugins on your own test server. It has not been certified against a running owner game server in this release. Owner setup Open your Cartcord store dashboard, Integrations, Game server delivery (preview). Review the platform rules, confirm server ownership, then create a connection. Keep its endpoint, connection ID and one-time agent secret in the private plugin configuration. Never put the secret in a product, Discord ticket or public repo. The endpoint must be the exact HTTPS Supabase game-agent URL supplied by setup. No RCON, panel or SSH password is collected. Each store supports one active connection per game; do not share one connection between different game servers. Minecraft configuration is plugins/CartcordMinecraft/config.yml. Set endpoint, connection-id, agent-secret, owned-server-policy-acknowledged and allowed-roots. Rust generates oxide/config/CartcordRust.json with the corresponding Endpoint, ConnectionId, AgentSecret, OwnedServerPolicyAcknowledged and AllowedRoots keys. Group roots are enabled by default. Opt into give/minecraft:give (Minecraft) or inventory.giveto (Rust) locally before configuring item products. Retain and back up the private execution journal together with game-world/player data. Product configuration After server acceptance, choose an existing positive-price manual product in the same store. Enter its product ID in the game panel and configure only the supported recipes below. Publish the correct game-server address, version, requirements, contents and support process in the product description. Minecraft group: lp user {player_id} parent add vip Minecraft revoke: lp user {player_id} parent remove vip Minecraft item: give {player_id} minecraft:stone 1 Rust group: oxide.usergroup add {player_id} vip Rust revoke: oxide.usergroup remove {player_id} vip Rust item: inventory.giveto {player_id} wood 100 Commands are fixed recipes, not an unrestricted remote console. The player ID comes from a verified link, never a buyer's text field. At most five recipes are supported per action. Groups must exist. The private server's local root allowlist and current capabilities must also permit the selected action. Revocation may remove only a group granted by that product. Consumed items cannot be recalled. Optional 60-second to 365-day group access is a one-time payment, not a recurring subscription. The duration starts when execution is authorized; delayed/partial executions need support review. Free claims and unreleased Stripe/crypto payment modes are not game fulfillment methods. Buyer account linking Open Your purchases, Game accounts, choose the store, sign in with the same Discord account used for purchase, and review the trust acknowledgement. Copy the private link command and run it from your own player account on that store's game server. Codes expire after five minutes and work once. Refresh the Cartcord page to verify the linked UUID/Steam ID. Never share the code. Checkout requires an available accepted connector and this identity binding. Delivery and recovery Only a positive, verified live PayPal order matching its saved payment log is eligible. Configuration and player identity are frozen in the checkout record. The agent pulls store-scoped work; the backend never connects to arbitrary customer RCON endpoints. A lease is not delivery. The agent requests a separate start authorization, persists a local journal and acknowledges actual API work. Items wait for an online player and inventory room. Permission/partial command failures or an uncertain response go to review, not a blind side-effect retry. Expiry/full-refund group revocations use the original order and game identity. Minecraft ranks use per-order LuckPerms contexts, preserving unrelated and overlapping ranks. Rust tracks pre-existing groups and active managed orders; reconcile any manual changes to managed Rust groups before resolving jobs. An execution journal is not an atomic transaction with a game's world save. Rust item state may depend on world saves; process/power-loss inventory and permission behavior requires real-server tests and a support recovery policy. The preview does not promise exactly-once or atomic multi-command execution. Keep clocks synchronized. A stopped/offline agent stops new game checkout readiness and can delay refund revocation. Minecraft expiry nodes and Rust's local managed-group expiry help while the plugin is running; disabling it is not a substitute for reconciliation. Disconnecting invalidates its secret and stops work; automatic product bindings continue to block new checkout. Inspect dashboard game jobs and the preserved server journal before resolving uncertain effects. Only an unstarted job may be automatically requeued. Record verified completion or arrange manual fulfillment when effects are uncertain. Platform requirements https://www.minecraft.net/en-us/usage-guidelines https://facepunch.com/legal/servers A store acknowledgement does not replace platform monetization requirements, content ownership, DLC permissions, buyer rights or applicable obligations.