as the title says, after patch 25.2 Ancient Craft is bugged when you trait enfeeble and it is actually almost half the value without using that trait.
as the title says, after patch 25.2 Ancient Craft is bugged when you trait enfeeble and it is actually almost half the value without using that trait.
Creeps:
Deathlyheals - R14 defiler | Deadlyline - R10 Warg
Freeps - FullyWrecked
#BringT2cBack
Yeah, this definitely needs fixing...
With Enfeeble:
Without Enfeeble:
They also killed our ability to keep up the enfeebled version of SoP:C https://www.youtube.com/watch?v=M5aZMOaHsh8
I disagree with the video in that I don't think it's an intentional change..
I think I know why this happens
Enfeeble SoP:C applies 2 effects that are probably separate effects:
The enfeeble version of SoP:C
A timer that applies the regular version after 10s
There's 2 categories of skills in the game:
Those were the newer version overwrites the older one
Those were the stronger version overwrites the weaker, but not vice versa
SoP:C seems to belong in the 2nd category
So let's say at second 0 you apply SoP:C with Enfeeble traited
2 effects get applied, SoP:C (enfeeble) with a 10s duration and a hidden timer with a 10s duration that applies SoP:C (regular) when it reaches 0
After 5 seconds you reapply SoP:C
The game checks the newly applied version and realizes it is the same strength debuff, therefore refreshes the duration
it also applies a second 10s timer effect - this does not refresh the old timer but both timers work simultaneuosly
So at this point you have:
SoP:C (enfeeble) for 10s
a 5s timer applying SoP:C (regular) at the end
a 10s timer applying SoP:C (regular) at the end
Now let's go forward in time another 5s:
SoP:C (enfeeble) still lasts for 5s
the first timer runs out
the second timer lasts 5s
The game wants to apply SoP:C (regular) and checks against the already applied SoP:C (enfeeble) which still lasts 5s. The game ignores secondary effects of debuffs (attack duration) and only checks primary effects (parry rating)
The game believes SoP:C (regular) is the stronger debuff than SoP:C (enfeeble) because the parry rating debuff is higher and overwrites it
Another 5s later the second timer runs out and the game again sees a newer version of the same debuff already applied (both SoP:C regular) and refreshes
If my theory is correct, scaling the Enfeeble versions to be higher than the regular versions like it should be would immediately bring back the old behaviour. It seems to me this is just a consequence of game mechanics in the background
EDIT: this theory could be proven or disproven with 2 Loremaster, if I'm correct untraited SoP:C should overwrite traited SoP:C immediately
So quick fix to all of these issues, get rid of the 10s window on Enfeeble and just make it the "doubled" effect. Seeing as how the doubling only applies to the base debuff amount and not to the amount added by legacies and traits it wouldn't be a true 200% effect for any of the rating based debuffs. Only the attack duration debuff from SoP:Command would truly be twice the amount of its untraited counter part, and attack duration is one of the weaker debuffs in our arsenal already.
So another update 25.whatever came out and no fix for this issue or on the others that we already have for so many time.
This is one capstone trait option that we lost here![]()
Has there been any feedback from devs on this issue?
Tilimir ~ Crickhollow
Not mentioned as a fix in this update either.
Is there valid hope for it to disappear magically just as it appeared? Until it comes back again.
Tilimir ~ Crickhollow
As I described on another thread about class slot LIs bugged for lvl 85 cap on the LS, the dev response to anything non Remmorchant related has been:
They do these things to LMs all the time. I stopped having the class as my main, but I was tempted to resume when the enfeeble trait got finally fixed. Too bad it didn't last.
Home base: Gladden• LI Reward Track Season 5 •
Its a bug, but easy to solve not to skill the last stone in tree.
bump![]()
As of July 23rd, 2020 (during the dark days of server "issues") -->
Has this been fixed or not?
I've read so much stuff about LM: this and that, that I don't remember what I've read any more.