Reading the screen

When exactly to report — Zero

On Ragnarok Zero, a respawn is counted from the server broadcast, not from the moment the boss dies. The two are a few seconds apart, and the whole window shifts by that much.

So report when the broadcast message appears on your screen. If you report as the boss falls, every timer you set will be slightly early — and the guild will conclude the tracker is wrong.

Reported at the wrong moment? Open the pencil and correct the time. It is worth the ten seconds it takes.

Recording a kill

Double-click a boss to report it as killed right now. A confirmation shows the boss, its map, the PvE/PvP zone and the time — read it before confirming. Your report starts the countdown for every member of the guild, so a mistake sends everyone to the wrong place.

If a timer already exists, the confirmation tells you how long ago it was set and by whom. That is usually enough to tell a genuine re-kill from a misclick.

Adding details after the kill

Click the pencil to open the edit window. There you can:

• correct the kill time if you reported late, or read it from the tombstone;
• pick the map when a boss spawns in more than one place;
• click the map to drop the exact position where it died.

Positions build up over time and reveal the spots a boss actually favours. Editing a kill never changes who reported it — the original author is kept.

Saying you are going

On an Imminent card, I'm up for it tells the guild you are heading there now. Several people can claim the same boss: it is a signal, not a reservation.

What matters just as much is the opposite. A boss marked Unassigned while its window is open means nobody is covering it — that is where you should go.

A claim expires on its own after 12 minutes, and disappears as soon as the kill is reported. Nobody has to remember to withdraw it.

Timer states

A respawn is always a window, never an exact time. That is why you see a range rather than a single moment.

Hovering and boss details

• Over a row — a mini-map showing exactly where the boss died. It only appears once someone has recorded a position, through the pencil.
• In the edit window — the boss card: element, race, size, level, and the elements it takes the most damage from.

PvE and PvP zones

The normal warp and the PvP warp lead to two different maps. Their bosses respawn independently, so each has its own timer. PvP boss names glow red and their row carries a red band down the left edge. The Zone filter shows one at a time.

Reporting a PvP kill on the PvE entry throws off both timers at once — check before confirming.

Discord alerts

A guild can connect a Discord channel from the menu. Once set up, the tracker posts on its own, without anyone needing the site open — that is the whole point.

Times are posted so that each reader sees them in their own timezone — a member in France and one in the UK read the same message differently, and both read it right. Nothing to configure.

Messages delete themselves once the respawn window has closed, or as soon as the boss is reported killed again. The channel keeps only what is still true.

With Raid-Helper set up, each kill announcement carries a Create raid button. One click, one confirmation, and the event is posted — once per kill.

Pick a mention (@here or a role), otherwise the message is posted but nobody is notified.

Your guild code

The code is the key. Anyone holding it can see and change your timers, so treat it like a password rather than a name.

Rotating the code closes the door to newcomers, it does not remove anyone. Members already in the guild keep their access. If you want a clean slate, the second prompt offers to remove every member as well — each then has to rejoin with the new code.

Timers, history and Discord settings are never touched by a rotation. They belong to the guild, not to its members.

Shared across the guild

Timers, history and statistics belong to the guild, not to your browser. Anything you report reaches the other members in under a second, with no refresh.

The same applies to deletions: Clear this timer removes it for everyone, which is why it asks for confirmation. The kill stays in the history.

Good habits

• Report immediately, before looting — thirty seconds of delay shifts the whole window.
• Wrong report? Fix the time in the edit window rather than reporting again.
• After maintenance, every boss respawns at once: earlier timers are worthless.
• Keep your guild code private. Anyone holding it — or holding an invite link — can see and change your timers. If one leaks, the guild owner can issue a new code in two clicks.

On a phone

The horizon, recent kills and statistics are hidden on small screens. Only Imminent and the list remain — what you need when you are already running.

Reporting a problem

The version number sits in the bottom-left corner of the page. Quote it when you report an issue — it shows straight away whether your browser is running the latest build or a cached one.