3.22.0b Patch Notes (restartless)
3.22.0b Patch NotesThis patch contains improvements to The Trial of the Ancestors and bug fixes of both small- and medium-importance. Trial of the Ancestors Improvements
General Changes
Bug Fixes
This patch has been deployed without restarting the servers. You will need to restart your client to receive the client changes in this patch. There are still further changes that were announced we will be getting out in subsequent patches. Has any exile really been far even as decided to use even go want to do look more like? Last bumped on Aug 29, 2023, 3:29:53 AM
|
|
" We're currently investigating and testing fixes for situations that some players are experiencing (tiles/assets sometimes not loading, long load times, cases of high CPU load) and hope to get them out soon. Has any exile really been far even as decided to use even go want to do look more like?
|
|
"This bug is not that old (it is 3 years old, which is still impressive). Spell Cascade has always taken account of area modifiers when placing areas, to make them more spaced out and prevent areas from overlapping too much. That has been the case since it's introduction in 3.1.0, at which point it as far as I can tell, it did not have the bug, because no cascadable spells were using the +x to radius stat. In 3.12.0, curses changed from having % area modifiers to having + radius modifiers as the gem levels up. Due to the way radii have traditionally been handled in PoE, unlike % area modifiers, which can all be combined into a single multiplier that gets applied in a standard function, adding to the radius can't be folded into that multiplier. This means that each skill which uses a + radius stat needs it's code changed to manually add the value of that stat before the aforementioned multiplier is applied. Unbeknownst to us at the time, this introduced the bug (at least as it pertains to curses). The curses themselves were correctly updated to account for this modifier applying to them, but Spell Cascade was not - it was adjusting the spacing of areas to account for all area modifiers except "+ radius" ones, which is incorrect - it was calculating spacing based on the wrong area radius. I only worked out this part today, but some other skills, such as Contagion, were actually handling radius in a different way which included the added radius in the base radius value that spell cascade saw, meaning they behaved correctly - so the bug was inconsistent from skill to skill. 3.22.0 includes a substantial internal rework of radius handling to allow radii for skills to mostly be determined by stats, which can then be described on the gem/skill popup (as is already done for the new Avenging Flame skill from Flamewood Support). This necessitated changes to how Spell Cascade calculates radius. We weren't expecting this to change anything, as in theory it was already accounting for all area modifiers and continued to do so in the new system, but due to the bug it was actually not correctly doing that previously for several skills, including all Hexes. Because the new version of spell cascade calculation was done correctly (and no longer requires special code in each skill for +radius to be applied), this changed behaviour with the skills that had the bug, and we didn't find this difference in testing prior to the patch release, so it was not described in patch notes. The correct, intended behaviour of spell cascade has always been that it calculates the spacing of the areas based on how big they actually are. The previous behaviour was that for many, but not all skills, it calculated spacing based on the area they would have had if they had no "+x to radius" modifiers. This is clearly a bug and meant it was inconsistent between different skills, and different ways of changing area of effect. We changed the behaviour back for curses for this patch to avoid people being stuck with a build that works differently to how they expect, but as stated, we'll be fixing the bug again in 3.23.0 Last edited by Mark_GGG on Aug 23, 2023, 3:35:17 AM
| |
" The relevant part of the patch notes regarding the spell cascade interaction says this: " I have also clarified my post earlier in the thread to make it explicitly clear, this patch reintroduces the bug so that spell cascade will again fail to see +radius modifiers on curses and thus not space them out as much, like before the patch. This behaviour was not intended, but it is being changed back to work that way for this league. The fix will be applied in 3.23.0. | |
"As it happens Reap and Stormcall are among the skills that didn't exhibit the bug - they apply additional radius in a way that meant Spell Cascade had the correct radius total, including the additional portion, so they were always spaced appropriately and their behaviour is unchanged. Last edited by Mark_GGG on Aug 23, 2023, 4:07:00 AM
|