Pivity vs BuildByBit: where to sell and support your addons
Side-by-side comparison of the two major game addon marketplaces Arnvio supports — Pivity for GMod/Rust, BuildByBit for Minecraft/Roblox/Hytale — and how to run support on each.
If you make game addons, two marketplaces cover roughly the entire buying audience in 2026: Pivity and BuildByBit. (GmodStore was renamed to Pivity — same platform, new brand, modernised tooling.)
Each targets a different set of games and has a very different support workflow. Here's how they actually compare, from creators who ship on both.
Quick comparison
| Pivity | BuildByBit | |
|---|---|---|
| Primary games | Garry's Mod, Rust | Minecraft, Roblox, Hytale |
| Audience | Focused GMod/Rust community | Largest by raw traffic, cross-game |
| Ticket system | Product-scoped, API-first | Account-scoped, plain text |
| API quality | Modern REST, good docs | Solid, account-level |
| Arnvio integration | Dashboard → Integrations → Pivity | Dashboard → Integrations → BuildByBit |
| Best for | GMod & Rust creators | Minecraft, Roblox, Hytale creators |
Which marketplace supports what
This is usually the first question — and the answer is cleaner than you'd think:
- Garry's Mod addons → Pivity
- Rust addons and plugins → Pivity
- Minecraft plugins (Bukkit, Paper, Spigot, Fabric, Forge) → BuildByBit
- Roblox models and scripts → BuildByBit
- Hytale content → BuildByBit
If your product spans games (rare, but it happens), you'll list it on both. Arnvio handles multi-marketplace catalogs from a single account.
Pivity
The modern GMod and Rust marketplace — the rebrand and rebuild of what used to be GmodStore. Same audience, dramatically better creator tooling.
Support workflow: Product-scoped tickets, clean REST API, real-time webhooks. Arnvio integrates via API token; setup takes about 5 minutes end-to-end.
Why creators like it for automation: the API is genuinely well-designed. Arnvio can import your open tickets on a schedule and give you a "Generate AI reply" button that drafts a response from your training data — you review and send from Pivity, so the customer still hears from you.
When to prioritise Pivity: you sell GMod or Rust addons. That's the whole answer.
BuildByBit
The biggest of the two by raw traffic, spanning Minecraft, Roblox, Hytale, and adjacent games. Different feel from Pivity: broader audience, wider skill range, more install-hand-holding.
Support workflow: BuildByBit uses account-level tickets rather than per-product tickets. One agent on your Arnvio account can help draft replies to every ticket across every product you sell. Efficient, but training data has to be clean because the agent needs to identify which product the customer is asking about.
When to prioritise BuildByBit: you sell Minecraft plugins, Roblox models, or Hytale content. This is where those buyers live.
How to think about running both
Most established creators sell on both. The support pattern that works:
- One Arnvio account, both integrations. Connect Pivity and BuildByBit under a single account.
- One agent per marketplace, or one per product family. The bigger your catalog, the more you want to split — smaller training data per agent = more accurate drafts.
- Draft, review, send — every time. Arnvio never auto-replies to your customers. It drafts using your agent's knowledge of your docs; you review and send from the marketplace. The customer relationship stays yours.
- Unified escalation. Route the "needs a human decision" tickets to a single inbox (email, Discord, or Notion). Don't context-switch between two marketplace dashboards.
The one thing that matters more than platform choice
Wherever you sell, the support experience your customers get is 90% about your documentation, not the platform. A creator with excellent docs on BuildByBit beats a creator with mediocre docs on Pivity every time — and the AI drafts get dramatically better with cleaner training data. See our training guide for the tactical version of that argument.