Scorp

From the information I have gathered -> 15 seconds after the encounter starts, and then every 70 seconds boss sends in 4 players. The combination of roles seems to be the following: - 1 Tank, 1 Healer, 2 DPS - 0 Tanks, 1 Healer, 3 DPS - 1 Tank, 0 Healers, 3 DPS - 0 Tanks, 0 Healers, 4 DPS After checking multiple videos, it looks like the encounter tries to cleanse 1 tank, 1 healer and 2 dps in an ideal case (except for first round -> tank is not sent here). Targets for each group are selected based on their corruption level (the higher the corruption, the higher the chance you will be selected). If there are no tanks or healers to be selected, these slots are filled by DPS (only with condition that there is someone remaining with corruption). In case less than 5 players are alive -> nobody is selected (to prevent the encounter from evading)

Fixed, will be applied after update

Currently most of the MOP encounter bosses, which do not move entirely or during a phase, few examples - https://db.pandawow.me/?npc=60491, https://db.pandawow.me/?npc=60410, https://db.pandawow.me/?npc=60999, https://db.pandawow.me/?npc=62980, https://db.pandawow.me/?npc=72276, https://db.pandawow.me/?npc=71734 have the following logic: If main threat target is out of melee range -> check nearest players and validate if one of them is in melee range: 1) If condition is true -> aggro on one of these players 2) if condition is false -> use the "no targets in melee range" mechanic, which in this case is https://www.wowhead.com/spell=144774/reaching-attack Any information if this behaviour, which you have described is the expected just for this boss or other bosses as well, which share the same behaviour?

Nothing to announce yet for upcoming weekly reset, but we'll explore possible changes to current instance lockout system. It includes more than just lifting the restriction to switch between 10 & 25 man difficulties, but only after the preparations for patch 5.4 release are done

Fix will be applied tomorrow together with update

Not exactly, 12:08

Time was changed from 8:00 to 14:00, we just forgot to modify the information in this specific forum thread. Change was done in other threads + announced on Discord

Neff solved the client crash. Will be applied after restart

Thanks for the report, the fact that you could see this quest at some point was indeed a bug, raid weekly rare rotation will start tomorrow as described here - The first rare to appear will be https://db.pandawow.me/?npc=69843

Fixed, will be applied after update

Throne of Thunder Loot system changed. Here is what you can expect starting from next weekly reset: Default Case (nothing changed here): 2 Items on 10 Man Normal / Heroic | 6 Items on 25 Man Normal / Heroic. Two Possible Scenarios: - If boss does not have any Tier Set Tokens in Loot Table -> all loot slots are filled by equipment from boss loot table; - If boss has Tier Set Tokens in Loot Table -> half of the loot slots are filled by equipment from boss loot table, while other half is filled with Tier Set Tokens; - Cosmetics (Mounts / Pets) use additional loot slot, drop chance is low, so these items are not seen every kill; Sharded-Loot System: Once loot is generated, every item dropped by the boss (except for Tier Set Tokens & Cosmetics) has a low chance to be replaced by an item from Shared Encounter Loot Table according to raid difficulty (Normal, LFR, Heroic). The chance that this will happen depends on raid difficulty - an individual item to be converted has a higher chance on 10-Man, than 25-Man, but less than LFR. This system does not apply to Ra-Den. Thunderforged & Heroic Thunderforged (same for Warforged & Heroic Warforged): Once all the items are known, there's a 25% chance on 25 Normal / Heroic and 10% chance on 10 Normal / Heroic that the item will be converted to an upgraded version. These rules will also apply to Bonus Loot, only difference is that player's loot specialization will also be taken into consideration. And few more things starting from next week. Currently these things were gated behind Patch 5.3: - Throne of Thunder Weekly Rares (Each week a different rare will spawn replacing some of the instance trash mobs); - All Heroic Thunderforged items are now available to drop from bosses. Currently, some are restricted to drop only in Patch 5.3

Before releasing this system there is still 1 thing where I lack the information for now. Maybe someone can help out with that. So the question - Were "Heroic Thunderforged" items available to players in Patch 5.2 or 5.3? There's some conflicting information around multiple sources that were checked, for example: - https://www.wowhead.com/item=96991/greatsword-of-frozen-hells (Added in patch 5.3.0 "Escalation") - https://www.wowhead.com/item=96918/rune-of-re-origination (Added in patch 5.3.0 "Escalation") - https://www.wowhead.com/item=96794/shattered-tortoiseshell-longbow (Added in patch 5.2.0 "The Thunder King") #Edit: My question got answered, will finish what remains to do here. Thanks Jegerm

The way it works now: - There are 6 fixed spawn points; - Each spawn point periodically summons equal amount of cranes; - Each Crane inflicts 1.56mil - 1.64mil (10 N) / 4.87mil - 5.12mil (25 N) to target-> https://db.pandawow.ru/?spell=138318 (Will double check this part) Effect radius -> to be reviewed

Personally, don't see any issue with selecting Ice Wall or not being able to hit it as melee. Would need more information on that. The way https://db.pandawow.me/?spell=135695 works now is the following - base damage on 25 Normal is 1'000'000 at Conduit Level 1 And 0 Energy (https://db.pandawow.me/?npc=68398). This value increases as your raid team increase the energy / level of North conduit. So for example if you decide charge it to level 2 and leave it at 40 energy the total damage will be: (Base Damage * North Conduit Level) + (Base Damage / 100 * North Conduit Energy) = (1'000'000 * 2) + (1'000'000 / 100 * 40) = 2'400'000. Other three conduits work in a similar way, if you have valid information which suggests this is wrong please open a new ticket with all the details

Similar case as described here. Normally, should be fixed as well