Siegecrafter Blackfuse adds 10 man normal

100 Blood Elf Priest
23980
I highly doubt this is intentional

1. Blizzard doesn't really buff normal bosses, especially not 2 months after patch drops
2. Even if they did, they wouldn't yolo stealth patch it

I just hope that it's back to normal tomorrow, lol
Edited by Alumenlux on 10/29/2013 11:40 PM PDT
Reply Quote
10 Blood Elf Paladin
10
could we see these changes in patch notes, blizzard?

ffs, these arent the kinds of things you just "slide in" with the patch.
Reply Quote
Game Designer
We had made several rounds of tuning changes to the various Siege of Orgrimmar encounters late in the 5.4 PTR process, and some health adjustments that were reverted before 5.4 was released ended up resurfacing in patch 5.4.1. Apologies for the inconvenience -- this should be corrected within the next day.
Reply Quote
100 Undead Mage
13095
We had made several rounds of tuning changes to the various Siege of Orgrimmar encounters late in the 5.4 PTR process, and some health adjustments that were reverted before 5.4 was released ended up resurfacing in patch 5.4.1. Apologies for the inconvenience -- this should be corrected within the next day.


Will this include 25H numbers? Conveyor belt add health went from 30m to 24m today.
Reply Quote
MVP - Technical Support
100 Human Warrior
22100
10/29/2013 11:53 PMPosted by Magic
Will this include 25H numbers? Conveyor belt add health went from 30m to 24m today.

That is quite a sizable nerf. It'll royally screw up this weeks progression for those that happened to raid on wed. instead of tuesday if fixed mid week though :\.
Reply Quote
2 Undead Mage
0
10/30/2013 12:14 AMPosted by Omegal
Will this include 25H numbers? Conveyor belt add health went from 30m to 24m today.

That is quite a sizable nerf. It'll royally screw up this weeks progression for those that happened to raid on wed. instead of tuesday if fixed mid week though :\.

how so? are any guilds that are currently working on siegecrafter actually putting any serious amount of time into him on a tuesday?
Reply Quote
90 Pandaren Shaman
17640
We extended our lockout and put four hours in yesterday on siegecrafter.
With blizzcon coming up next week we have several people going so we won't raid then.
Reply Quote
100 Troll Druid
11200
10/30/2013 12:54 AMPosted by Coneofcold

That is quite a sizable nerf. It'll royally screw up this weeks progression for those that happened to raid on wed. instead of tuesday if fixed mid week though :\.

how so? are any guilds that are currently working on siegecrafter actually putting any serious amount of time into him on a tuesday?


We were last night, but granted it was only normal mode not heroic. In any event, we did manage to get our first kill, but it took probably 2 hours more than it should've as we needed to acclimate 2 new dps to jumping onto the conveyor belt (and more importantly, managing the dismount without falling to their deaths). Many battle rezzes were wasted on that last night :/

Good to know we were still able to beat the encounter after a bit of tweaking, but frustrating to know we could've been spending that time on Paragons; we were extremely close to getting Siege last week and chose to extend. Could not figure out why what was easily manageable for 1 dps last week was now requiring 2.

Tuesday isn't our normal raid night, had to swap from Thursday due to RL scheduling issues, but it's not like Tuesdays or patch days have been the only troublesome nights recently, there have been a TON of technical issues since 5.4 dropped, we've lost a couple raid nights because some players can't log on, or the instance server crashes (this happened to us at the end of the night too, we had to shut it down 15 minutes early when everyone got booted from instance servers).

Very frustrating when you only raid 2 nights per week, Blizz!
Reply Quote
90 Draenei Hunter
9320
That is quite a sizable nerf. It'll royally screw up this weeks progression for those that happened to raid on wed. instead of tuesday if fixed mid week though :\.


Confused by your logic here. Why would reverting it to its intended health "royally screw up this week's progression"? You would be using the same conveyor strategy you used prior to the accidental 20% nerf.
Reply Quote
100 Dwarf Hunter
23545
10/30/2013 08:28 AMPosted by Subrosian
You would be using the same conveyor strategy you used prior to the accidental 20% nerf.

They mean anyone who killed it for the first time this week before it is fixed would suddenly run into problems on the fight again next week. Whether that counts as "royally screwing up" a week of progression or not is a personal judgment.
Reply Quote
90 Draenei Hunter
9320
You would be using the same conveyor strategy you used prior to the accidental 20% nerf.


