Fossilize bugged in cyrodiil

Vizirith

Will remain grayed out about 40% of the time even when enemies are not cc immune. Wasn't all that noticeable until ran into a few longer 1v1's. Over the course of a few ~ 5 min fights, fossilize never could be cast. Unsure what exactly triggers the bug.

Bergzorn

Not sure if this is still the case, but a while ago one ore several of the debuffs with negative timer (debuffed by 5k days) on your target could lead to this behavior. Can't remember which ones exactly.

Cozzy1991

Seems to be a reoccurring theme that dragon knights skills don’t work…. Leap anyone?

silver1surfer69

Same here. IC and cyrodiil. Have it only vs some players and especiaally in longer fights.

milllaurie

Thing is, people are reporting a "stunned for 49k days" bug. I had it occur to my guildmates, not to myself.
Some stinning skills (toppling charge, surprise attack and such) will leave a 49k day status effect. Sometimes it bugs the receiving player totally (cant cast skills, cant sprint, only break free) and sometimes it will only let them break free on demand and give cc immunity on demand. You can't stun such players because technically they are stunned for 49k days.

katanagirl1

milllaurie wrote: »

Thing is, people are reporting a "stunned for 49k days" bug. I had it occur to my guildmates, not to myself.
Some stinning skills (toppling charge, surprise attack and such) will leave a 49k day status effect. Sometimes it bugs the receiving player totally (cant cast skills, cant sprint, only break free) and sometimes it will only let them break free on demand and give cc immunity on demand. You can't stun such players because technically they are stunned for 49k days.

That’s a interesting theory, one I have not seen mentioned previously. You may be onto something.

However, I am not sure if the skills you mentioned are causing the status effects that I have seen either personally or here on the forums. It’s either Streak, Burning, Poisoned, Soul Tether, Mortal Coil, and something that causes Minor Maim I think for me.

I often feel like the fact that skills don’t fire is often just because of lag and/or desync. I can see the cursor on the NPC or player in PvP and sometimes it is open and I can’t use a skill and then later it “winks” and I can. (On console the four lines of the cursor squeeze tighter together to indicate that the enemy is targeted.). I can plainly see the cursor right on top of the enemy and it is not targeted.

I do not use my dk in PvP anymore but I see this on my stamplar PvP and my stamblade PvE toons.

milllaurie

katanagirl1 wrote: »

milllaurie wrote: »

Thing is, people are reporting a "stunned for 49k days" bug. I had it occur to my guildmates, not to myself.
Some stinning skills (toppling charge, surprise attack and such) will leave a 49k day status effect. Sometimes it bugs the receiving player totally (cant cast skills, cant sprint, only break free) and sometimes it will only let them break free on demand and give cc immunity on demand. You can't stun such players because technically they are stunned for 49k days.

That’s a interesting theory, one I have not seen mentioned previously. You may be onto something.

However, I am not sure if the skills you mentioned are causing the status effects that I have seen either personally or here on the forums. It’s either Streak, Burning, Poisoned, Soul Tether, Mortal Coil, and something that causes Minor Maim I think for me.

I often feel like the fact that skills don’t fire is often just because of lag and/or desync. I can see the cursor on the NPC or player in PvP and sometimes it is open and I can’t use a skill and then later it “winks” and I can. (On console the four lines of the cursor squeeze tighter together to indicate that the enemy is targeted.). I can plainly see the cursor right on top of the enemy and it is not targeted.

I do not use my dk in PvP anymore but I see this on my stamplar PvP and my stamblade PvE toons.

We have tested it with toppling bugged. The target could break free indefinitely and give himself cc immunity on demand. He had the 49k days toppling on him. Only occured in a duel in a player house though.
My brother had gotten a 49k days surprise attack on him. He could ONLY break free, not sprint or use any skills or even barswap. He wasnt able to get stunned even after he died. Relogging fixed it.
Only seems to occur on classes who can purge themselves though. First was on a stamden (netch), second was on a magplar (ritual).

katanagirl1

milllaurie wrote: »

katanagirl1 wrote: »

milllaurie wrote: »

