A dedicated server only relays the world. Combat, damage and deaths are worked out on the game of the player who owns that part of the world, so a server on its own never sees a kill. WhereTheCrowFlies hooks those moments on each player's game and sends them to the server every ten seconds. The Raven's Call checks each report against the players actually connected before it credits anything.

Nothing earned before is lost. The vanilla stats and skills arrive as a full snapshot, not as changes, so the moment a player's game reports, everything they had earned before the mod was installed is filled in. A lost packet cannot make them drift.

Without the crow a player still shows up with joins, leaves, playtime and biome discoveries, and the census still counts what they have built. On a vanilla or unmodded server, WhereTheCrowFlies stays silent: no errors, no delay, nothing in the log.

Gear tier is in every record, but stays at zero on a dedicated server today.

Discord gets the big moments. Joins, leaves, raids, season starts and ends, lore lines, boss world-event messages and the server's start and stop go to the Chronicle, the dashboard feed and the server log, never to Discord. Each kind of player event can be switched off on its own.

The narration has a Norse voice. Each event is told from a set of flavour templates, picked at random. Turn EnableNarrativeMode off for plain fixed lines.

Your own words, too. Write a message per boss in the WorldEvents settings, and it is recorded after that boss falls. Fill lore.txt with lines of lore, set an interval, and the raven recites one at random. A few lines of Norse myth are there to start with.

The online count is honest. It counts the players actually in the world: a player who just left is not counted, and neither is one still at the password prompt. A player whose game crashed counts until the server drops the dead connection, up to half a minute, or a minute and a half on a crossplay server.

It lives at http://localhost:2112 on the server machine, and the page ships inside the mod. To reach it from another PC, see the Toolbox below.

No health, inventory or position for a player who is online. A dedicated server never has them: they live on the player's own game. The dashboard shows each player's stored record instead: totals, titles, skills, milestones, the death history and everything WhereTheCrowFlies reported. The only positions it keeps are where players died.

With a token set, the page opens its settings panel for you the first time it is refused. The feed and season panels say "Needs the API token (Settings)." until you enter it.

Just the files? EnableHttpServer = false turns the page and the API off. The bot export, the Chronicle, Discord and the hosted push keep running.

The title is the server's name for you: in its Discord and Chronicle narration, on the dashboard and in the bot export. Nothing changes on the in-game nameplate.

Your first title wears itself. After that you choose: titles you earn later are added to your list and wait there until you pick one. A cleared title stays cleared.

Only earned titles. Neither a player nor an admin can set a title that player has not earned. The player commands need WhereTheCrowFlies on that player's game and AcceptClientReports on. The admin command works from the server console with no client mod, or from an admin's game with WhereTheCrowFlies. A change shows on the dashboard and the export at the next refresh.

Run it from the server console, or from an admin's game with WhereTheCrowFlies installed (F5 console): the server checks its admin list first. Leave the name off and the season is called Season_ plus today's date. The name becomes the Chronicle's season folder, so trailing periods and spaces are trimmed.

One season at a time. season start refuses while a season is running and names it: end it first.

Standings are deltas. At the start the server notes each player's counters, so the season panel shows what was done during the season, not lifetime totals.

A short hitch every few minutes. The census walks the loaded world's objects on a timer, every 5 minutes by default (CensusIntervalMinutes). A real server with about 1.1 million objects finishes in under half a second. Set it to 0 to turn it off; the dashboard then says so in one line.

Two plain files, no new ports. A bot that already reaches the server over FTP or SFTP needs nothing else. Deleting BarrkBOT_data1.json does no harm: it is back on the next refresh. Renaming either file breaks a bot that looks for it. The Toolbox has the file's shape and a short example.

A rented server gives you the game's ports, a web panel and FTP: no shell, and no way to open the dashboard's port. The push needs only outbound HTTPS, the same way out the Discord webhook already uses.

What leaves the box. A read-token holder sees the roster with every player's stats, skills, titles and death positions; the feed and season standings; and the census, with the rough position of every portal, bed and ward. Only for that server, and only with that server's token.

One small difference. On the hosted page, fish and resource names are shown as tidied-up game names instead of their real ones.

Where it has run. A Windows and a Linux dedicated server have pushed to a receiver over HTTPS, and a real Windows server pushes to Raven Iron's receiver at https://trc.ravenirongames.com. It has not yet been run on a rented host.

