Everything a Guild Leader, Official or Admin needs to run an SE event with zbot — the commands only you can use, the hits spreadsheet, and the order to do things in.
/se_boss. Nothing smart works until it knows./se_next. It picks by zone, hit size, reserves and who's awake./se_hits account:./se_reset on day one. Once, for the whole alliance.👉 You count as a leader if any of your Discord roles contains admin, leader, or official. That's the only gate — there's no separate list to maintain.
A 6-day guild boss event. zbot handles the clock for you.
Everyone gets 5 hits a day. Up to 2 unused hits carry over — anything past 2 is lost at reset. So the plan is: spend down to 2, and save those 2 reserves for Day 6.
zbot will not recommend a player who is down to 2 hits or fewer, unless it's Day 6, or unless they die at boss 50 and the boss is still above 50 (then it tells them to dump everything).
| When | What zbot does |
|---|---|
| 5:00 PM | Posts a reminder in each -se channel and pings the guild role: "SE reset in 1 hour — use your hits, only 2 carry over." |
| 6:00 PM | Daily refresh: everyone gets 5 hits plus up to 2 carried over, and the day counter ticks up. |
| After Day 6 | The event ends itself. No more reminders, no more refreshes. |
Both are automatic once /se_reset has started the event. You don't schedule anything.
The boss counts down from 200 to 1. Lower number = far more HP. Kill one and the next, harder boss spawns.
zbot remembers one current boss per guild — level plus % HP remaining. Leaders set it; every recommendation is built from it.
A hit's power depends on the boss's % HP remaining. This is the heart of every recommendation.
Above 70%, zbot looks for the smallest hit that can still carry the boss all the way past the deadzone — no point sending your biggest hitter to do a job a medium one can do. If nobody's average is big enough, it says so and tells you to chunk it down instead.
Between 60% and 70% it wants the biggest Defier hit available, to get out fast.
Below 60% it prefers a clean kill if someone's average can finish the boss; otherwise the biggest chunk.
These refuse to run for anyone whose roles don't include admin / leader / official.
Set your guild's current boss. Do this first, and again whenever the boss moves. Two ways:
/se_boss level:70 percent:41/se_boss score:9.11e18score is your guild's total score from the in-game Guild Rank board. Paste it exactly as shown and zbot works out the boss level and % HP for you — much easier than eyeballing a percentage, especially on the hard sub-50 bosses.
Members log their own hits with used:. You can also log for someone else, by their account number:
/se_hits account:2 used:3 — account #2 used 3 hits/se_hits account:2 set:5 — force account #2 to exactly 5 remainingused: subtracts. set: overwrites the total — use it to fix mistakes, not for normal logging.
Account numbers are shown in the spreadsheet, column A. zbot assigns them automatically.
Starts (or restarts) the event: Day 1, everyone back to 5 hits, reminders and the daily refresh switched on.
Ends the event early: stops the 5 PM reminder and the 6 PM refresh. Stats and everyone's current hits are left alone. Normally you don't need this — the event ends itself after Day 6.
Corrects the day counter if it drifts (a missed refresh, a late start).
/se_setday day:3This changes only the day number. Nobody's hits move. It matters because Day 6 is when zbot stops holding reserves back.
Worth knowing, because you'll be answering questions about them.
The brain. Recommends up to 3 players to send, in order, with the reason for each.
With no options it uses the boss you set with /se_boss. You can also override on the spot:
/se_next · /se_next level:70 percent:76 · /se_next score:9.11e18Each pick shows whether the player is ☀️ awake, 🌙 asleep or ❓ unknown (from their /se_available hours), their average hit for that zone, and hits left. Below the picks you'll see who's holding reserves, who has no Defier for this zone, and who was skipped for having no average recorded.
level/percent/score, the guild's tracked boss is updated too. When a member does it, they just get an answer — nothing is saved. That's deliberate.The quick glance: what day it is, total hits left across the guild, the current boss, and the single top pick.
Lists everyone who still has hits, most first. Add guild:All to see all four guilds at once — handy near reset time.
/se_hitsleft guild:AllHow members feed zbot their stats. Chase your guild on these two — a player with no averages recorded can never be recommended:
defier 70–100%, deadzone 60–70%, aspen 0–59%). This is what the picks are ranked on.gk_defier (no Defier = no hits above 60%) and dies_to_boss50.Point members at the stat setup guide — every field, with screenshots.
You have edit access to one tab per guild: <Guild>_Leaders.
The Hits Remaining column (column E) is the single source of truth for hits. zbot reads it, and everything zbot does — the daily refresh, /se_hits, /se_reset — writes back into it. Edit it and zbot instantly agrees with you.
It's a dropdown, 0–7. Green means 3–7, red means 0–2 (that player is on reserves). Click the cell, pick a number.
/se_update data and is protected — if you try to type in one, Google will warn you. That's working as intended, not a permissions bug.| Column | What it is |
|---|---|
| A — Account # | zbot's number for the account. Use it with /se_hits account: |
| B — Account Name | Their in-game name |
| C — DD | Damage dealer (Aspen / DGN / Other) |
| D — Defier/GK | Whether they can hit above 60% |
| E — Hits Remaining | Yours to edit. Dropdown 0–7 |
| F — Average Hit | Their overall average |
| G, H — Ely HP, HW HP | Survivability on the deep bosses |
| I — Defier Zone Avg | What ranks them above 70% |
| J — Aspen Attack | Attack stat |
| K — Support S Tier | Supports with SOLi |
You won't see the bot's raw data tabs — they're hidden on purpose. Nothing you need is in them.
The rhythm of an actual event.
/se_reset./se_boss score:… off the Guild Rank board — the easiest way to keep it accurate./se_next. Send the top pick. If it says the deadzone can be skipped in one hit, that's the hit you want./se_hits used:1 themselves — or you log it: /se_hits account:7 used:1./se_boss, and ask /se_next again./se_hitsleft guild:All to see who's sitting on hits they're about to lose. zbot pings the guild at 5 PM anyway.The things that actually come up.
Discord's own cache, not a zbot problem. Use the Discord app rather than the browser, and press Ctrl+R to refresh it. It clears on its own.
Nobody has run /se_boss since the last restart. Set it.
Three usual causes, in order: they're down to 2 hits or fewer (holding reserves — normal until Day 6); they have no Defier and the boss is above 60%; or they have no average recorded for that zone — /se_next lists these people explicitly at the bottom. Get them to run /se_avg.
Commands only work in the four -se channels, and you need your guild's role to act in your guild's channel.
Just fix column E in the spreadsheet, or use /se_hits account:<n> set:<n>. Both land in the same place.