Thing is, people are reporting a "stunned for 49k days" bug. I had it occur to my guildmates, not to myself.
Some stinning skills (toppling charge, surprise attack and such) will leave a 49k day status effect. Sometimes it bugs the receiving player totally (cant cast skills, cant sprint, only break free) and sometimes it will only let them break free on demand and give cc immunity on demand. You can't stun such players because technically they are stunned for 49k days.

That’s a interesting theory, one I have not seen mentioned previously. You may be onto something.

However, I am not sure if the skills you mentioned are causing the status effects that I have seen either personally or here on the forums. It’s either Streak, Burning, Poisoned, Soul Tether, Mortal Coil, and something that causes Minor Maim I think for me.

I often feel like the fact that skills don’t fire is often just because of lag and/or desync. I can see the cursor on the NPC or player in PvP and sometimes it is open and I can’t use a skill and then later it “winks” and I can. (On console the four lines of the cursor squeeze tighter together to indicate that the enemy is targeted.). I can plainly see the cursor right on top of the enemy and it is not targeted.

I do not use my dk in PvP anymore but I see this on my stamplar PvP and my stamblade PvE toons.

We have tested it with toppling bugged. The target could break free indefinitely and give himself cc immunity on demand. He had the 49k days toppling on him. Only occured in a duel in a player house though.
My brother had gotten a 49k days surprise attack on him. He could ONLY break free, not sprint or use any skills or even barswap. He wasnt able to get stunned even after he died. Relogging fixed it.
Only seems to occur on classes who can purge themselves though. First was on a stamden (netch), second was on a magplar (ritual).

That’s very interesting, it does seem to prove your theory in PvP.

The PvE targeting problems I see might be due to something else then.

silver1surfer69

The thing is its not that it completely refuses to work but it only works sometimes. I feel like it wont work 20-40% of the time. When i have an infinite bug on me (49k days...) i cant sprint anymore which i described in another thread and this kind of bug can only be solved by completely relogging but fossilize still works sometimes then. Observed in CP IC and Cyro EU.

Edit: Same with opponent. I had eg longer fights when my fossilize was greyed out only only worked like every 50 sec but the stun from dizzy worked in the meantime.

paulychan

Bergzorn wrote: »

Not sure if this is still the case, but a while ago one ore several of the debuffs with negative timer (debuffed by 5k days) on your target could lead to this behavior. Can't remember which ones exactly.

I had eternal cc immunity which was caused by a DK guard using chains, I think, while I was solo flipping a rss (ps4na) yesterday. I stuck around for a fight and was indeed cc immune for the entirety of it. i layed it down and went to the hammer instance to remove. its very much a thing tho

paulychan

I forgot to add that I used shield charge or whatever against the npc.

Vizirith

Still bugged.

silver1surfer69

Any update on when this is fixed? It is still bugged. I hope u fix it with update 32. As in combat preview or patchnotes you (zos) said DK will get some long overdue love. For me personally this will be the pivot point if i leave the game.

silver1surfer69

Dear ZOS,

i try to provide as much info as i can to fix the petrify/fossilize bug.

Ive been monitoring this and try to figure it out as much as i can by analyzing my recorded fights.
Sometimes i can fossilize my opponent a 1st time and then the cc immunity check for further fossilizes seem to always show that the target is cc immune - fossilize is greyed out.
This is eg for about 50 seconds. If the target gets stunned by another CC/ eg from another player, eg fear seems to work very good, then after this cc immunity wears off
(6-7 sec) i can fossilize the target again. But sometimes i cant fossilize my opponent at all, observed up to many minutes.

I can imagine this has maybe also something to do with what was introduced in update 5.2.7:

https://forums.elderscrollsonline.com/en/discussion/500502/pc-mac-patch-notes-v5-2-7:

"General:
Crowd Control abilities that have fail safes for targeting already CC’ed targets will now properly update when looking at targets that gain CC Immunity via special means, such as abilities or potions."


-> the described above + maybe the 49k days debuff bug shows for petrify/fossilze that the target is cc immune - BUT AS DESCRIBED OTHER STUNS WORK! Maybe only stuns with (in 5.2.7 patchnotes) the described failsafe show this behaviour. What is an other failsafe CC, was there something similar reported?

Jim6270

