Getting Started

Verify Setup

Confirm that the RanklyStats mod is running correctly and data is flowing to your dashboard.

Step 1 — Check RPT Logs

After starting your server, open the latest .RPT log file in your profiles directory. Search for "Rankly" to find mod messages. You should see:

[Rankly] RanklyStats mod initialized
[Rankly] Config loaded — endpoint: https://rankly.gg/api/ingest
[Rankly] API key validated
[Rankly] Ready — tracking events

RPT files are typically located at profiles\DayZServer_x64_*.RPT (where "profiles" is your -profiles= directory).

Error Messages to Watch For

![Rankly] RanklyConfig.json not found — Config file is missing or in the wrong directory

![Rankly] Invalid API key format — API key does not match the expected RNKLY-XXXX-XXXX-XXXX-XXXX format

![Rankly] Failed to reach endpoint — Network issue or firewall blocking outbound HTTPS

Step 2 — Check Your Dashboard

Once a player connects to your server, data should appear on your Rankly dashboard within 1–2 minutes. Look for:

·Player connect/disconnect events in the activity feed

·Server status showing as "Online" with a player count

·Kill feed entries once PvP or PvE combat occurs

Expected Timeline

0–30 secServer starts, mod initializes and validates config

30–60 secFirst player connects, connect event queued

1–2 minFirst batch sent to Rankly (based on send_interval_seconds)

2–5 minData processed and visible on your dashboard

Common Issues

Wrong profiles directory

RanklyConfig.json is not in the directory set by your -profiles= launch parameter. Check that the file is in the correct folder. The RPT log will show "RanklyConfig.json not found" if the mod cannot locate it.

Fix

Move RanklyConfig.json to the correct profiles directory and restart the server.

Firewall blocking outbound HTTPS

Your server host may block outgoing connections on port 443. The mod needs to reach https://rankly.gg to send data.

Fix

Allow outbound HTTPS (port 443) to rankly.gg in your server firewall or contact your hosting provider.

Placeholder API key not replaced

If the config still contains "RNKLY-XXXX-XXXX-XXXX-XXXX" the API will reject all events with a 401 Unauthorized response.

Fix

Replace the placeholder with your actual API key from the Rankly dashboard.

Using -mod instead of -servermod

If you accidentally used -mod=@RanklyStats, clients will be required to download the mod to join. RanklyStats is server-side only.

Fix

Change -mod to -servermod in your launch parameters.

No players connected

The mod only generates events when players are on the server. An empty server will not produce data.

Fix

Connect a player to the server and wait 1-2 minutes for the first batch of events to be sent.

Still Not Working?

1.Double-check all steps in the Quick Start Guide

2.Review the FAQ & Troubleshooting page for additional diagnostics

3.Contact support with your RPT log file and server details — we will help you get set up

Previous: Configuration · Back to Getting Started