🏰WoE Events Setup

Set up WoE tracking and scoring for your server

Track War of Emperium battles and generate leaderboards automatically. RagnaSync captures kills, castle captures, and guild attendance to calculate scores and post results to Discord.

How It Works

During WoE, your server sends events to RagnaSync:

  1. Session starts - WoE begins, initial castle owner recorded

  2. Events happen - Kills, captures, attendance tracked

  3. Session ends - Scores calculated, leaderboard posted to Discord

You'll see results like this in your Discord channel:

🏆 Castle Siege Results - Prontera Castle
════════════════════════════════════════

Rank | Guild Name      | Points | Breakdown
-----|-----------------|--------|----------------------------------
  1  | PhoenixOrder    |   8    | Castle Owner (3) + First Break (2) +
     |                 |        | Longest Control (3)
  2  | DragonKnights   |   1    | Most Kills (1)
  3  | ShadowLegion    |   1    | Attendance (1)

Configuration

Add these settings to your channels.conf in the discord: { } block:

Setting
Type
Default
Description

ragnasync_woe_enabled

bool

false

Enable WoE tracking

ragnasync_woe_channel_id

string

""

Discord channel for leaderboards

ragnasync_woe_attendance_min

int

3

Minimum members for attendance point

WoE Events

Your server sends these events during WoE. Each event uses RagnaScript format.

Status Events (Start/End)

Marks the beginning and end of a WoE session:

Field
Required
Description

guild

Yes

Guild that owns the castle

castle

Yes

Castle identifier

status

Yes

started or ended

Capture Events

When a guild captures a castle:

Field
Required
Description

player

Yes

Player who captured the Emperium

guild

Yes

Guild that captured the castle

castle

Yes

Castle identifier

account_id

Yes

Player's account ID

character_id

Yes

Player's character ID

Kill Events

When a player kills another during WoE:

Field
Required
Description

killer

Yes

Name of the player who got the kill

killer_guild

Yes

Killer's guild

killer_account_id

Yes

Killer's account ID

killer_character_id

Yes

Killer's character ID

killed

Yes

Name of the player who died

killed_guild

Yes

Victim's guild

killed_account_id

Yes

Victim's account ID

killed_character_id

Yes

Victim's character ID

castle

Yes

Castle where the kill happened

Attendance Events

Track guild participation during WoE:

Field
Required
Description

guild

Yes

Guild name

castle

Yes

Castle identifier

count

Yes

Number of guild members present

Point Values

See WoE Scoring for detailed scenarios, but here's the quick reference:

Award
Points
How to Earn

Castle Owner

3

Own the castle when WoE ends

Longest Control

3

Hold the castle for the longest total time

First Break

2

First guild to capture the castle

Attendance

1

Have enough members present (default: 3+)

Most Kills

1

Guild with the highest kill count

Castle Identifiers

Use these castle names in your events:

Castle
Identifier

Prontera

prontera

Geffen

geffen

Payon

payon

Alberta

alberta

Aldebaran

aldebaran

Castle identifiers should match your server's castle configuration. These are examples - use whatever names your server defines.

Tips

Session boundaries matter - Always send a started status at WoE begin and ended status when WoE finishes. Without these markers, scores can't be calculated.

Capture events are required for ownership changes - The castle owner can only change through capture events. If no captures happen, the guild from the start event owns the castle at the end.

Attendance is per-guild - Each guild can only earn 1 attendance point per session, regardless of how many attendance events are sent.

Kill ties share points - If two guilds tie for most kills, both receive the point.

Related

PreviousLogin & LogoutNextWoE Scoring

Last updated