Server Owner FAQ

1. Sign up at playeranalytics.org and start your free trial.
2. In the dashboard, click Add Server — you'll get an API key (shown once, so copy it).
3. Click Download Plugin and drop PlayerAnalytics.cs into your server's oxide/plugins/ folder.
4. Open oxide/config/PlayerAnalytics.json, paste your key into the "SaaS — API key" field, and reload with oxide.reload PlayerAnalytics.
5. Data starts flowing within a minute or two.

No — tracking is automatic. Players can optionally sign in with Steam (free) to view their own stats, and link Steam↔Discord for rewards, but nothing is required of them for analytics to work.

It's 14 days, free, on the monthly plan. You add a payment method at checkout, but you're not charged until the trial ends — cancel anytime before then and you pay nothing.

$9.99 / month per server. Prepay and save:

• 3 months — $26.99 (~10% off)
• 6 months — $49.99 (~17% off)
• 12 months — $89.99 (~25% off — about 3 months free)

Prepaid plans bill up front and don't include the 14-day trial.

Per server. Two servers on monthly = $19.98/mo, and so on. Monthly plans prorate instantly when you add or remove a server; prepaid plans lock your price for the term.

From the Billing card in Account Settings → Manage Billing. You can switch between monthly and prepaid plans right from the dashboard — even during your trial — and cancel anytime.

Yes. Prepaid plans get a reminder email about 7 days before they auto-renew, showing the upcoming amount.

Use Download Plugin in the sidebar, or the plugin card in Account Settings. If a server is running an older version, you'll see a red Update Plugin badge on its card and a banner at the top of the dashboard.

No — for security we only ever store a scrambled (hashed) version, never the key itself. Just click Rotate Key on the server card to generate a new one, paste it into the plugin config, and reload. The old key stops working immediately.

Two quick checks:

• If the plugin logs "Invalid API key" (401) — the key is wrong or was rotated. Repaste the current key and reload.
• If there are no requests at all — your server can't reach api.playeranalytics.org (firewall/DNS).

Also confirm your subscription or trial is still active.

Once your server has logged about 30 player sessions and a few deaths — usually within the first day, faster on a busy server. Until then it shows "—" so it isn't misleading on thin data. It updates live, with no nightly batch to wait for.

It's a single 0–100 score that blends several signals about whether players are enjoying your server. The biggest factors are:

• Do players come back? — how many return the next day (this counts the most), within a week, and longer term.
• How long they stay — your average session length.
• How active they are — gameplay events per session and total daily traffic, measured against your server's slot count so small servers aren't penalized for being small.
• Lifetime playtime — how many hours your regulars rack up.
• Rage-quits — a low rate lifts the score; a high one drags it down.

The score only uses the signals it has enough data for, and it's shown to your players too. It needs roughly 30 sessions and a few deaths before it appears, so it isn't thrown off by a quiet first hour.

The Community Health Score is a separate, owner/admin-only score that measures how "sticky" your community is — not the live gameplay experience the Server Health Score tracks. It's built from:

• Returning players — long-time players who are still showing up.
• New-player retention — whether recent newcomers stuck around.
• Engagement depth — how active your players are.
• Link rate — how many of your active players have linked their Steam account.
• Community investment — how many engagement features you've turned on (Welcome Back, Rivalries, web chat, Discord webhooks, achievements).

It carries a daily trend and a "what moved it" note so you can see the score change over time. It's wipe-proof (it uses lifetime player history), and it needs at least 5 active players in the last 30 days before it shows.

A rage quit is an actual logoff — not just a death. When a player disconnects, the plugin looks at their last few in-game actions: if 2 or more of them were deaths, that session is recorded as a rage quit (they died repeatedly, then left).

• Only voluntary logoffs count. Kicks, bans, and connection timeouts are never counted as rage quits.
• Suicides don't count toward the death streak (using /kill to respawn at base isn't frustration).
• The Top Rage Quitters list ranks players by how many times they did this; each player's detail page shows the deaths in the ~5 minutes before each quit — i.e. what actually drove them off.

Because a real rage quit is fairly rare — most deaths don't end in someone logging off — these numbers are usually low, and a quiet or PvE server may show none at all. That's expected, not a bug.

Players can remove themselves at playeranalytics.org/my-data — they sign in with Steam, see every server holding their stats, and erase themselves from any or all (which also stops future collection). They can download a copy of their data there too.

As an owner/admin you can also do it for them: open the player's profile, turn on Mod Mode, and use Erase player data (GDPR). Bans and mutes are kept either way. See the Privacy Policy for the full picture.

Yes — generate a Stats Embed Key in Server Settings. It's read-only (the same stats a player sees, no admin metrics) and your developer pulls it from their back-end. Full guide: playeranalytics.org/stats-embed.

Yes. On each achievement in Server Settings, click Reward… and add one or more rewards — any mix of Server Rewards (RP), Economics (currency), and Custom console commands (use the "Add reward" button for multiple). They're granted in-game the moment a player completes the achievement. You can also customize the unlock message shown in chat from Server Settings.

For Custom, you enter your own console commands (one per line) with placeholders: {id} = the player's Steam ID, {name} = their name, {amount} = the amount you set. For example: inventory.giveto {id} scrap 1000.

Players also get an in-game chat message and sound the moment they complete any achievement (reward or not) — e.g. "🏆 Achievement unlocked: Apex Predator". Turning rewards on won't retroactively pay or notify for achievements players already earned; only new completions count.

Per-wipe achievements pay out each wipe they're earned; lifetime ones pay once. This needs the plugin updated to v3.0.6+, and the ServerRewards or Economics plugin installed for those two options (Custom works with vanilla console commands).

Yes — turn on Mod Mode and you get Warn / Mute / Kick / Ban on each player profile, with reason templates, auto-escalation, a Mod Log, and optional Discord mirroring.

Set a Custom URL in Server Settings (lowercase letters, numbers, and hyphens; 3–32 characters). Your page goes live at playeranalytics.org/s/your-slug with leaderboards, reviews, who's online, and your branding.

Yes. In Server Settings, set "Is this a PvP server?" to Yes. The Map then hides everything a rival could use to scout — deaths, combat, gather, loot, builds, bases, raids, crafting, and team activity — from players and viewers. NPC kills, vending, and monument events (Bradley, Heli, server events, event wins) stay visible, since those don't reveal where someone bases.

You and your admins always see the full map. The hidden data is stripped on our side before it ever reaches a player's browser, so it can't be pulled out another way.

There's also a separate "Show names in map?" setting — turn it off to keep player names off the map labels for whatever sources do show. The two settings work together.

Webhooks for chat mirror, wipe summaries, achievement unlocks, welcome-back, moderation, and server offline/online alerts — plus Steam↔Discord linking with auto-join and role/group rewards.

The plugin detects the wipe and can reset per-server analytics so each wipe starts fresh (configurable). Your historical Wipe Summaries are preserved for players to look back on.

Yes — invite staff by email with the Members button. They get admin (or viewer) access and are never billed — they ride on your subscription.

No. Adding servers is owner-only, and billing is only visible and editable by the owner. Admins help run your existing servers — they can't create new ones or touch your plan.

Gameplay events — sessions, kills/deaths, activity, and server events — tied to Steam IDs, sent to PlayerAnalytics. See our Privacy Policy and Terms for full detail. Payment data never touches your game server; billing is handled entirely by Stripe.