The server answers only itself by default. Set HttpBindAllInterfaces = true together with HttpApiToken (a long random value), restart, and keep port 2112 (HttpServerPort) behind a firewall. With a token set, /api/state, /api/gamedata, /api/activity, /api/census and /api/pins need ?token=<value> or an X-Api-Token header; the page and /api/health stay open. In the browser, enter the token once in the page's settings (the gear, top right).

Make a webhook in your Discord channel's settings and paste its address into WebhookUrl under [Discord] in BepInEx/config/com.raveniron.theravenscall.cfg. Deaths, boss kills, kill and death milestones, biome discoveries and titles then post as embeds. With WebhookUrl empty nothing is posted, and everything else works the same.

The files are BepInEx/config/TheRavensCall/BarrkBOT_data1.json (players) and BarrkBOT_data2.json (game data). The players file looks like this:

{
  "generated_at": "2026-08-17T04:12:00.000Z",
  "world_name": "Midgard",
  "day": 214,
  "online_count": 6,
  "raid_active": false,
  "raid_type": "",
  "players": {
    "Thorium Wubarrk": {
      "name": "Thorium Wubarrk",
      "kills_narrative": 341,
      "deaths_narrative": 12,
      "active_title": "Wolf Hunter",
      "...": "..."
    }
  }
}

A minimal read in Node.js:

import { readFileSync } from 'node:fs';

const data = JSON.parse(readFileSync('BarrkBOT_data1.json', 'utf8'));
const player = data.players['Thorium Wubarrk'];

if (player) {
  console.log(`${player.name}: ${player.kills_narrative} kills, ` +
    `${player.deaths_narrative} deaths, title: ${player.active_title || 'none'}`);
}

The full field list is in docs/API.md in the GitHub repo.

Raven Iron's receiver is for its own servers only, so deploy your own private copy of hosting/netlify/ from the GitHub repo; its README has the receiver's side.

1. Make two tokens: run openssl rand -hex 24 twice, one for HttpApiToken (unless you already have one of 24 characters or more) and one for PushToken.
2. Set HttpApiToken (24 characters or more) under [Companion], and PushUrl, PushToken and PushServerId under [Push], in com.raveniron.theravenscall.cfg. The id is 1 to 32 characters of a-z, 0-9 and -.
3. Register the id with both tokens' sha256 hashes in the receiver's TRC_SERVERS environment variable, then redeploy the receiver: a change in the Netlify UI does nothing until the site is redeployed.
4. Open https://<your receiver>/s/<id>/. Raven Iron's own runs at https://trc.ravenirongames.com.

How often. The push rides the same tick as the export, so it rounds up to a multiple of StatsPushIntervalSeconds (10 s by default): PushIntervalSeconds = 15 pushes every 20 s. PushHeartbeatMinutes pushes everything even when nothing changed, so the page knows the server is alive.

Changed the API token? Restart the server and register the new hash: the pushed hash only changes at a restart.

Read the BepInEx log; on a rented host, pull it over FTP. A working push logs one Push enabled: server_id='…' line at boot, then stays quiet.

• Push disabled: names the setting that is missing or malformed.
• Push failed: means the receiver could not be reached; the mod keeps retrying.
• Push rejected: names one of four refusals, each retried every 15 minutes:
  • 401: the push token was rejected. Check PushToken and PushServerId against the receiver's registry.
  • 409: the receiver has a different HttpApiToken hash for this id. Re-register read_token_sha256 and redeploy.
  • 422: the receiver refused the bundle. Set HttpApiToken to 24 characters or more.
  • 413: the bundle is over the receiver's 2 MB limit.

Until the first push lands the page reads "Registered, waiting for <id> to report"; "server silent since …" means no push has arrived for three heartbeats.

Send DELETE /s/<id>/api to the receiver with the write token in the Authorization: Bearer header. It answers {"deleted":true}, removes the stored copy, and the page reads "no data" again. Then remove the id from the receiver's registry and redeploy, so the tokens are dead too. Clearing PushUrl on the server stops new pushes at its next restart.

Copy the folder BepInEx/config/TheRavensCall/ and the settings file BepInEx/config/com.raveniron.theravenscall.cfg. The folder holds: