View Issue Details

IDProjectCategoryView StatusLast Update
0019414Return of ReckoningGeneralpublic2024-02-03 01:23
ReporterReturnOfReckoning Assigned ToVegetaplays  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0019414: [Bastion Stair] Zekaraz the Bloodcaller Bugged
DescriptionReporter: Caduceus42

Greetings,

Yesterday my group and I had great difficulty in Bastion Stair on Zekaraz the Bloodcaller.

This is the 3rd boss of the middle wing, and it requires the party to take skulls to an altar in order to reset an increasing damage bonus he gets.

What was happening is that the mechanic of taking the skulls to the altar was on a cooldown where the altar could not be interacted with for a long period after a skull was used. That was so long that it increased the boss's damage too high (well over 100%) for our party to handle and it would eventually result in our tank getting 1-shot every time we tried it.

I have done this boss many times, and I do not recall observing this behavior in the past. I have observed this behavior more recently, however due to the party compositions our party was still able to complete the instance. We tried this with different people carrying the skulls, to ensure it was not a user-error.


**Expected Behavior:**

A member of the party can take a skull to the altar whenever the party feels the damage is getting too high.

**Observed Behavior:**

Dropping the skull on the altar seems to have a significant internal cooldown, that would lead the boss's damage increase to be well over 100% before a second skull could be brought to the altar, and the same internal cooldown was in place for the third, and so forth.


I can supply video evidence if necessary, but that will have to wait until next week's Bastion Stair.

Thank you!
TagsDungeon: Bastion Stair, World Object

Activities

ReturnOfReckoning

ReturnOfReckoning

2023-08-13 04:28

reporter   ~0036179

Commenter: Gunlingers

''A member of the party can take a skull to the altar whenever the party feels the damage is getting too high.''

You have 3 Skulls max for that Dps race. And normaly you put a skull in at 75%, 50%, 25%.
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 04:28

reporter   ~0036180

Commenter: Caduceus42

>
>
> ''A member of the party can take a skull to the altar whenever the party feels the damage is getting too high.''
>
> You have 3 Skulls max for that Dps race. And normaly you put a skull in at 75%, 50%, 25%.

That may be so, but I don't think the cooldown on the skulls is intentional. This bug is occuring before 3 skulls are used.

When we played, the first skull worked as expected, but the second skull will not work (the altar cannot be interacted with) until a certain time has passed. By the time it worked, the damage buff would already be way above 100%, somewhere in the realm of 130-150%, which is when the fire puddle started one-shotting our full Sovereign tank.
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 04:28

reporter   ~0036181

Commenter: dkoerner85

The fire puddle is not the thing one-shotting the tank, it's Ardent Breath (the fire breath). At the beginning of the encounter it usually does one hit for around 800 damage, but as damage increases I have seen it hit for up to 6 times with 2500 damage per hit.
ReturnOfReckoning

ReturnOfReckoning

2023-08-13 04:28

reporter   ~0036182

Commenter: Zomega-WAR

I forgot to report this at the time but it's been bugged for weeks. 1st skull will reset the boss's damage bonus, the skulls after that do not. I can confirm that it doesn't matter who runs the skulls, and I've had an instance where we even tried changing people between skulls (person A does skull 1, person B does skull 2), and that didn't work either.

Issue History

Date Modified Username Field Change
2023-08-13 04:28 ReturnOfReckoning New Issue
2023-08-13 04:28 ReturnOfReckoning Tag Attached: World Object
2023-08-13 04:28 ReturnOfReckoning Tag Attached: Dungeon: Bastion Stair
2023-08-13 04:28 ReturnOfReckoning Note Added: 0036179
2023-08-13 04:28 ReturnOfReckoning Note Added: 0036180
2023-08-13 04:28 ReturnOfReckoning Note Added: 0036181
2023-08-13 04:28 ReturnOfReckoning Note Added: 0036182
2024-02-03 01:23 Vegetaplays Assigned To => Vegetaplays
2024-02-03 01:23 Vegetaplays Status new => closed
2024-02-03 01:23 Vegetaplays Resolution open => fixed