Demonologist osmosis shield vim drain bug

Where bugs go to lie down and rest

Moderator: Moderator

Post Reply
Message
Author
User23
Low Yeek
Posts: 6
Joined: Thu May 10, 2018 5:18 pm

Demonologist osmosis shield vim drain bug

#1 Post by User23 »

It appears that in some cases (I think it involves toggle dropping mobs) demonologist's osmosis shield vim drain can become permanent. My Demonologist is stuck now with -49 vim per turn with no toggles on. The osmosis shield animation is playing, and it likes like it's duplicated many times so the swirls are very thick.
Last edited by User23 on Tue May 29, 2018 1:15 am, edited 1 time in total.

Cathbald
Uruivellas
Posts: 743
Joined: Wed Jan 22, 2014 1:46 pm

Re: Demonologist osmosis shield vim drain bug

#2 Post by Cathbald »

it's a known bug though cause is unknown, it seems to involve having auto-use on osmosis shield and getting dispersed from what has been seen so far.
I write guides and make addons too now, apparently

You can go here for a compilation of everything I wrote, plus some other important stuff!

Includes general guides (inscriptions, zone, prodigies), and class guides (Demo, Anorithil, Bulwark, Zerker, Sblade)

User23
Low Yeek
Posts: 6
Joined: Thu May 10, 2018 5:18 pm

Re: Demonologist osmosis shield vim drain bug

#3 Post by User23 »

Is this kind of thing fixable with the lua console?

HousePet
Perspiring Physicist
Posts: 6215
Joined: Sun Sep 09, 2012 7:43 am

Re: Demonologist osmosis shield vim drain bug

#4 Post by HousePet »

Yeah you could disable everything and set your vim regen to 0.
My feedback meter decays into coding. Give me feedback and I make mods.

Shibari
Cornac
Posts: 37
Joined: Tue Jun 25, 2013 2:39 am

Re: Demonologist osmosis shield vim drain bug

#5 Post by Shibari »

If you can figure out a way to reproduce this let me know, my attempts have failed. Whats actually happening is really clear (ability activates, somehow, like 10 times, without removing the stored values of the previous activations) but that shouldn't be possible. Strongly suspect it has to do with autouse. Were you using that?

Post Reply