It simes like it is immovability pots that make fossilice bug. When an enemy you are figthing is using those pots you cannot use fossilice on them for a full pot doration insted of only the 10.5s as it should be. So you end up seeing that they are not CCimmune and you cannot use fossilice on them even though you can stun CC them with any thing ells.

Hope they fix this because many builds are onplayable on DKs because of it.

silver1surfer69

Ok i just a perfect example for this fossilize bug. It was a long and hard fight that i recorded.
Fossilize was greyed out for 4 minutes and 42 seconds from the beginning on, i couldnt fossilize my opponent not a single time and checked the recording after - it was greyed out 100% entirely until i managed to hit the guy 2x with dizzy swing and

-> STUNNED him that way.

- After that fossilize was working everytime after the cc immunity wore off (6-7sec).

-> I asked the guy after if he had a 49k debuff on him. He checked and said NO.

--> BUT HE SAID HE USES UNSTOPPABLE POISONS THAT ALSO BREAK U FREE!


(Here is the tooltip text of such a poison:
Immobilizes your target and grants you Unstoppable, rendering you immune to control effects for 3.9 seconds. This poison will also break you free of ongoing control effects.)

-> So we are getting closer - it seems it really has to do with what is described in update 5.2.7 patchnotes:

https://forums.elderscrollsonline.com/en/discussion/500502/pc-mac-patch-notes-v5-2-7:

"General:
Crowd Control abilities that have fail safes for targeting already CC’ed targets will now properly update when looking at targets that -!- -!- -!- gain CC Immunity via special means, such as abilities or potions." -!- -!- -!-

(This happened in CP IC PC EU)

silver1surfer69

2 additionaal thoughts what also could play a role:

- The CP star that makes your CC immunity duration longer.

- as many others have already pointed out, its very likely that immovabilitty potions play a major role here.

silver1surfer69

I wanted to inform you that the fossilize problem/bug is still in the game. Its far less often now. But when i encounter it its unusually often fighting against Necros. Sometimes its with wardens too. I think templars sometime too. All that leads me to the thought that is also has something to do with a purge that necros (Expunge) and wardens (Betty Netch) have. Pls check this. Maybe they purge/autopurge the immobilization or something but as already described sometimes i cant fossilize them at all, over minutes, or i can fossilize 1 or few times and then i cant anymore over long durations. Pls investigate, ty.

silver1surfer69

It looks and feels like there is a timer that isnt resetting itself under certain circumstances.

Vizirith

Still bugged jfc

silver1surfer69

Its still in the game. Had it yestreday night 2x. Same pattern as always. Target cant be fossilized for minutues until stunned by another sorce then can be fossilized. Its almost always with necros. Have you checked if its the thing i said before that it happens when necro purges the immobilize? That was 3 months ago. Did you even bother to investigate that route? Pls do something!!!

soniku4ikblis

This was happening to me in Cyro on NPCs. Couldn't figure out how to fix it. Then I was attacked by a NB who I fought for roughly 5 minutes. Could not Fossilize him in that long length of a battle. Finally just gave up.

Will try another form of stun to get the skill to work again. Works fine in dungeons atm.

silver1surfer69

soniku4ikblis wrote: »

This was happening to me in Cyro on NPCs. Couldn't figure out how to fix it. Then I was attacked by a NB who I fought for roughly 5 minutes. Could not Fossilize him in that long length of a battle. Finally just gave up.

Will try another form of stun to get the skill to work again. Works fine in dungeons atm.

Yes now that you say this, the npcs in IC on the flag can be fossilized for like the first some seconds (maybe 10) and after that they cant be fossilized anymore (of course without having them stunned before). Happens every day, every fight!

What you can do is as you already said yourself try to stun your opponent with something else, or if you havent another source, try to set them off balance (if have this, for dk: immobilize (skill or poison) and then whip) and then use a heavy attack, this stuns too.

silver1surfer69

When fighting the static NPCs at a flag in IC the behaviour is even weirder. As said they can only be fossilized in the first seconds after entering the fight with them, something like 10 sec and after that they cant be fossilized anymore but here fossilize is NOT greyed out but is not working.

silver1surfer69

