Frequently Asked Questions
Quick answers to the questions support hears most often. Use the category chips to narrow the list; click any question to expand the answer.
What is SimpleLinks?
SimpleLinks is a hosted Steam ↔ Discord linking service for Rust server owners. Players verify once on a branded link page, and your Oxide plugin queries our API to read the verified Discord identity, Oxide group membership, country, and Trust Score for any SteamID on the fly.
You do not run anything yourself — a single plugin sits in your oxide/plugins directory and talks to the API.
Do I need a separate bot or web server?
No. The Discord bot, the link page, and the API are all hosted by SimpleLinks. The only file you install is the Oxide plugin on your Rust server.
Which Rust modding frameworks are supported?
Currently Oxide / uMod. Carbon support is on the roadmap but the API itself is framework-agnostic — anything that can issue an HTTPS request with a header works.
How does a player link their accounts?
Players run /link in your Rust server (or click your branded link page URL). They authorise with Discord, confirm the SteamID detected from the in-game request, and the binding is live within a second.
The link page lives at your-subdomain.simplelinks.cc by default, or your own custom domain on Standard and Pro plans.
Can one Discord be linked to multiple Steam accounts?
Yes — but every additional Steam reduces the Discord identity's Trust Score through the multi-account penalty. The full bond history (including archived links) is visible on the Account Graph.
What happens when a player unlinks?
The binding is moved to an archived table, not deleted. The Account Graph keeps showing the historical edge so admins can detect alt-account patterns. The Plugin API will report the SteamID as unlinked from that moment forward.
How do I authenticate Plugin API requests?
Every request sends the per-server Plugin Key in the X-Plugin-Key header. Keys are scoped to a single Server inside a Guild inside an Org — see Authentication for the full hierarchy.
What are the rate limits?
Free: 60 requests/minute per Server. Standard: 600/min. Pro: 6000/min. Bursts up to 2× the steady-state limit are absorbed by a token bucket. Full table on the Rate Limits page.
Why am I getting 401 invalid_plugin_key?
Three usual causes: (1) the key was rotated in the Dashboard and the plugin still has the old value; (2) the header name is wrong — it must be exactly X-Plugin-Key; (3) the Server was deleted or moved to another Guild. Rotate or re-issue the key from Dashboard → API Keys.
Can I cache Plugin API responses?
Yes, briefly. The plugin already does a 5-minute in-memory cache for lookups. Going longer is fine for low-stakes data (country, display name) but not recommended for permission-sensitive fields like Oxide group membership, which can change at any moment from admin actions.
How is the Trust Score calculated?
It is a weighted composite: Stability 35% + Cross-server reputation 25% + Age 20% + Multi-account penalty 20%, normalised to 0–100 and bucketed into Trusted / Normal / Watch / Risk tiers. The exact formula and inputs are documented on the Trust Score page.
What counts as a "zombie" account?
Any linked identity whose last verify request is older than the Org's Zombie Threshold (default 90 days, configurable in Settings). Zombies are flagged in the Users list and can be cleaned up in batch — the cleanup is opt-in and reversible from the archive table.
Can I override the Oxide group tier classification?
Yes — SimpleLinks auto-classifies group names by keyword (e.g. vip → Trusted, banned → Risk), but you can override any group's tier per-Org in Settings → User Management → Oxide Group Tier Overrides. Overrides affect both Trust Score input and the pill colours in the Users list.
What is included on the Free plan?
One Guild, one Server, the full 32-action Plugin API, the Dashboard, the link page on a SimpleLinks subdomain, and 60 req/min. No credit card. Free plans never expire.
What do the Standard and Pro tiers cost?
Standard is $5 / month or $50 / year (two months free). Pro is $10 / month or $100 / year (two months free). Both unlock unlimited links and bring up the Org / Guild / Server caps; Pro adds white-label, custom CSS on link pages, and priority support. The Custom Bot add-on at $5 / month per Discord server is sold separately and stacks on any tier, including Free.
How does upgrading work?
Upgrades from the public pricing page or the in-Dashboard Billing tab take you straight to Stripe Checkout. The new limits and features unlock the moment the checkout completes; the webhook updates your Org tier in seconds. If you already have a plan subscription, switching tiers (Standard ↔ Pro) or intervals (monthly ↔ yearly) is done through the Manage Billing portal, which prorates the difference automatically — you only pay (or are credited) the unused portion of the current period. Downgrades to Free always take effect at the end of the current billing period.
Can I switch between monthly and yearly?
Yes — open Billing → Manage Billing in the Dashboard and update the price on the existing subscription. Stripe prorates the swap automatically. Yearly is roughly 17% cheaper than paying monthly (two months free).
Can I cancel any time?
Yes. Cancellation is one click in the Dashboard. Your Org reverts to Free at the end of the period — nothing is deleted, but features beyond the Free tier (extra Servers, Custom CSS, custom domain) become read-only until you re-subscribe.
What is the Custom Bot add-on?
$5 / month per Discord server. You supply your own Discord bot token and the verification flow runs under your bot's name and avatar instead of ours. Setup details on the Custom Bot page.
What happens to my custom bot if I cancel?
You keep custom-bot capability until the end of the paid period. After that, the shared platform bot takes over automatically — no broken verifications, no downtime. Your saved token stays disabled and can be re-enabled the moment you resubscribe.
What player data do you store?
SteamID, Discord ID, Discord username and avatar hash, country code of the last verify request (no city, no GPS), the linked-at and last-seen timestamps, and the Oxide groups your servers report. We do not store IP addresses long-term — the country attribution is computed from the request and the raw IP is discarded.
How do I delete a player's data?
Use the user detail view in the Dashboard, or call POST /users/:id/unlink. Unlinking archives the binding for audit; full GDPR-style deletion is available on request via support — it scrubs the row from both live and archive tables.
Where is the data hosted?
SimpleLinks runs on a global edge platform with the database replicated to the region nearest each request. Your data never touches a non-edge origin server.
Still stuck? Open an issue on GitHub or ping support from the Dashboard.