I love that 8.4 added visible ailments. but 15 is way too little.
doing a poison based fast attacking Swarmblade, being limited to seeing 15 is nearly the same amount of information we had before we could see ailments.
Iām sure it is, but iām just providing feedback. And suggesting maybe they should limit based off mob Health.
lower the targetās HP, lower the cap of ailments to show. That way when it gets to a big boss where you can stack things up, you get the information you care about.
Or make Target dummies have no cap. So we can see our potential, test to see if gear set X gives more stacks vs Gear set Y.
Once we have a way of getting that information, we can then have the limitations placed back on multiple target combat, for smoother and responsive play.
Yep i would also like to know that andā¦
ā¦Thats always good for the devs! I just wanted to give you a quick answer that i saw on this post.
Iām at least happy that we have those ailment stacks now, even though its only 15+ capped. Now we can test if all the mechanics work as intended. Before i never knew if some of them work together because of the many numbers we can see on a dummy.
I agree for more visible stacks will be awesome, as 15 stacks feel a little bit too low for stuff like poison or frostbite. Just taking example from Guild Wars 2, they have those ailments like bleed stacks displayed up to 99+, so I just wondering why do Last Epoch sticking with 15 visible stacks.
The computation seems a bit weird here. Arenāt the stacks are already applying even without the stack display? It sounds kind of weird saying changing display of 15 to 16 require double computation than changing 14 to 15. I am not sure how their code works, but computational works doubled sound really weird to me as a programmer.
I was wondering this myselfā¦
until I guessed that maybe the Ailment stacks are applied as entirely separate hits/second on a target with their own damage,duration and rateā¦ not just one āX stacks applied each secondāā¦ LIke 15 invisible bleed mobs hitting the target with different damange numbers and durations vs 1 invisible mob hitting for 15x the damage.
Pretty sure summing up 15+ separate stack entities would computationally be far more resource hungry than just how returning how many stacks of a single entity are being appliedā¦ and considering that there is probably a limit on the number of computations per tick that the game engine can handle to remain within a certain performance windowā¦
Honestly.,ā¦ I am guessing hereā¦ I have no idea how EHG is doing it to say for sureā¦
That is exactly how it works. Should I link the post where I explain this again?
Scrolling is hard on the fingersā¦
Donāt you have a phone? Scrollingās easy on phones.
Nahā¦ am old schoolā¦ I seldon use my phone for web browsing and most definitely not commenting on forumsā¦ sure you have noticed my penchant for being excessively verboseā¦
Even given some expensive step for each individual ailment stack, summing them up should be a strictly linear scaling. Scaling significantly with the stack size is in itself super odd, but 2^N is wild. If thatās for real the algorithm is weird and wrong. Itās just not something that can possibly fall within the scope of a justifiable requirement or a limitation of the data structure.
2^N does seem excessive and perhaps just saying āDoubleishā has opened a bigger can of worms than it shoudā¦ Wonder if @EHG_Mike is up for explaining it in more depth?
āEveryone has a phone, right?ā - ActiBlizz
1 Like
Again? Iām pretty sure he explained it on discord which I then paraphrased in the above link. Iām sure he has better things to do.
Maybe he doesnt need to explain it in more detailā¦ This is purely out of interest and well outside the realms of the game.
The doubling of required system resources on a single increment like that described is generally an abnormal/unusual thing in the programming world so it would be interesting to understand why that could be the case with this particular implementationā¦ maybe its just how Unity works, maybe its a particular side effect of the way ailments are implementedā¦ maybe its related to something else that has nothing to with ailments themselves but impacts on the performance based on the addition of this to the UI.
We would love to be able to give the full ailment stack counts. We canāt do it without compromising the performance of the game. I know this seems like a trivial system. Itās something that people were very confused about why we didnāt have it at all for a long time. This has been on our feature request list for years. The 15 stack limit is the only way we have been able to get the performance we need to not cause major problems.
If we find a way to increase the visible stack count, we will.
7 Likes
Was my description of it reasonable?
I probably shouldnāt have brought numbers into it. I was really just trying to make it easier to relate to. In some circumstances it can be way worse than others and we have to design it with the worst case scenario in mind. Putting those numbers to it doesnāt really answer why itās like that.
3 Likes