What it does
RunBook starts on its own when you zone into a dungeon or raid and records the run. Your history keeps per-dungeon stats and best times. If your partner runs it too, each log also shows the other's gold, XP, drops and notes.
- Starts on its ownZone in and a run starts. Step out alive for repairs and come back within 30 minutes (2 hours for raids), or do a corpse run, and it's the same run. Time outside doesn't count, except up to 10 minutes running back as a ghost.
- Clear times and boss splitsEach boss kill with its split against your fastest clear: green ahead, red behind. Splits start on your second run of a dungeon; raids wait for two nights ending on the same boss.
- Deaths, wipes and dropsDeaths with names, wipes, and the latest drops: yours and your partner's from green up, other players' from blue up. In a raid, only your own and your partner's deaths and drops are counted (a run's details add a count of everyone else's deaths).
- Gold and XP per runYours, your partner's and a Together total, with per-hour rates after 5 minutes. Gold is coin plus the value of items you got inside.
- History and dungeon statsThe last 200 runs with full details, and a Dungeons tab with stats for each dungeon: runs, clears, best and average clear, gold per hour, XP per hour, deaths per run, wipes and blue and epic drops. All your characters share one history.
- Duo syncEach of you sends your gold and XP, notable drops, boss kills, notes and any reset you saw, so a kill one of you missed while dead or outside still counts.
- The Group tabEveryone in your group or raid, most gold first, with gold, XP and rates from each player who runs RunBook. It's for showing only: other players' numbers never change your run.
- Instance cap"Instances 3/5 this hour", and the day's count once you're within 5 of 30. It assumes Classic's limits, which are unconfirmed for Forever, and you can change them.
- Notes and fixesNotes on any run (a note on your current or last run syncs to your partner), boss kills marked by hand when the game doesn't report them, and commands to fix mistakes: take back a boss mark, delete a run, or reopen one you ended while you're still inside.
- Ready for a reported Forever client issueThe Forever beta client has been reported to sometimes fail to load add-on data. RunBook keeps two copies of your data, merged at every login, and warns you when a load fails (unless both copies fail at once, which looks like a fresh install).
/runbook backupcopies all your runs and settings as compressed text, and/runbook restoreputs it back.
Display only, no automation. RunBook reads what happens and shows it. It never casts, targets, moves, loots, rolls, resets or clicks anything for you.
Playing as a pair
Both of you install it. Until you set a partner, RunBook picks one on its own: the first RunBook user you're in a two-person group with (not someone you first heard in a bigger group), or a friend in game (friends list or Battle.net) who runs it, in a group of any size, about half a minute after you hear from them, as long as they're the only friend of yours in that group running it. You get a chat line either way. To be sure, set each other:
/runbook partner <name>Your partner, on your realm/runbook partner <name>-<realm>Your partner, on another realm
When your partner is a Battle.net friend and plays another character on the same account, your log follows them there.
First time in game: a 5-minute check
RunBook was tested against a simulated client. On Forever itself:
- Type
/runbook debug on, then run a dungeon with a boss or two. - Type
/runbook check. It shows whether Forever reports boss kills to add-ons, whether loot lines and resets can be read, and whether sync is working. - If boss kills aren't reported, mark each boss as it dies with
/runbook boss <name>or the "Mark a boss kill" key binding. Let one of you do it; the other's log gets it through sync.
What it sends
Add-on messages go to your party, raid or instance group only, never to whispers, guild or public channels, and only while sync is on. If you two run different versions, you both get a one-time message and sync stays off until you match. Every message carries RunBook's sync protocol number, a random tag for your session, and the dungeon's map ID, name, wing and start time. On top of that, each kind carries:
| Message | Contents |
|---|---|
| Stats | Your run's time, coin, loot value (vendor and auction), XP, kills, and whether it ended |
| Drop | The item ID, count and quality of a notable drop, and when it dropped |
| Boss | The boss's encounter ID and name, when it died, and when you entered |
| Note | The text of a note you add |
| Split, new run, reset | That you came back in, started over, or saw a reset message (with the dungeon's name) |
Nothing else is sent: no character details, no location outside the dungeon, no history. Separately, /runbook report party (or raid, instance, guild, say, or a whisper) posts the run summary and blue-or-better drops to chat, only when you use the report command.
Commands
/runbook help lists every command.
/runbookShow or hide the live window/runbook historyThe history window (/runbook statsand/runbook groupopen the Dungeons and Group tabs)/runbook note <text>A note on this run, or your last; syncs to your partner/runbook boss [name]Mark a boss kill by hand (also a key binding)/runbook unbossTake back the last boss kill/runbook endEnd the run now (/runbook startreopens it,/runbook newstarts over as a new instance)/runbook reportThe run summary and blue-or-better drops, just to you; add party, raid, instance, guild, say or a whisper to share it/runbook exportThe last 200 runs as CSV in a copy box, for a spreadsheet/runbook partner <name>Who you sync with/runbook cap [n/off]The instance cap per hour (/runbook cap dayfor the daily one)/runbook backupAll your runs and settings as text (/runbook restorepastes it back)/runbook checkTroubleshooting: what your client supports and what RunBook can see
Good to know
- No combat data: boss kills come from encounter events, and deaths from the death event (yours) and party frames (others).
- Gold is what the run brought in, not profit after repairs, ammo or potions.
- Time inside counts even when you're away from the keyboard. Hunter pets' deaths aren't counted.
- Forever hides creature IDs inside instances, so an add-on can't tell two copies of a dungeon apart. RunBook catches resets from the reset message (sync passes it on) and from a named boss dying twice. Otherwise, type
/runbook newafter a reset. - Dire Maul's wings can't be told apart: type
/runbook newwhen you switch wings.
Install
- With an add-on manager: in the CurseForge app or WowUp, search for Vulcan RunBook and install it for World of Warcraft: Forever.
- By hand: download the zip (the Download button above), unzip it, and copy the
VulcanRunBookfolder into theInterface\AddOns\folder of your Forever game folder. To find it, open Battle.net, select the Forever game, click the gear icon and choose Show in Explorer. - Turn it on: at the character screen, click AddOns and make sure Vulcan RunBook is ticked. If it's greyed out as "out of date", tick Load out of date AddOns.
- Playing as a pair? Both of you install it.