Impending Doom + Vixen's Entrapment BROKEN on 1st cast
" Cursed ground setup worked before fix, so question what GGG fixed in the patch ?? Did they tested it ?? Last edited by mpyu1992#6377 on Aug 23, 2023, 12:09:37 PM
|
![]() |
Chiming in with mostly confused after the patch notes, it's not clear to me at all what the intended mechanic is now.
Tested again on my 3.20 Occultist and it worked better before this latest patch? Feels okay clearing maps, bricked for killing rares and bosses. If GGG would rather the build die then I'd prefer them just straight up saying "we do not want you to play this anymore". Confusing and unclear. My Forum Thread | https://www.pathofexile.com/forum/view-thread/3289135
My Hideout Showcase | https://hideoutshowcase.com/viewprofile/RevanBane Hideout Community Discord | https://discord.gg/8McTXAKFbG |
![]() |
Apparently one needs to remove the gems and re-equip them.
|
![]() |
" nothing unclear there. just see, what happened - they changed smth (dont remember what exactly and too lazy to check patchnotes) in league patch - bug appeared - they tried to fix it but failed - they reverted changes been made in patch - bug still there conclusion - they have no freaking idea how their code works and how to fix this problem. like many times before. its strange to think that they dont want to fix it. even company like ggg wouldnt do that. but they cant. Мы и так уже играем в совершенство (с) Achilles2626
Проблема: нет проблемы. Решение: создать проблему "Мы не хотим забирать ощущение, когда ты кидаешь сферу возвышения на предмет с закрытыми глазами, потому что боишься посмотреть, испортил его или нет. " |
![]() |
Even in the Crouching_tuna video where it says its fixed you can see if doesn't proc for him on 1tap in blood aqueduct only where the circles overlap.
So yeah i think people who say doom 1taps use cascade and it 1taps where the circles overlap but without cascade in both gloves/chest it doesn't. |
![]() |
The build without super min / max gear was never good for bossing , even last patch.
So even if all would work as intended, you still would struggle on single target. 80% of all active Skills in this Game are not viable for PoE's Endgame and yo uthink they care if 1 more does not work. IF you look at PoE Ninja we have the same 10-20 Builds people play for the last 4-5 Seasons. PoE is in maintenance mode. |
![]() |
" But... they know exactly how to fix this. They did, at start of the league. Let me put this even more straight to you: - they introduced bug with Spell Cascade and Vixen's long time ago (3 years, to be exact), where Spell Cascade should spread more (it was changed from % increased AoE to + radius or something like that, and that caused circles to overlap). People call it "how it's supposed to work", while it's in fact not how it's supposed to work. - they changed some stuff in internal code for 3.22 (most likely some kind of refactor, because 10+ years old software tends to be bigger and bigger case of spaghetti code and requires some love) - therefore, they fixed a bug with Spell Cascade and Vixen's - either without aiming to do that or with a mindset of "it can't be that bad, and we have 9 people working on the game so let's just jump to next task" - league starts, people get to ID + Vixen's, shit goes down - they check it out, see that it's not in fact a bug, but they have a dilemma now - keep it as it should be or find a way to reintroduce bug, so people are not as mad - they so what's morally right - since people started their league with ID hoping it will work with Vixen's, they reintroduced bug for remainder of the league That doesn't change main issue here - Spell Cascade and Vixen's are not working how they wrote the code and they still want to fix it. I get that people might have usual "no fun allowed" mindset on that, but they still fail to understand that devs don't really want to have buggy code, as it may lead to more and more problems as time goes. I really don't get why are people that mad on that issue. |
![]() |
"We have reinstated the old behaviour only for Curses for the remainder of the Ancestor League, but this incorrect behaviour will be fixed in the 3.23.0 patch."
the old behavior is currently NOT reinstated, as the first cast still doesn't proc impending doom with spell cascade. Is there any official statement regarding this issue? |
![]() |
" From what I can tell it was reverted again during one of the hotfixes. :( |
![]() |
Have the exact same issue. Please fix! I spend like 10 hours on speccing my build for this shit to go down.
|
![]() |