ArmaDB

Server-side player event logging with Discord webhook batches, BIS IDs, UTC and Kyiv timestamps, combat details, and a persistent delivery queue.

Players now

19

Servers

4

Rating

-

Subscribers

-

256 downloads

Get it on the Workshop reforger.armaplatform.com/workshop/6A57335815F000B2

Busiest servers running it 4 in total

All servers

Players on servers with it

daily, last 30 days

0 20 40 60 80 17 Sep 24 Sep 1 Oct 8 Oct 15 Oct peak 63
Average players Low to peak in each bucket

Details

Author
Dobrogo_Vechora
Version
1.0.5
Size
22 KB
Licence
APL
Game version
1.8.0.13
Likes
0 / 0 dislikes
Published
12 Sep 2026
Updated
1 week ago
Workshop ID
6A57335815F000B2

Recent adoption

30 days: +11 −10 ↑5

Version history

6
  1. v1.0.5 22 KB 8 Oct 2026
  2. v1.0.4 18 KB 20 Sep 2026
  3. v1.0.3 15 KB 14 Sep 2026
  4. v1.0.2 15 KB 13 Sep 2026
  5. v1.0.1 14 KB 13 Sep 2026
  6. v1.0.0 10 KB 12 Sep 2026
Description from the Workshop

CENTURIA Game Events Logger records player activity on your Arma Reforger server and delivers event batches to a Discord channel through a webhook. EVENTS • PvP kills and player deaths • Teamkills and suicides • Other player deaths • Player connections and disconnections • Admin kicks and bans • Scenario start/end and restart requests • Detection of a previously interrupted session PLAYER INFORMATION Player-related events include nicknames, BIS identity UUIDs and factions when available. Every event includes its occurrence time in UTC and Kyiv time. COMBAT DETAILS Available information includes damage type, hit zone, damage-source prefab, held weapon context, and distance between participants. The local journal stores additional technical details. BATCH DELIVERY Events are recorded immediately and sent to Discord every 10 minutes by default. The interval is configurable. A persistent local outbox retains pending events across ordinary restarts and retries failed deliveries. SETUP 1. Install the mod on your server and start a scenario. 2. Open CENTURIA_GameEventsLogger/config.json in the server profile. 3. Set webhook_url and enable discord_enabled. 4. Restart the server. Keep your webhook URL in the server profile only. Never include it in the published addon. NOTES • Initial test release; live server validation is ongoing. • A kill and its corresponding player death share one event. • Combat details depend on what the engine and other mods expose. • Connection loss does not prove a client crash. • Scenario lifecycle events do not always indicate a process restart. • Duplicate delivery is possible after an ambiguous network failure. • Requires a scenario based on SCR_BaseGameMode. • No external mod dependencies.