Here a video of the how it works:
1 Like
And here the revive even if an assassine pinned you down and you are downed (red-lifebar)
1 Like
Some intentional cheesing (legend - harder, faster, better, stronger)
1 Like
It is 100% and it also is 100% consistent stopping disablers.
No, itâs not. Iâve been playing with the Warrior Priest quite a bit.
It does not trigger when getting disabled while holy fury is already active after Divine Shield ends or if you get killed before it triggers.
When it does trigger, itâs often not enough to get rid of a hook rat. I think most other disablers will get staggered off though.
yeah because the talent says:
and so you have to let fury expire and then enter it againâŚthen it works 100% consistent⌠like the talent says it.
I have playtested it for several hours and the talent actually says it as well. Please read the talent first how it works and then pretend something.
Every time you enter righteous fury you will have a free revive and and a free stopping from disablers, because your shield will proc 100% consistent.
Thats also why i said yesterday to you that i doubt that this is a bug, but actually an intended mechanicâŚwhich has to be reworked because it is damn overpowered, and easily triggered by intent, with a cooldown of only a 30seconds at most.
To clarify it further, fury has to be inactive to get the shield/revive/bubble/stopping disbalers/ and the moment it enters fury you will be rescued by your bubble.
1 Like
Oh thanks. Iâm pretty pretentious but lucky youâre here to correct me.
I wasnât trying to be antagonistic. Someone online contradicted you. Youâll get through it. Also coherent sentences help. Like so, âBefore you pretend to know how something works, try reading the description.â
Then follow up with the unnecessary screenshot of the description Iâve read several times as if this matter calls for photo evidence.
My confusion earlier when I asked the question was because people made it seem like it was so bugged it always resâd you, so I was surprised to find it doesnât till I played some more.
I never said it was supposed to activate while fury is active. Perhaps I couldâve also clarified what I was asking. The example was just one example to demonstrate that itâs not 100% going to save you everytime you get downed just incase you werenât aware because I mistakenly thought thatâs what you meant, it wasnât crystal clear.
The talent works according to itâs description.
However, that doesnât automatically imply that Fatshark was aware of, and intended for the interaction with the level 30 talent that heals damage when divine shield triggers.
Even still, this interaction is buggy and inconsistent. Iâve seen numerous visual glitches when it triggers. It doesnât always res you when downed, even without righteous fury already being active, and you having it activate with the heal talent. Sometimes the damage taken while downed or disabled doesnât give righteous fury. Sometimes divine shield from fury clears wounds. Usually it does not. Maybe you can tell me why. I donât know
1 Like
Even as host? As host it always worked for me every single time for hours of playing him.
Might be the case but so it is an unaware mechanic and not bug, maybe my definition what a bug actually is differs from yours.
so you werent implifying the inconsistenty and bugginess with following?
if that was only stating a fact of the discription that you have to trigger it by intent and doesnt work outside of it then i misunderstood you, sorry for that but in context of debating wether it is inconsistent and/or buggy it really sounded like you are trying to trigger it while you have fury up and therefore you wonder why it is so inconsistent.
My point is you can trigger it way too often way too easily by intent by because loosing fury doesnt need much time, so if you want you can really cheese maps with a minimum of awareness.
sorry for the harsch wording towards you previously, i am just a bit baffled by introduction of this mechanic, and i just cant believe that this was overseen because the too talents and there mechanics are crystal clear. The developers have experience in putting builds an mechanics together. It is not like they are doing it the first time. Also it doesnt need hours of deepdive into the build to bring up some insane mechanics like in path of exile. The mechanic are 2 crystal clear talents not more not less and therefore i truly believe that they knew about it and that it was intentional to bring this mechanic into the game, what somehow outrages me.
So sorry from my side. I only cant believe your point of view that this was unintended by the devs and therefore i am afraid that this will stay in the game for way too long.
Youâre a nice person. Now I feel bad for being super sarcastic and cranky.
No, I wasnât implying that was a bug. I couldâve been more clear. I was only giving an example of when it doesnât revive the player. My initial expectations for how the talent works (or doesnât work) were based on the idea it was bugged and 100% always kept the player from getting downed. I was confused. One friend had even told me you canât die from getting downed or disabled.
2 Likes
I want to stress again that Fatshark has been made aware of that very particular interaction before it went live and decided to still go through with it.
1 Like
Ah there you see the inconsistency, yeah this is pretty tricky, sometimes you will be downed, sometimes it triggers before you are downed, but it will always revive/bubble you. I mean sure it has to do with the bar of the fury and how much filled it is and if the fury is already close to be activated you will be never downed, if it isnt close, it gets tricky when it will shield you. So on low fury bar (while inactive) you cant rely on it being not downed.
As long as the shield is active on you of course, but the bubble has only a chance to kill the hooks (it wont push them off) but this chance is low. Some guy also did the math, which breakpoints do you need for what chance, i guess it was even royalcheese. Leeches and assassines will get pushed off and even being killed.
Here are the breakpoints for killing a hookrat with your shield of faith on cata with 20% power vs skaven and enhanced power
and here what royalcheese wrote:
Other fatshark special, time to wait other 6 months to maybe get a fix.
2 Likes
And by then there will be a group of people whoâve become attached to it and kick up a stink when itâs removed.
3 Likes
You donât have to wait six months for this. It will already happen if you change it today. I quote:
âNo FS, why??!? Sure, it may have made the game a bit easier. But thatâs no reason to remove a playstyle. It was fun and this is only a PvE game that doesnât need balance. Warrior Priest is weak again and unplayable on anything higher than Champion.â
Actually, the combination is kinda strange in this sense. Certain weapons and talents become only viable on higher difficulties like Greatsword, Conflagration, (old and new) Coruscation. But it was more like they get more efficient with still a pre-set limit. But this one? It gets more powerful and more powerful the more you throw at WP.
This combination actually scales with Weaves damage scaling. On Weave 160, you are sure to get revived by every single attack. We need the first troll video of someone cakewalking Weaves now O.o Even Coruscation didnât manage that. Though, scratch the part of old Corusction having a pre-set limit. That RMB was beyond busted.
1 Like
you mean like this?
1 Like
Seems someone was faster. Although it is only the effect and not the whole Weave. There is âstillâ the issue with getting through in 15 minutes. Though, the one-hit revive is real ^^â Video also serves as a good indicator on the potential downtime. Less than 20 seconds, though only if nothing is killed in the meantime.
Now, I wonder how the scoreboard reacts on this. FS has changed it that casting Shield of Faith on downed allies and reviving them counts in the scoreboard as normal revive. Will it be the same with auto-revives of yourself? Finishing the mission with 10 revives in the scoreboard. All on Warrior Priest. Most helpful teammate ever.
1 Like
I still stand by what I said. Iâm fairly certain it takes Fatshark a long while to get around to looking at community feedback.
Even if someone there saw that warning, it might not have been the right someone; it may be they thought it was fixed. Or maybe it was fixed before the patch was live and somehow didnât make it out. I donât know.
This is why you donât just roll this stuff out on the first possible moment if you donât have the QA to go over interactions like these.
And just looking at darktide, they clearly lack those QA resources to even publish proper patches in that game, so the least they could do is let the patch notes sit a little bit with community before pulling the plug.
There are really easy solutions to âoops i missed thisâ, and its far from being the first time either. Iâm personally getting really tired to times Iâve seen someone say âhey this sounds stupidâ and it somehow ending up in the game for the foreseeable future.
1 Like
To be honest while this is all good and well, Iâm not sure Iâd call it broken. Admittedly I havenât played WP too much, but the little Iâve played it, I decided to roll back to the party heal talent.
This is useful in fringe situations, but youâre kinda assuming youâre soloing, or at least that thereâs nobody there who could save you. If the partyâs good, something that goes to help everyone is more useful IMHO.
One or two years ago I would be also most likely considering the ability to be broken.
At this stage of the game life, I consider it just funny. It also kind of fits into warrior priest trope.