Quick patch to clean up a few things from the past couple of days and add some improvements we've been meaning to ship.
A note on yesterday's hiccup
Yesterday we had to scale up our servers to handle the traffic spike from raid week. During the upgrade there was a roughly 8 minute window where some pages didn't load correctly. Everything has been stable since, and we've pushed a fix that automatically clears any leftover issues on your next visit.
If anything still feels off (pages not loading, getting redirected weirdly), clearing your browser's cached data should sort it out. In Chrome: Settings > Privacy > Clear browsing data > Cached images and files. You don't need to clear cookies or anything else.
Roster Refresh Confirmation
When refreshing your roster from the guild, players that aren't in the fetched roster used to be silently removed. Now you'll get a confirmation dialog listing exactly who would be removed, with the option to keep them or remove them. No more accidentally losing manually added players or alts that aren't in the guild.
Improvements
- All Raids combined view: Insights and Stats tabs now default to showing all bosses across every raid in the tier instead of locking you into a single raid. You can still filter to a specific raid if you want.
- Auto-difficulty switching: If your selected difficulty has no data (e.g., you're on Mythic but only have Heroic logs), the app now automatically switches to the best available difficulty instead of showing an empty page.
- Gear spec overrides: The Gear tab now respects roster spec overrides. If you've set someone to a different spec in your roster, their gear analysis and role grouping will use that spec instead of whatever they're currently logged out as.
- Normal difficulty removed from filters: We only process Heroic and Mythic data, so the Normal option has been removed from the Insights and Stats difficulty selectors to avoid confusion.
Bug Fixes
- Fixed boost tier not updating immediately in the sidebar after allocating or removing boosts
- Fixed a database connection issue in the boost service that could cause data to be read from the wrong source
- Fixed collaboration server stability issues
As always, feedback and ideas are welcome in Discord.