They mean anyone who killed it for the first time this week before it is fixed would suddenly run into problems on the fight again next week. Whether that counts as "royally screwing up" a week of progression or not is a personal judgment.


Two guilds killed it in 25 Heroic, so Omegal is correct, this is a major screw up. I don't like this situation at all - either Blizzard reverts the 20% health nerf, in which case they just handed two guilds easier kills and changed the race dramatically (as unlike Norushen, Siegecrafter matters quite a bit) .... or they leave the nerf, in which case they arbitrarily nerfed one of the more challenging, interesting 25-man encounters due to a technical slip-up.

Ugggh. The botch-ups this tier are starting to add-up to an impressive total. Norushen overhaul (wtf...), Galakras locking-out raid groups in 25 Heroic, and now this... bleh.
Edited by Subrosian on 10/30/2013 9:45 AM PDT
Reply Quote
100 Worgen Druid
13370
Some people are reporting an increased health pool on Iron Jug on 10 man heroic. Was that also affected by this accident? It felt like we needed more damage this week to get past him barely on enrage with healers dpsing while last week that wasn't an issue at all.
Reply Quote
100 Troll Rogue
21875
I believe two guilds got their kill last night in 25-man Heroic.

Doesn't look like anyone killed it last night. WoWProgress has the kills recorded at 4AM on Tuesday which would put it before this reset. Additionally if you look at the activity logs of players in both guilds you'll see that they have early SoO heroic kills in their activity log after their siegecrafter kill indicating that they killed it last lockout.
http://us.battle.net/wow/en/character/korgath/Purge/feed
http://us.battle.net/wow/en/character/arthas/Paloro/feed
Edited by Fierydemise on 10/30/2013 9:50 AM PDT
Reply Quote
90 Human Priest
0
looks like this is getting fixed right now...

https://twitter.com/devolore/status/395604571910701056
Reply Quote
2 Undead Mage
0


They mean anyone who killed it for the first time this week before it is fixed would suddenly run into problems on the fight again next week. Whether that counts as "royally screwing up" a week of progression or not is a personal judgment.


Two guilds killed it in 25 Heroic, so Omegal is correct, this is a major screw up. I don't like this situation at all - either Blizzard reverts the 20% health nerf, in which case they just handed two guilds easier kills and changed the race dramatically (as unlike Norushen, Siegecrafter matters quite a bit) .... or they leave the nerf, in which case they arbitrarily nerfed one of the more challenging, interesting 25-man encounters due to a technical slip-up.

nah, dread and static killed it monday night.

even in the bugged state, from what i read, belts were nerfed by 20% but boss's health was increased by 8%, so it wouldn't be a huge deal anyway, even if anyone got to it in that state? taking 1 person off every belt is (very roughly) the equivalent of +8% boss damage anyway. although i guess you would have been able to remove your worst belt people from the belt, which is nice.
Edited by Coneofcold on 10/30/2013 11:53 AM PDT
Reply Quote
90 Blood Elf Priest
16465
even in the bugged state, from what i read, belts were nerfed by 20% but boss's health was increased by 8%, so it wouldn't be a huge deal anyway


last night, belt was at 24 mil (instead of 30)
boss hp was the same, 1771 mil

and the boss was dropping way faster than before.

and yep, we killed it monday night, before the "bug"?
Edited by Popsickelz on 10/30/2013 12:29 PM PDT
Reply Quote
2 Undead Mage
0
ah ok, guess my source on that was wrong.
Reply Quote
90 Orc Hunter
17370
10/30/2013 09:35 AMPosted by Subrosian


They mean anyone who killed it for the first time this week before it is fixed would suddenly run into problems on the fight again next week. Whether that counts as "royally screwing up" a week of progression or not is a personal judgment.


and changed the race dramatically


lol

the race
Reply Quote
90 Draenei Paladin
15175
Has the issue been resolved?

My team and I ran in there thinking we can just throw one person on the belts as always, come to hear "oh, that's not good" from one of our belt killers, followed by the bosses shield, followed by wipes. Luckily we only lost 30 minutes of raid, hopefully it's fixed by the time we raid tonight.
Reply Quote
90 Undead Mage
10845
10/30/2013 01:21 PMPosted by Xtrm
Has the issue been resolved?


Should be fixed already.

https://twitter.com/devolore/status/395604571910701056

One can only hope!
Reply Quote

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)

Reported!

[Close]