Iced Edges stops working

[Jango-EX]

OK guys, I have a bard with Iced Edges and every once in a while I remember to check if it's working or not, while active, and sure enough, no ice damage is happening. I have to deactivate and activate again for it to work.

Does anyone else suffer with this issue? Is it a known issue, maybe related to Iced Edges in particular or some known bug happening with all of these new imbue thingies that I'm not aware of?

[copecetic]

same with my bard and "resonant arms"
everytime i log in i have to deactivate then reactivate the imbue or no sonic damage

pretty sure the imbues on my mage eldritch knight from spellsword work fine, whenever i log in they are on and working

maybe a bard issue?

[ReyalsNogard]

At least they are nice enough to outright turn the imbue off on my Arti so I don't have to guess.

[Firebreed]

Def bugged.

[Jango-EX]

Sooo... is it best to just not use bards and their imbues altogether? Will this be addressed at some point?

[Firebreed]

Sooo... is it best to just not use bards and their imbues altogether? Will this be addressed at some point?

We'd have to wait and see what's in the next patch, since the devs have decided to give us the silent treatment for the past 3 months. Given the volume of bugs that were uncovered during this period, it will be interesting to see what percentage of them gets fixed in the following patches (hint: it will be unfathomably low). Maybe one day the playerbase will finally prioritize bugfixing more in terms of what they want (and voice this concern), but for the time being it doesn't seem like bugfixing is something the devs feel very pressured on addressing.

[adamkatt]

Since they cant seem to ever get these on off abilities right i just turn them all off and back on again on first login...

[J1NG]

Hmmm, I've just tried this just now, and can't replicate this issue that the other players here in this thread has experienced.

With no other Imbue bonus, and just the Ice Edge (or Resonant Arms) toggles, they work for me after relogs and client restarts at this time.

Can anyone provide me what else they have on their characters when they experienced this? Enhanements and possibly Destiny choices?

J1NG

[copecetic]

Hmmm, I've just tried this just now, and can't replicate this issue that the other players here in this thread has experienced.

With no other Imbue bonus, and just the Ice Edge (or Resonant Arms) toggles, they work for me after relogs and client restarts at this time.

Can anyone provide me what else they have on their characters when they experienced this? Enhanements and possibly Destiny choices?

J1NG

bard 12/ rogue 2

swashbuckling and precision are the only other active enchantment/clickies/etc i have on
they stay on fine each time i log in
resonant arms still shows its on, on the hot bar, but its not as no sonic damage always have had to turn it off then on again on loading ever since inbues were introduced

cant post screenshot, have tried everything in the "post a pic" guides but have never been able to, i am just a scummy premium account so thats probably why

[SWCarter]

The Warlock ES imbue (Spiritual Retribution) also has to be re-enabled on every login. And the Aura of Courage, core 2 from the same tree. It's annoying because all of the other toggles persist and I occasionally forget to renew the two that don't.

[J1NG]

bard 12/ rogue 2

swashbuckling and precision are the only other active enchantment/clickies/etc i have on
they stay on fine each time i log in
resonant arms still shows its on, on the hot bar, but its not as no sonic damage always have had to turn it off then on again on loading ever since inbues were introduced

cant post screenshot, have tried everything in the "post a pic" guides but have never been able to, i am just a scummy premium account so thats probably why

Unfortunately, I am unable to replicate the experienced issues that has been reported in.

