Live logs: stream overlay, Discord board and watch page

WoW doesn't let an addon use the internet or read the combat log, so the uploading happens in your browser instead. The game writes every fight to a log file, a tab on ForeverDB reads that file as it grows, and each pull is sent the moment it ends. There's nothing to install: the ForeverDB Uploader isn't needed for this.

What you need

• Chrome or Edge on Windows, macOS or Linux. Firefox and Safari can't read a folder as it changes, so they can only upload a log after the run, on Replay.
• A free ForeverDB account (log in with Battle.net), so your pulls have an owner and only you can change them.
• Combat logging turned on in the game. The ForeverDB addon turns it on by itself in dungeons and raids (its setting Log combat automatically in dungeons and raids, on by default). Without the addon, type /combatlog when you zone in.

Start logging live

1. In Chrome or Edge, open foreverdb.net/replay and log in.
2. Under Live logging, give the run a title, choose who can see the report (public, unlisted or private) and press Choose Logs folder and start.
3. Pick the Logs folder inside World of Warcraft\_forever_ and allow the browser to read it.
4. Play. Keep the tab open: you can use other tabs and the rest of the site. Each pull appears on the report, the overlay, the Discord board and the watch page a few seconds after combat ends.
5. When you're done, close the tab or press Stop. The report stays on your profile with every pull in it.

Where your pulls show up

• Stream overlay: a link for OBS, Streamlabs or any streaming app's browser source. It shows bosses killed, wipes, deaths and damage and healing meters for the last pull or the whole run, with a see-through background.
• Discord board: one message in your raid or dungeon channel, edited after every pull with the kills, wipes, deaths, the last pull's damage and healing per second and who died. A new run starts a new message. It uses a channel webhook, so the ForeverDB bot doesn't have to be on the server.
• Watch page: a private link with an access code for your raid, guild or viewers. It shows the run's numbers, every pull in a strip coloured by kill or wipe, the meters, and the fight map of the newest pull: where everyone stood, who got hit by what and who died, with playback.

Add the overlay to OBS

1. Press Make overlay link on this page and copy it.
2. In OBS: Sources, +, Browser. Paste the link as the URL and set the width to 360 and the height to 460.
3. Options go on the end of the link: ?show=run for the whole run instead of the last pull (both for both), &meter=dps or hps for one meter, &rows=8 for more players, &scale=1.3 for bigger text, &bg=solid for a dark background.

Connect a Discord channel

1. In Discord, open the channel's settings (the cog next to its name), then Integrations, Webhooks, New Webhook. You need the Manage Webhooks permission.
2. Name it ForeverDB if you like, press Copy Webhook URL, paste it on this page and press Save.
3. Press Send a test. A message should appear in the channel. Deleting the webhook in Discord stops the board.

If something doesn't work

• Nothing appears. Check combat logging is on (type /combatlog: the game says whether it's on or off), that you picked the Logs folder and that the tab is still open. A pull is sent when combat ends, not during it.
• The browser won't open the folder. Chrome and Edge refuse folders inside C:\Program Files (x86), where WoW installs by default. Install the game in another folder, such as C:\Games, or upload the log after the run on Replay.
• The overlay says the link was turned off. A new overlay link or watch link replaces the old one. Copy the new one.
• Discord stopped updating. After three refusals in a row (the webhook was deleted or the channel removed) the board pauses. Save the webhook again to restart it.

Who sees what

The overlay, the Discord board and the watch page show what the report shows: the names of the characters in your log, their damage, healing and deaths. Anyone with the overlay link, or the watch link and its code, can see them, even when the report itself is private. Making a new link stops the old one at once. Characters on the hide list stay hidden. Your BattleTag is never shown.

(Making the links needs JavaScript and a ForeverDB account.)