A shared battle board for War of Emperium. Your WOE leader places every
group on the castle map; you see your own order on a second screen, live,
and report contact with one button.
Nothing to install and no account to create — a guild code is all it takes.
I have a guild code
Your WOE leader gives you the code. Paste it, then use the character you
actually play WOE with — that name is what the leader sees next to your
reports.
Already using the RO MVP Tracker? The same guild code works here — this
reads the guild you already have, it creates nothing.
I am setting this up for my guild
Creates a space with its own code, which you then share with your guild.
You become its WOE leader straight away, simply by being its first member.
Pick the server your guild plays on: it decides the WOE schedule and the
countdown everyone sees.
Groups
Map
no plate yet
——
Contact
Event log
Timeline
No team yet
Pick your team in Roster
no plate yet
All castles
Every castle, grouped by city. A red frame means at least one team is
in contact there right now.
Past sessions
Open one to read its log — who was hit, when, and in what order.
Your team
Your reports go to this team, and your orders come from it. Ask for the
team you fight with — your WOE leader confirms it, so the roster stays
the one they built.
Pending requests
Members asking to join a team. Nothing changes until you approve.
Import roster
One line per team, as Group · Team number · Player. Groups and
teams that do not exist yet are created; a player already in the guild is
assigned straight away, and anyone else is remembered so they land in
their team the moment they join with the guild code.
No WOE leader yet
Claiming leadership sends a confirmation code to your guild's Discord
channel. Anyone in the channel will see the request — that is the point.
Session
Switching space only forgets the guild on this device — your identity,
and your leadership, stay intact. Signing out destroys the anonymous
identity itself: you come back as somebody else.
Reporting rules
How fast a member may report again, and how long a contact stays on
the board before it fades back to unknown.
CooldownsecContact lastssec
Leaders
Always keep a second leader. An anonymous identity lives in this
browser only — cleared data or a new machine means a lost account,
and a space with a single leader would stay locked forever.
Site admin
castle plates & WOE hours
Castle plates and schedules are shared by every guild, so they sit
behind a separate key. If you don't run the site, ignore this.
WOE hours
Castles
Unticking a castle hides it everywhere — selector, grid, new plans.
Nothing is deleted: its plans and past sessions stay, and ticking it
back restores them as they were. A castle with a live session stays
visible regardless.
Calibration
Plates are shared by every guild — saving needs the admin key from
Roster. Image size is read from the file itself.