Purple Dragon Knight
Iced Edges, Resonant Arms, with Cores from WC, Cores from Inquisitive (to test if it's the Imbue dice giving issues), brought in an Alchemist to boost the Imbue Dice furhter. And this still doesn't replicate the issue. So the issue is unlikely to be Imbue dice related specifically.

I do have a Halfling Bard I can go and test next, but I suppose the next details I'll be asking is; what race is everyone experiencing issues with this issue on?

I also thought it might be Sneak Attack related, given the 2 rogue, however, with 1d6 sneak attack available on my PDK Bard, this did not show any issues after relogging either. The toggle remains active and the effects remain active.

Again, I'll go test if the Halfling Bard experiences this issue (possibly a Race specific issue).

J1NG

:: edit ::

Just tried this on a Halfling Bard, and there is again, no issues to report. The toggle remains on after relogs and client restarts. This Bard also has Precision, so it is not the Precision Feat related causing it to not apply whilst it appears the Toggle is on (when in fact it needs to be re-toggled).

Will require more information about the builds players have experienced this issue on. Race, Class Split, Enhancements, Destiny, Items. Need to find a common cause that exists between all of them, as right now, all the ones I can think of aren't testing positive.

[J1NG]

The Warlock ES imbue (Spiritual Retribution) also has to be re-enabled on every login. And the Aura of Courage, core 2 from the same tree. It's annoying because all of the other toggles persist and I occasionally forget to renew the two that don't.

I have been able to replicate the Spiritual Retribution imbue issue (toggling off after a relog), so will look into this further tomorrow as I've ran out of time for tonight. The Aura of Courage toggle however has always behaved like that if my memory serves, and thus is not really an unexpected issue that has recently surfaced.

In relation to the Bard toggles, whilst I haven't been able to further test it (yet), I can confirm that the Lighting the Candle in Henshin Mystic also remained on after application on a known buggy scenario. Again, will need more details from the players who experienced toggling issues to be able to test and try and locate a possible cause of issue.

J1NG

[archest]

activating one imbue turns another off?

[J1NG]

activating one imbue turns another off?

Toggles of the same "type", yes.

So Resonant Arms and Iced Edges will switch the other one off, as they are of the same type/category. Much like Power Attack and Precision turn the other off when they are toggled on.

There are however, various "types" of toggles; so the Prism toggle in Shiradi can be on whilst other toggles are on, as they are not in the same category. As is the "secondary" toggles of the Arcane Archer. So far, as I do not have a multi-class that has access to multiple Imbue from different classes, I am unsure if such a situation may allow more than one toggle (from each class enhancement) be allowed to be turned on. I am assuming not, but have not tested this yet.

J1NG

[J1NG]

The Warlock ES imbue (Spiritual Retribution) also has to be re-enabled on every login. And the Aura of Courage, core 2 from the same tree. It's annoying because all of the other toggles persist and I occasionally forget to renew the two that don't.

Just tested this on a PDK and a Dwarf Warlock, and in both cases, having just enough AP spent into Enhancements to get Spiritual Retribution, and having absolutely nothing else (No racial, no destiny, no reaper AP spent, no other toggle, including the Warlock Pact, or even any Guild Buffs or any gear or encumberance) both Spiritual Retribution and the Aura of Courage both turn off after logging/restart. Dying and reviving however, will maintain Spiritual Retribution tooggles on status.

As for whether these are bugs or not, I am unsure.

As I have a feeling that because Spiritual Retribution is applicable for Eldritch Blasts as well, which itself is in a bit of a weird grey area as to what it is (Spell? Yeah. Attack? Sort of. Ranged Attack? Could be.) especially after Eldritch Shapes are applied, these were possibly coded to turn off to prevent possibly other issues from arising after a relog/restart. Ever since the attempt at porting something similar to the GMoF during the ED update experienced setbacks, I'm assuming it's possibly related to the system employed by the Warlock blasts. So unfortunately this particular toggle issue might just be something we have to live with. Hopefully not, but I'm not putting much stock on this one getting altered.

J1NG

[Jango-EX]

I'm not even sure about it stopping working when logging off. It seems to stop working at random, even if it was working before in the same game session. In this manner, if the test consists of logging off and on again and trying to see if it sticks, I'm afraid it won't be enough to replicate the issue. I'm not sure though.

My toon is a gnome bard 16 /artificer 1 and the Iced Edges imbue stops working since forever.

My toggles are Death Watches You, Arcane Alacrity, Colors of the Queen, Power over Life and Death, Skill Mastery, Shadar-kai, Find Familiar: Fox, Power Attack and Iced Edges.

[Jango-EX]

Yep, I tested multiple logins, Iced Edges does not stop working between logins. It is another thing entirely that makes it stop working, unfortunately.

Had it been the case, the chore of always turning off and on when logging in would resolve the issue, but it does not. It seems random. I'll try to keep watching it to see if I find a pattern.

[CeltEireson]

Never had any issue with the resonant arms switching off and on during login. Have noticed some new graphic that seems to associated with some attacks that I never saw prior to the patch, perhaps i should have been and they fixed it - large white geometric symbol above a mobs head occasionally when im hitting it accompanied by a bell sound. Doesn't appear to be from the mobs given how infrequently they hit me.

[J1NG]

I'm not even sure about it stopping working when logging off. It seems to stop working at random, even if it was working before in the same game session. In this manner, if the test consists of logging off and on again and trying to see if it sticks, I'm afraid it won't be enough to replicate the issue. I'm not sure though.

I hope some players can see why the Devs look at some bug reports and wonder why some players bother posting right? :p :)