I want to add an observation. Recently i had a fight with a templar. Same pattern, he couldnt be fossilized entire fight. After like 3 min i managed to win and he respwaned in the sme IC district and we continued the fight. After that he could be fossilized normally all the time.

So this is the observation, after the target dies and respawns the bug is gone.

I encounter this bug in the last months only with necros (almost all the time), templars (seldom) and wardens (seldom). No other class since a long time. So pls investigate this, my thought is that the purge is what these classes have in common, and the bug maybe happens when the immobilization is purged/autopurged!

silver1surfer69

Some days ago encountered again a Necro in IC that couldnt be Fossilized a Single time oder Minutes. About 95% of the time IT is with necros.

Xarc

maybe it is because the target is using an immunity when you're trying to fosilize ?
As a necro I can say i'm very often fossilized...

silver1surfer69

Thank you. There is no immunity longer then 10.5 seconds (= immovabilty potion, if you happen to drink it after breakfree you can prolonge this to 16.5 sec). Or other abilities that grant hard cc (stun) immunity, but it can be recognized if an ability is used. You are welcome to join and recapture the Diskussion and Informations gathered in this thread by browsing through the Informations gathered here above.

silver1surfer69

Ok one of the reasons for this bug is figured out finally - we could replicate it every time!

Today i met a very friendly templar (@hutnik666) that i was fighting in IC and he had the bug.
He was a huge help and immediatly joined in trying to figure the bug out. I asked him to fight me and try stuff that could be the reason. We fought and tried everything we imagined that leads to the bug for about 1 hour.
In the process we tried several of the stuff i had theorized before that could be the reason, like cleansing
the immobilization after breakfree. That was not the reason for it.

He finally came up with the idea that it is, if you cancel mistform. That is when you go into mistform and immediatly press the button again.
We could replicate this every time that this bugs out fossilize. After you do that fossilize is greyed out and stays greyed out for as long as you want until you stun the target again by another stun. I had figured out this temporary workaround with the stun to reset it, some months ago as described above in this thread.
I recorded the whole session and it worked everytime. We again tried different froms of animation cancelling. Cancelling by weapon swap, or canceling by dodge roll.
Only the animation cancelling by pressing the button again quick bugs fossilize, not the cancel by swap or dodgeroll.
So after scrutinizing this for months and months now, it finally got figured out, at least 1 reason that leads to it. Pls be aware that there could be more resons that can bug fossilze out, like the breakfree poisons (identified in october with the help of another friendly sparring partner, a big thank you to @nonoobs) as described above, but this reason is fixed by Zenimax already i assume. If there are more reasons for fossilze to bug, i hope we can gather them all here, and figure them out too. We finaly have figured this reason out and we could replicate it every time.
I hope this gets patched out of the game now with the next update. Here it is:

-> Fossilize gets bugged out (greyed out infinitely) if the target is animation cancelling mistform by pressing the button 2 times in quick succession.

silver1surfer69

I want to add, ive seen in my recordings from other fights, it seems to be not only if you cancel mistform but just if you leave mistform by pressing the button again! I just had a fight where the oponent stayed in mistform for 5 seconds and mistform was greayed out after it nonstop!
Again we tested that this is not happening if you leave mistform by other means like weapon swap or dodgeroll.

silver1surfer69

Therefore it seems that fossilize is not resetting itself when the target is leaving mistform by pressing the misform button again, not only if this was a very short time but also some seconds. As posted earlier above, this has very likely to do with the mechanic introduced in update 5.2.7, as described in the 5.2.7 patchnotes:

https://forums.elderscrollsonline.com/en/discussion/500502/pc-mac-patch-notes-v5-2-7:
"...General: Crowd Control abilities that have fail safes for targeting already CC’ed targets will now properly update when looking at targets that gain CC Immunity via special means, such as abilities or potions."

-> Leaving mistform by pressing the mistform button again has to be added to the bugfixes concerning this mechanic please.

Edit: Maybe there needs to be a Mistform-On and Mistform-OFF logic for the gamecode. Maybe the reason for the bug is that there is just a Mistform-On (which means CC-Immunity-On) logic/command, so the immunity, at least for this failsafe ability fossilize, stays active after pressing the misftorm button, even if it is to leave the mistform state.