UnknownX7 / NoClippy

A XIVLauncher plugin.
128 stars 36 forks source link

Plugin disabling itself when it didn't before #35

Closed jmrs2603 closed 2 years ago

jmrs2603 commented 2 years ago

I used NoClippy along with XIVAlexander and ACT when it started activating its dry run out of nowhere mid-session and now won't stop switching back even though both of these separate programs have been disabled. This issue has only started happening today (08/31/22).

jmrs2603 commented 2 years ago

Forgot to mention that this only happens when I weave something, it says there's been an unexpected lock of around 500ms and enables dry run.

UnknownX7 commented 2 years ago

NoClippy does this when it detects that something else is already reducing the animation lock.

jmrs2603 commented 2 years ago

I'm not aware of anything else reducing the animation lock though.

UnknownX7 commented 2 years ago

Are you sure XIVAlexander is disabled? NoClippy is specifically detecting that the packet has an animation lock value that the server wouldn't send. Try to close Alex and see if NoClippy is still detecting it.

jmrs2603 commented 2 years ago

I am absolutely sure that Alex is disabled, I uninstalled it to try and troubleshoot.

UnknownX7 commented 2 years ago

Please send me %AppData%\XIVLauncher\dalamud.log as well as this,

Enable these two settings image and then use some skills on a mob and copy these lines from the chat and send them here. image

UnknownX7 commented 2 years ago

You have Double Weaver installed, which also reduces the animation lock. It was updated yesterday so it likely auto updated and reenabled. (I deleted the comment in case the log file contains any personal info that a plugin may have logged.)