Share a raid report

Every report has one address: logbreakdown.com/logs/ followed by the id of the log. Whoever has it can read the report in a browser, no account needed. Sharing is pasting that address in Discord.

Copy the link

The Share button at the top right of a report copies its address. The Fights menu at the top picks the whole night, one raid, or one boss. Each raid has its own page, /logs/…/BT for Black Temple, and the button copies the page you are on, including the open tab and the selected fights.

Link straight to a tab

The open tab is part of the address, after a hash. Copy the link while a tab is open and it opens on that tab for the next reader. Bare #trash is the CLA trash-requirements tab. RPB trash is #scope=trash, below.

Link straight to a fight scope

The selected fights are in the same hash (scope=…). Boss kills is the default and is left off, so #combat is In combat on boss kills. When a tab is in the hash, scope comes after an ampersand: #combat&scope=night opens that sheet on the full raid. One boss is scope=boss: followed by the encounter id; pick the boss in the menu and copy, the report writes it.

More on what each scope sums under Reading a report.

Who can read it

Everyone. Every report on Logbreakdown is public: anyone with the link reads it without an account, it is listed on the site and turns up in the search box, search engines may index it, and it may be shown as the sample report on the front page. There is no visibility setting to pick, at upload or afterwards.

As the owner you have a Settings button at the top right of the report, next to Share, with the title and the raid team. The same dialog deletes the night, parsed log and all: deleting is the only way to take a report off the site, and it takes effect the moment you confirm.

Post to Discord automatically

A raid team can carry a Discord webhook. With one set, every upload for that team posts an embed to the channel: the title with the link, the team, the instances and the date, then the night in numbers: kills and wipes, time raided and share in combat with the longest break, potions per raider and kill, consumables at pull, deaths with the three who died most, and how many CLA checks came out red and yellow. Those counts are the same checks as the To fix line on the report: gear to talk about, cheap gear, consumables under 80 % of pulls, missing drums, and unmet trash. Nobody has to paste anything.

1. In Discord, open the channel settings, then Integrations, then Webhooks. Create one and copy its URL.
2. In Logbreakdown, open Raid teams from the dashboard. On the team, press Edit name and Discord, paste the URL and save. No team yet? New team asks for the same two things.
3. Choose what happens on a night with several raids: one message for the night, one message per raid, or a question after each upload.
4. If another officer also uploads, open People on the team, create an invite code, and send it to them. They paste it under Join with a code. Their uploads use this webhook and these CLA lists. They never see the webhook URL.

Already uploaded? Settings on the report has a Post to Discord button that sends the same embed. Raid teams shows what each option looks like in Discord, and every team with a webhook has aTest the channel link that posts a hello before the first upload.

Raid teams

Every night you or an officer attach to the team builds the team page: who was on which pulls, and the last weeks of potion windows, deaths per pull and consumables per raider. Merge an alt into its main there; nothing on that page is a score.

What the link shows

Character names as they appear in the log, with class colours, and everything the CLA and the RPB computed. If the night belongs to a raid team that has copied the CLA lists, visitors see that team's rules, the same colours as the owner, not CLA's defaults and not the viewer's. There is no account name and no e-mail on a report. A log names everyone who raided that night, and the report is public, so do not upload a night the people in it would not want shown.