Hi, currently playing Erasing Strike VK with crap ton of stun. And I’m being punished for using an affix that was SUPPOSED to help me in these fights against certain enemies. I was fighting Rayeh in empowered monolith and it’s spamming AoE at me on top of his pizza slice move. Why has been there no improvements in this case? I remember this being the case in PoE2 Xesht fight too where you would get infinite hand slams if you stun him during this phase.
Probably only against Rayeh and Gaspar where this kind of thing can happen. Anyways this shouldn’t be happening at all. Affixes are there meant to help players, not punish them.
There was no improvement in this area because to little people care about and EHG had other issues so it was forgotten. I’m sure it will stay on the bottomline of issues that needed to be fixed for a long time as sad as it is for people who think stuns are fun.
Yeah but mechanicly, and after they took a very long time to squish bugs, it’s still there. So either it’s an issue htey can’t solve in a nearly one year time frame or they didn’t want to solve it because other stuff is more important or they forgott the issue existed.
To me forgetting about a broken mechanic in their game is more diplomatic then saying they don’t care they have a buged mechanic ingame and leave it there even after they announced their big patch that should solve all old problems aka stun beeing wonky.
To me it’s a bit shamefull that stuff is still arround but that’s only my personal oppinion. Given the time they needed to fix Lagoon I realy have no high hopes for people who use stuns ^^.
Again, it’s not forgotten. There are thousands of bugs in game like these. If a bug affects only a small part of the population (or isn’t game breaking and just mildly annoying) and the fix isn’t a simple one, then it gets pushed back for a long time in favor of more important bugs or easier to fix ones.
This happens in pretty much every game, but even more in seasonal games, because each new content added will introduce new bugs as well.
PoE1 still has bugs from beta that haven’t been fixed. Nor is it likely they ever will.
It’s not that devs don’t care or forget about it. It’s just that there’s only so much manpower available and you can’t fix all the thousands of bugs, especially when some are somewhat minimal but are hard to fix.
1.2 was supposed to fix the technical debt as per the reasoning for the large delay. Sad to see a core issue like this is still not fixed. If it is not done in this time then I think there is no hope for it being done ever.
I don’t know where you got this. 1.2 was delayed to introduce big endgame changes, since that was the point players were complaining most about.
It had nothing to do with delaying a season just to fix bugs. That would have been terrible and most players wouldn’t return just for that.
I never said they didn’t take the chance for fixing bugs. Just that it wasn’t the main cause for the delay. That was primarily due to wanting to revamp endgame entirely.
As for catching up on bugs, they did. A lot of them were fixed. Certainly more than in any other patch to date. They just haven’t fixed them all (nor will they ever because it can’t be done).
As I said before, almost all games have bugs that never get fixed. Usually bugs that aren’t too relevant.
This isn’t one of them, it just hasn’t been enough of a priority (or simple enough) to fix. I don’t expect it to stay relegated forever, but I also don’t expect it to be fixed right away.
It might not be relevant to you but it kills a complete playstyle and while I don’t use it I still think it’s equaly important to having an ailment system or bows that shoot arrows or toons facing into the right direction.
On top of it it alters some bossencounters to nearly unbeatable levels.
One mans trash is another mans treasure and I would never belittle somones choice and what said person seems to like because it not matters to myself. It’s a glearing oversight with a more issues behind it.
I’m not belittling anything, no need to get all riled up.
I said “usually” aren’t too relevant. And I did also say “This isn’t one of them, it just hasn’t been enough of a priority (or simple enough) to fix.”.
You just told someone their worrys and their choices aren’t too relevant. Where I’m from that’s a complete dick move. I only want to say that their concerns are valid and that a mechanic that breaks the game obviously in some encounters needs to be adressed.
Yes there are not much people who play it and that could be a factor on how fast things get fixed or not. Ehg taking their time to fix their systems as well as working on the endgame and overlooking a mechanic that breaks the game is just another “feels bad” moment.
I would be a bit pissed of if I made a build that works just to find out it isn’t because it breaks the game for whatever reason and the devs let it slide for whatever reason.
I get your point that this only affacts a very tiny fraction of players and therefor isn’t that big of deal from your perspective. That’s an understandable point of view so no worrys . I just don’t follow it because it’s a sad thing if EHG is blocking a builds success because of whatever reason when it should work properly.
BTW @user38 did you open up a Bugreport? Because this topic is more of a bug then a feedback matter .
Hello, I think this is more of fitting to be a “feedback” kind of post. I don’t think it’s a bug but rather more of a “bad design” in coding and how the bosses interact when being stunned in some scenarios, like I mentioned in the post where this happened too in PoE2 where they probably didn’t test it out thoroughly during combat. I played other games too where the boss would bug out if you stun/kill/interrupt them at the wrong time, causing possibly softlocks, etc…
Besides, there’s already a bug report I linked in the original post from a year ago…Just have to remind EHG again with this one…
Thank you for voting this. Hopefully it gets “fixed” in the next few patches.
. I just don’t follow it because it’s a sad thing if EHG is blocking a builds success because of whatever reason when it should work properly.
.