In all honesty though, that situation you're describing is not surprising. That's why some bugs are more annoying than others to track and find.

Currently, the potential cause list is simply, "everything else" in game at the moment. We need more info, and currently the only way to get that is through you with you keeping tabs on it (as you are doing now I note in your subsequent post). When you start to notice something a bit more, report back, even if it's not necessarily the correct replication process, at least it'll give us players who doubles up as player based testers the chance to eliminate ways for it "not" to replicate the bug.

J1NG

[Jango-EX]

I'm really not getting your point.

It seems to me that you are implying that it is MY job to debug this issue. Not at all, it's not even my job to complain.

I am a paying customer that is reporting an issue that needs to be corrected. I'm not getting paid to provide more information nor I need to be lectured about how bugs are tracked and corrected.

If that wasn't your point, I apologize.

Oh, and about the "only way to get that", I'm pretty sure that devs and debuggers have way more tools than I do to find problems and the fact that I'm reporting this may add additional insight to whatever bugs are being tracked, so don't be so sure about that. I can HELP if I want and that's all. I'm not REQUIRED to do it in order for my report to be valid. Iced Edges is bugged and that's it. In a level I'll reincarnate, probably won't use it again for years and won't personally care. Hope the devs can resolve this issue because it'll help DDO, not me.

[J1NG]

I'm really not getting your point.

It seems to me that you are implying that it is MY job to debug this issue. Not at all, it's not even my job to complain.

I apologise, my post you are refering to does indeed quote you and appears to be referring to you specifically, but the intial sentence was more of a critique of how some report of bugs by players can be much worse, or leave it so open ended that it makes it impossible to track on the player side who wants to help track it down so the Devs can get a quick fix in (since the work has been done by someone else already and they only need to check and confirm it rather than dig for an unknown amount of time to look for the offending piece of code causing the problem). On hindsight it should have been written more clearly and possibly distinct from the reply I made, as it is easily confused when not understanding the context it was made under.


Oh, and about the "only way to get that", I'm pretty sure that devs and debuggers have way more tools than I do to find problems and the fact that I'm reporting this may add additional insight to whatever bugs are being tracked, so don't be so sure about that. I can HELP if I want and that's all. I'm not REQUIRED to do it in order for my report to be valid. Iced Edges is bugged and that's it. In a level I'll reincarnate, probably won't use it again for years and won't personally care. Hope the devs can resolve this issue because it'll help DDO, not me.

I believe you might be misunderstanding something here.

The Devs absolutely have the tools to help track bugs down, but not always. That's why there's some old longstanding bugs in the game that aren't resolved.

My point about the only way to help track it down quicker - from further observed info from you, would be to allow players like me, who are happy to volunteer their time to help track down the source of bugs - on the player side - as we do not have the tools like the Devs do, so that we can give the Devs a more precise location of where the issue is and get a fix out for it sooner.

So it is not the Devs asking for more info, it is players like myself who are trying to help DDO overall by tracking bugs reported on the forums, and filtering out any bug reports that were posted in error (not actual bugs), so the Devs don't go on a wild goose chase for something that isn't a bug, and work on actual bugs that need fixing, or making new features for players overall.

This is of course, if you are happy to provide further info. Which is entirely voluntary on your part, as is the testing I and others do to help DDO. :)

J1NG

[Jango-EX]

Yeah dude, then tone down please, for future instances. I was pretty happy here talking about some issue that I crossed upon and now I really don't feel like going through hoops to find stuff. "Some reports can be much worse"? Please.

People report what they see, and be as specific as they can. Or not, whatever. It's not their job. I don't recall needing to pass through some kind of voluntary bug retention grid in order to report an issue.

I'm not happy about being lectured by another player about what I should or should not do either. You still seem to think that I need to learn something about bug finding from you. If you are volunteering to debug things OK, good for you. Just don't be condescending to others while you're at it.