That also makes sense @Meeeeeeeeeeeeeeeshka why the nerf happened.
Boss 3:
Assuming that is what they are referring to.
I thought the sun-bombs did adequate damage on 4/17. They did a lot of damage but was doable. I’d be willing to face off an increased damage sun-bomb and see how it feels though.
I agree with tbuzz was very easy to kill
I agree 100% except you may want to when you’re changing it back please make the chains start ticking for damage 5 seconds after they place or something because as of now if a chain and pool spawn on you at the same time its basically a 100% chance of death
Boss 4 is not in a playable state. Every sky AOE we had in our raid had at least 1 person not seeing one or both of the aoes. With having to jump out of 2nd aoe there is just not enough time to take care of orbs and adds. We think adds are overtuned and we need a fix for the sky aoes or it will just not be doable consistently due to visual bugs.
Yeah with how the sky seed thingies that fall from the sky are just being so inconsistent its literally impossible
the reason its impossible isnt the player its the game with whatevers happening there
Quick update: We fixed the bug with boss 2 that was causing it to not do all the mechanics as intended. The boss should be back to its usual difficulty now.
He is still broken in terms of doing all mechanics at the same time when he reaches 25% health. If this is intented it basically makes it impossible at the moment without god tier dps AND nobody dying until then. He rushes, jumps, and places the pools on chains at the same time (he did this twice in a row on our longest run which got him below 25% so I doubt its coincidence).
Had it today were the boss is under 25% health, chain spawns with pool, chained person jumps and then immediately dies because the boss has jumped on them. theres no time to regain stamina or even react if you did have the stamina to jump again.
The boss is only getting taken down with insane dps burning it.
Edit for clarity: im talking about boss 2
In the mini DLC the spider boss has an actual jump animation, why does boss 2 not? One example: Today he chained me and in under a quarter second jumped on me, instantly killing me. There’s also getting double pooled + chained, although an attempt could be argued for positioning in this case. That said, the pools are enormous.
What makes boss 2 a struggle are the insta kill bugs/mechanics. It’s not a fair fight, there’s nothing you can do when it happens & very close to nothing you can do to prevent it from happening through legitimate gameplay. For the double pools, it’s also kind of random. No animation or cast bar to spawn it / etc … its just a weird mechanic. The chain pool is atleast tied to something.
Beyond that, the flow of the fight is there. Originally he was kind of a chase everyone around the map & jump fight. Now he is very coordinated similar to boss 1. I think expanding on his first iteration, throwing chaos in the mix, jumping around more, etc, would have made a more interesting fight. But I’ll take him as he is, just fix the unavoidable insta kills lol.
Besides the insta kill bug, leather is noticeably more survivable than cloth on this fight too while being chained. Specifically the musky shield doesn’t have to be at literally 100% to soak with 3 people w/ full hp too (using aged enhanced vit pot). Normally I’d think this is okay in an MMO but it’s the first time I’ve ever noticed on Orbus in a raid lol.
I guess this was reverted? His rotation itself seems consistent but the timing between types of actions is super inconsistent.
Boss 2 is definitely a pain, he’s certainly killable, we’ve taken him down a couple times since the changes landed. It’s just a meat grinder of a fight, you just have to hope you aren’t losing crucial players To the instant kills before you’ve lost enough dps to finish him. I couldn’t begin to guess what needs to be fixed to balance him, it’s still so chaotic. One suggestion that springs to mind, If he didn’t get a massive damage reduction during his charge phase it might give players a chance to burn him through his murder phase at 25% , seems odd that the hardest time to hit the boss is also a dps stop, shouldn’t people be rewarded for landing hits while he’s charging around the room? A damage increase seems more fitting in that situation, reward skilled players for hitting the moving target and give us another strategy to kill him, simply burning him down while players kite
Indeed he is killable, but he’s to RNG. as you state: ‘‘You just have to hope you’re crucial players don’t get killed’’.
I also think that Boss 2 is very annoying. Given that boss 1 has 0 DPS checks and if you do the mechanics you’ll beat the boss, and Boss 3 has the Consume Add DPS check, it feels strange that the current strat is assume everyone will be picked off one by one going into the rampage phase.
The mechanic that feels like it needs to be tweaked for me is jumps below 50%. Honestly everything else seems manageable as a mechanic.
Here are my suggestions for fixing the jump below 50%.
Requiring people to be stacked between 0 and 3 seconds ish + having massive AoE insta murder pools (when stacked) is a big part of the issue. Chain targets are at increased risk because the spawning in double pools will be extremely more likely to kill them, although everyone will probably die within it (it comes down to armor type & musky shielding). Multiple damage sources = no unbending either.
For example, you could chase the target the boss is following around the map as a group, with chained people be more towards the center of the map as to not damage people. This keeps you clumped for a 0 second jump. However, at any moment, he could double pool and murder most/all of the group.
There’s no way to be clumped & not clumped. If you split into groups of 3, all people must be topped off & shielded. Cloth will die without 100% shield, 100% hp, and aged enh vit pot (I also mana shielded), leather get slight but not much leeway. Any chain targets will not be topped off/not max shield(killing cloth on the jump with 1 tick of chain dmg to their shield). You can’t pre-heal or pre-shield chained targets because the chain is doing constant dmg, so a musky must hit at the very last half second possible. Theoretically a musky could nail it 100% the time, but probably not. So, lets assume every time here 0-2 chain targets die every 30 seconds. Then every 30 seconds pools happen, and probably insta kills 0-4 players from 2 groups, or wipes an entire single group of 3 people. If you’re not double pooled, and not chained, you get saved by unbending once here. Otherwise you will die with unbending.
If a musky dies as one of those people, the group probably dies too. If you can’t kill the boss in under 60-90(unbending luck) seconds from 50%, the group probably dies. This is while the boss is chasing players around being harder to hit, taking reduced damage, jumping, while you may be repositioning yourself. The only way to really burn him would be to wait at 51%, let mechanics go off, then unleash maximum DPS, letting people die until 0%.
–
How 2 fix:
This boss is probably doable without random animationless instant unannounced double pools. But they are such a non fun nuisance / wrench in the gears that I question their very existence. They seem like a bug tied to jump pools tbh. I’d argue to alter/remove them & add a different mechanic. A complete removal of random pools probably makes the boss easy, but right now they don’t make the boss hard they make it dumb. Pools after jumps are fine. Also fix the timing between actions so he doesn’t chain then insta jump or pool. If you add a way to know who is going to be pooled seconds ahead of time, then don’t have him instant chain right after so they can drop the pool & get back to the party within a reasonable amount of time if they were paying attention. If you remove the random pools and add something else then I’d have to see it lol.
It’s the random 0 seconds between actions, and it’s the dichotomy of be grouped but don’t be grouped or an instant unannounced huge AOE will instantly kill the entire party or a significant portion. Sometimes his actions have reasonable delays, but throughout the fight the actions stop synchronizing and he’ll begin doing things back to back.
–
I suppose maybe if each group has 1 musky they can try to keep their 3-split alive and also get 1 brez. But nothing can stop a double pool from instantly killing the group together. They’d have to split in an area large enough to not get double pooled with the center teammate, then rejoin on chains for a jump, as long as the boss doesn’t instantly jump lol. I’m also thinking ranger DPS only because cloth just isn’t worth it, in terms of surviving the fight legitimately and not burning. Shamans must be super S.O.L for this fight too lol. The issue is shielding. Jump damage is immediate and I don’t remember seeing a cast bar / any warning. You could count seconds except that there is no set # of seconds to count. Furthermore considering cloth need to be healed/shielded within 0.5 seconds for a group of 3 the timing is very important lol, plus latency.
The other potential option is create two enormously spaced lines of players on both sides of the boss, each group w/ 1 musky, slowly working inwards to prevent double pooling / running into a pool later. More players might also allow cloth to survive here, except 99% chance they still die instantly to getting single pooled & chained with no delay. idk if the group has to follow the chased target, might have to. I also don’t remember if you can be double pooled while chained/waiting for a jump. Top the group off while on top of the chained target to survive the jump. Idk maybe yeet your turret to heal people super far away so they don’t die to pool/chains in the next round after taking jump dmg. Or possibly, regroup again after a jump, heal, then break back into a line. Stand on the edge of your last pool to conserve space. Tanks can fill in for jumps during chases. If one side dies too much, a DPS can swap sides. You need a musky + 2 others to survive a jump, at minimum.
– What am I saying. Chug a heal pot after each chain lol. Not sure the CD, I never use them.
Lastly, always let the jump target die after 50%? Potential for that. lol. Stay split, don’t let pools overlap. Chug a pot or get healed later. Immediately heal chain targets, and 1 will die. B-res.
If as a strategy you have to rely on good RNG to kill it before all players die then it is not a good boss. Is it killable? Absolutely (if you are willing to grind for multiple hours if you get bad jump RNG)! But that does not make the boss hard, just unfair at 25% hp due to him still doing everything at once.
Every good boss should be able to be done without sacrificing players and should be able to be killed 100% consistently provided everyone is playing well. At the current state you are garunteed to lose players at 25%. Getting to 25% can be consistent as long as the dps follow specific strategies but afterwards it is guaranteed to kill at least 1 player due to him doing everything at once.
He honestly should probably hit harder, rush more often, and jump more often. Just not like we have it now where everything lines up with eachother making surviving using any type of strategy useless.
Boss may be killable by groups who are willing to grind for hours upon hours but this makes the raid completely impossible for those who do not have the time to grind for good jump RNG at 25%. This boss was too easy on release and is still broken even now. Its better than it was when the buffed it initially but it is still RNG dependent like he was when he was initially buffed (which is what the fix was supposed to do: Not make him do everything at once like he is still doing).
If the devs really don’t want to change what he does at 25% I can agree with making him take more damage during rush so players have an actual chance at killing him consistently (albeit players dying to unfair mechanics)
I think im just not going to bother with hard mode citadel at least until its fixed, boss 2 and 4 are so broken
An bug I find with boss 2 is the animations. He animates depending on speed, we try to slow him on rampage phase, that leads to the normal walk animation showing rather than his charging rampage.
So how do we know if his on rampage or not? I’ve seen multiple tanks get killed by rampage because they thought it wasn’t doing it or even worse now, think it might be rampaging and run without any way to tell.
The boss needs to be consistent in animations for what its doing no matter his speed. Rampage has his shoulder to the side running animation, non rampage has his waddle walk.
Boss 3 bug: the adds from the sky cogs spawn even when it shouldn’t when cleared by the poison sun glow above people heads.
These 2 specifically always spawn adds. these are both in corners and close to rocks, hopefully I got the position right. might be 1 more that does this too but not 100% sure.
Thinking about boss 2, if the boss jump didn’t go to chained people and chained people had roughly a 3 or 5 second indicator debuff to show the chains are coming we could with skill manage grouping up, pool placement and chained people being healed.
People without chains - all group together ready to soak the boss jump damage and then jump out the pool.
People with the debuff - Panic, run away from the group, stay close enough so that healers can keep you alive, position so that the pool is in a good place and jump the pool when it hits.
Tank - live your life freely as you have about 5 seconds of freedom before the boss comes to kill you again or worse rampage, possibly hamstring if your a warrior pre jump or stun lock as pally if that helps?
…I think that would fix the RNG of everything and the fact we are guaranteed to lose 1 person each jump at the moment. Thoughts?
I thought that the citadel hard mode was supposed to be done by people with god tier dps and not by people who play casually
I think he ment its only doable with dps from 100k+, and there arent a lot that can pull those numbers unboosted
Everybody that pulls 100k is doing it boosted. If you’re in a Hard Mode raid, you should ABSOLUTELY be boosted. That’s the hardest content in the game lol
