Game configuration examples
Review protocols, plugins, player IDs, and configuration requirements for Minecraft, ARK, Rust, and other games.
Last updated:
Check before configuring
The Agent sends commands using Source-compatible RCON, except for Rust, which uses WebRCON (WebSocket). A game appearing in a selector does not establish protocol or plugin compatibility. These are configuration examples, not a list verified against every real environment.
| Check | What to confirm |
|---|---|
| Protocol | Source-compatible RCON support (WebRCON for Rust) |
| Server and plugin | Commands for granting, renewing, and removing the benefit |
| Player ID | Whether the command expects Steam64, EOS, a player name, or another ID |
| Game rules | The benefit is allowed by the game's sales rules (below) |
| Result | Purchase, delivery, and expiry verified using a test recipient |
Use Windows Agent setup for installation and the command reference for syntax.
Game sales rules
Each game publishes what servers may sell. Read the rules for your game before selling. Products that break a game's rules cannot be sold under the Moneta terms either. This summary is based on the official documents as read on 30 September 2026 and is not legal advice. Rules change, so check the originals.
| Game | Allowed | Not allowed / notes | Official document |
|---|---|---|---|
| Minecraft | Access fees (same price for everyone), donations, cosmetics, gameplay entitlements that don't ruin other players' experience or give a competitive advantage, in-game currency that can't be cashed out | Competitive advantages. Anything that looks like a cape. Show content and prices before players join. Give paying users a purchase history. Don't use the Minecraft name or logo as your main name | Usage guidelines, EULA |
| Rust, Garry's Mod | Access fees (one-off or subscription), donations, cosmetic items, effects or enhancements, server currency, ads | Don't grant Facepunch DLC to players who haven't bought it, or block players from DLC they own. Make clear the server is unofficial | Facepunch server guidelines |
| ARK: Survival Ascended | Revenue up to operating costs, and tips | The dedicated server EULA forbids running it for Commercial Purposes, defined as revenue above operating costs or tipping | Dedicated server EULA |
| CS2 | Not stated | The older CS:GO server guidelines ban letting players use skins they don't own, fake ranks, and custom models or skins; Valve disabled tokens of servers that broke them. They don't say whether they apply to CS2 | CS:GO server guidelines |
The Rust guidelines list only the five kinds of monetisation above. They don't mention gameplay advantages such as kits, resources or queue priority, so we recommend asking Facepunch before selling them.
Minecraft Java Edition and LuckPerms
- Enable RCON on the Java server and check its actual port and password.
- Install LuckPerms and prepare the
vipgroup and permissions. - Register a Minecraft RCON target in Moneta using the game's configured port.
- Require
playerIdin the product. For this example, enter a player name recognized by LuckPerms. - Configure purchase and expiry commands and verify with a test recipient.
lp user {{id.playerId}} parent add viplp user {{id.playerId}} parent remove vipThis example uses ordinary group membership and needs no renewal command. Removal processing removes the group after the Moneta benefit ends. If other products also grant that group, check that removal will not affect their benefits.
See the official parent-command documentation.
ARK and ARK: Survival Ascended
The Agent has ark and arksa connection settings. Enable RCON in the game and register its host, actual RCON port, and password.
VIP, kits, or points require a game plugin that provides those operations. Choose the plugin and version, then check:
- Whether commands require Steam64, EOS, or an in-game ID.
- Whether the commands work through RCON.
- Whether the recipient must be online.
- Whether the granted benefit can be removed when it ends.
There is no single grant command shared by all plugins. Match ID settings and commands to the selected plugin.
Rust and Oxide
For Rust, the Agent connects over WebRCON. Older Agent versions don't support WebRCON, so update to the latest version.
- Enable WebRCON in the server launch options, for example
+rcon.web 1 +rcon.port 28016 +rcon.password "password". - Use letters and digits for the password. Spaces,
/,#or?may stop the connection from working. - Install Oxide (uMod), then create a
vipgroup for the benefit and grant it permissions, for exampleoxide.group add vip. - In Moneta, choose Rust as the game and register the RCON target. Use the
rcon.portvalue as the port. - Choose
steam64as the product's required ID, then set the purchase and end commands.
oxide.usergroup add {{id.steam64}} vipoxide.usergroup remove {{id.steam64}} vipWhat happens when the buyer has never joined the server can differ between Oxide versions. Before selling, test granting and removing with a test Steam ID. If you use Carbon, replace these with its equivalent commands.
Check Game sales rules for what you may sell. WebRCON setup is covered in Facepunch's server guide.
Other games and plugins
For CS2, Garry's Mod, and other games, available benefits depend on game or plugin commands. For Palworld too, start with the protocol rather than the game name.
Include these details when asking for help. Do not send passwords or Agent credentials.
Game and version:
OS and hosting environment:
Plugin and version:
Benefit to sell:
Player ID type:
Commands tested and results:Use the contact page.