I’ve tested this and found that Conduit does not work until you have taken at least one point in Thundering. We’ll look into a fix.
Thanks for the report!
I’ve tested this and found that Conduit does not work until you have taken at least one point in Thundering. We’ll look into a fix.
Thanks for the report!
Thanks, I’ve confirmed this and made a note of it internally.
Thanks, I’ve confirmed this and made a note internally.
This topic was automatically opened after 24 hours.
I’ve confirmed that this is a bug with Shock in general. Resistance Shred ailments have reduced effects on players as intended, however.
Thanks for the report!
I’ve confirmed this and we’ll look into it. Thanks!
This issue has now been resolved. Thanks for bearing with us!
This issue has since been resolved.
The EHG Post Tracker has been disabled due to a compatibility issue.
Starting 10 minutes from now we'll be performing maintenance on our forum.
We anticipate this lasting for approximately half an hour.
External link →Thanks, I’ve confirmed this internally and we’ll look into it.
The bug only happens with “Move or Attack” - “Move Only” and “Move or Break Destructible” work fine.
I’ve fixed this internally. Thanks!
Thanks, I’ve confirmed this and we’ll look into it.
Thanks, I’ve looked into these bugs and confirmed them. Flame Ward’s Infusion node is a separate problem from the items-- I think the “increased fire damage” buff is applied to the player after the Fire Aura is made, so it isn’t applied.
Thanks for the reports!
Heyo!
In cases where a patch has either removed quests that grant passive points, or changed the rewards for those quests, your character will have more passive points spent than they are entitled to - and so earning additional passive points through leveling or completing quests will not result in additional passive points being available to you until the number of passive points your character is entitled to is once again greater than the number which they presently have allocated.
Closing thread for 24 hours.
Hey all,
Just dropping in with an update on our status. We currently have a fix for this in QA that we hope to push live within the next few days. I’m very sorry this went on for as long as it did.
This should be fixed as of 0.7.10c. Please let us know if anything else is missing. Thanks!
Thanks, I’ve made a note of this internally.