CENTURIA Game Events Logger

by Dobrogo_Vechora
CENTURIA Game Events Logger

Summary

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

Description

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 same-faction kills flagged for review
• Suicides and other player deaths
• Player kills against AI when exposed by the scenario
• Player connections and disconnections
• Admin kicks and bans
• Game Master role grants and revocations
• Game Master interface opening and closing
• Supported Game Master teleport actions
• 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. Damage records include their age and whether the recorded attacker matches the credited killer.
When available, an earlier non-TRUE damage record is retained as additional context for deaths completed by medical or scripted damage. The local journal stores additional technical details.
EXTRA / EXTRA2 EQUIPMENT
Death events record the items equipped in the Extra and Extra2 slots of the killer and victim. These slots are commonly used for colored identification tapes or armbands.
Discord displays item names or prefab filenames and distinguishes empty slots, missing slots and unavailable data. Items carried inside backpacks or pockets are not counted.
Separate snapshots are captured when damage is observed and when death is recorded. If the equipment differs, the card shows the earlier state with its age. This helps administrators review incidents, but does not automatically determine whether a teamkill was intentional.
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
Install the mod on your server and start a scenario.
Open CENTURIA_GameEventsLogger/config.json in the server profile.
Set webhook_url and enable discord_enabled.
Restart the server.
Existing installations do not require new configuration settings for Extra/Extra2 logging.
Keep your webhook URL in the server profile only. Never include it in the published addon.
NOTES
• A kill and its corresponding player death share one event.
• Combat details and equipment availability depend on what the engine, scenario and other mods expose.
• Equipment snapshots describe observed damage/death time, not necessarily the moment a weapon was fired.
• Held weapons and earlier damage records are contextual information, not proof of the fatal weapon or hit.
• Teamkill classification does not establish intent.
• Connection loss does not prove a client crash.
• Scenario lifecycle events do not always indicate a process restart.
• Teleport-to-cursor logging records an accepted server request, not guaranteed completion of movement.
• Duplicate delivery is possible after an ambiguous network failure.
• Local checks do not establish compatibility with every server mod combination.
• Requires a scenario based on SCR_BaseGameMode.
• No external mod dependencies.

License

Arma Public License (APL)

Version
1.0.7
Game Version
1.9.0.37
Version size
21.97 KB
Downloads
639
Created
12.09.2026
Last Modified
05.11.2026
ID
6A57335815F000B2