Vangy wrote: »

Synozeer wrote: »

The huge healing ticks are still there. Images from today on my templar.




Welcome back, Cancerplars.

Im confused..... It says 1.2k hps from harvester.... So if its supposed to heal for 7k per 4 seconds with 6 secs ICD, that is about 50-60% uptime... So 7k/4 = 1.75k hps and with about 50-60% uptime --> 1k+ which seems about right no?

I wasn't in the thick of things for much of that combat, so harvester wasn't active for the majority of the fight. I was only showing the FTC report so people could see the average and highest healing ticks along with the CLS combat log showing the same thing.

Interesting, looks like the most important bug didn't get fixed.

In before working as intended.

If it were me, until the bugs can be fixed, I would code in a simple hard-cap on the heal received by the set, to mitigate the issues.

Vangy wrote: »

Synozeer wrote: »

Vangy wrote: »

Synozeer wrote: »

The huge healing ticks are still there. Images from today on my templar.




Welcome back, Cancerplars.

Im confused..... It says 1.2k hps from harvester.... So if its supposed to heal for 7k per 4 seconds with 6 secs ICD, that is about 50-60% uptime... So 7k/4 = 1.75k hps and with about 50-60% uptime --> 1k+ which seems about right no?

I wasn't in the thick of things for much of that combat, so harvester wasn't active for the majority of the fight. I was only showing the FTC report so people could see the average and highest healing ticks along with the CLS combat log showing the same thing.

That information alone is not enough for me to deduce if its broken... Maybe a video with a log shot would serve better. Ive been using malu and nothing wrong is showing from my experience. I am however, on a DK tho. No BOL spam to test. Your numbers look write and without a breakdown of time I cant tell if its broken or not...

Look at my Devouring Swarm ticks in the combat log - I also have Malubeth ticks going on at the same time so you can see that these are happening within 2 seconds.

I recently ran the orsinium dwemer public dungeon group event and noticed a 8.8k scourge harvester heal. This was on a tank explicitly designed for self healing but that was odd. While going back to the dungeon i fought the large pull of dwemer spiders and got a 6.7k heal tick. Right before scourge harvester gave the heal (this being the first proc of it the fight) I got the "Overcharge" buff, not sure from where however. Scourge harvester proced 6s later and gave normal 1.2k heals.

During the test i just did against the Resonant Centurion I got at most a 2.8k heal tick but can't see any "Overcharge" buffs, but that heal was after scourge harvester had proced thing, 1-2 times prior, so it could be the game is keeping a 'phantom' teather on the target that continues to buff the heals, but after that spider fight i'm not sure. In the first Resonant Centurion fight with the 8.8k heal I got 2 procs of scourge harvester and then on the 3rd I got the proc that began with 7880 healing, hit the 8.8k peak, but the last two ticks were back to 1.4k, and i do not see any strange buffs before that proc that would explain that heal. I'm not sure what it is that is triggering these heals, but I doubt that this tank build would be triggering the bug zos mentioned in the patch notes.

Any idea what this "Overcharge" buff is? Any thoughts on the potential for scourge harvester leaving the heal buff on the player? Another thing to add, the last tick or two of the heal is often the lowest, or only stronger than the first few heals, which means it could be a healing buff that triggered slightly before the teather formed and expired slightly before it ended. Not sure, its a good set but these bugs are getting irritating.

Really zos, if you can't even manage to fix a single set what hope has this game got..

Just disable the set until you get your stuff together because i can't be bothered having 3 months worth of crap players using broken sets.

Infact considering this is still broken can i report them for using it? Pretty sure 8k heals a second is not intended.

I knew it was too good to be true, ZOS can only fix stuff in theory. They send a list to santa claus.

Does anyone have data on Malubeth from before DB or Thieves Guild when this set started coming into question , so that we could compare to the current healing ? A video with combat UI from then perhaps .

RinaldoGandolphi wrote: »

Honestly, Malabeth is fine now stop complaining please.

it has a 6 second cooldown between procs like Bloodspawn..so 7k dived by 6 = 1.1k HPS around that balpark.

the 6% chance makes it more like 7-8 secs which is fine...honestly folks need to stop complaining about tanks in PVP...i killed many Templars tonight that were using Malabeth, and I myself tried out Malabeth tonight om y DK and hoenstly...it has its pros and cons Bloodspawn is every bit as good after the nerf to Malabeth, so it just comes down to more healing or more Ultimate.

Prior to the change i would agree Malabeth procing with no cooldown for 7k heals wasd OP, but with the 6 second cooldown now its balanced, to make any other changes to it would make it useless.....

PS: that 30% healing received actually makes my Dragon Blood usable, it still won't completely refill my bar but it will atleast get me out of execute range for the 3k magic it costs.

It's healing 7k per tick, not 7k per proc. So it's 7k HPS, not 1k. The issue is not the 30% additional healing.

And I think (but haven't tested it), the 6 second cooldown starts counting from when it first procs, not when the proc ends. So if the beam lasts the entire duration, it can proc again almost right after ending. That's how Bloodspawn works, because I'm fairly positive I get Bloodspawn procs back to back - when one ends, I can almost immediately get another proc.

Synozeer wrote: »

RinaldoGandolphi wrote: »

Honestly, Malabeth is fine now stop complaining please.

it has a 6 second cooldown between procs like Bloodspawn..so 7k dived by 6 = 1.1k HPS around that balpark.

the 6% chance makes it more like 7-8 secs which is fine...honestly folks need to stop complaining about tanks in PVP...i killed many Templars tonight that were using Malabeth, and I myself tried out Malabeth tonight om y DK and hoenstly...it has its pros and cons Bloodspawn is every bit as good after the nerf to Malabeth, so it just comes down to more healing or more Ultimate.

Prior to the change i would agree Malabeth procing with no cooldown for 7k heals wasd OP, but with the 6 second cooldown now its balanced, to make any other changes to it would make it useless.....

PS: that 30% healing received actually makes my Dragon Blood usable, it still won't completely refill my bar but it will atleast get me out of execute range for the 3k magic it costs.

It's healing 7k per tick, not 7k per proc. So it's 7k HPS, not 1k. The issue is not the 30% additional healing.

And I think (but haven't tested it), the 6 second cooldown starts counting from when it first procs, not when the proc ends. So if the beam lasts the entire duration, it can proc again almost right after ending. That's how Bloodspawn works, because I'm fairly positive I get Bloodspawn procs back to back - when one ends, I can almost immediately get another proc.

Worse actually, since it ticks twice a second, those 7k ticks would give 14k hps for the duration. Its a good set, but these bugs plaguing it are getting old.

olsborg wrote: »

I knew it was too good to be true, ZOS can only fix stuff in theory. They send a list to santa claus.

Almost correct, what they actually do is outsource the coding for bug fixes to special needs elves at the North Pole.

Same result though.