ISBoxer.com

I'll try my best to explain the byzantine nature of this problem.

When config is exported every slave window sees {FTL} just fine. Follow works, assist works, etc.

Somehow randomly and I've never been able to pinpoint where one slave window will stop recognizing {FTL} and completely ignore me when I command follow or assist.

To get that window to recognize {FTL} again I have to make that window the master by switching to it and then switch back to my preferred master.

My profile is in parts, thanks to being very large though I have attempted to make it smaller over the years.

Part 1: https://pastebin.com/Z6k6gUc0
Part 2: https://pastebin.com/AeLH0eSd
Part 3: https://pastebin.com/0WAwQTk5
Part 4: https://pastebin.com/nBEtb7yW

When the FTL is being randomly lost, if you use the debug console, does it show that ISBoxer is not sending the FTL combo along with the key ?

Note that the modifiers will be numbers 160, 161, 162, 163, 164, 165.

Left Shift = 160
Right Shift = 161
Left Ctrl = 162
Right Ctrl = 163
Left Alt = 164
Right Alt = 165

Hi Bob.

I could not get the issue to replicate last night. I will try again in a bit with debugging on. Thanks!

Ok got two screenshots. You can see they both show the same keystrokes. Debug from SLOT 2 which exhibited the problem 5 minutes into a BRH run.

Before: https://ibb.co/dmNW28
After: https://ibb.co/mzeYFT

Note: The last one CTRL + SHIFT + F12 is the slot switch as I can't see Slot 2 debug window without focusing it.
Note: CTRL + ALT + SHIFT + 0 is the IWT keybind. I have that on /follow to get in passenger mounts.

Anyway you can clearly see slot 1 issued a follow FTL on shift + F11 and slot 2 received it in both scenarios. Something seems to be wrong with FTL.

Also saw the same problem on slot 3 in the same dungeon run. 1 boss apart basically.

I'm not seeing anything where FTL actually stops.
If FTL stopped, then you wouldn't have the modifiers on the keystrokes, which is what FTL is. You do have the modifiers, so FTL is working.

As the keystrokes appear to be sent to the game, it sounds more like the game is not processing the keystrokes. Which it can do if there is something else interfering (something else hooking the game perhaps), you flood it with commands, or there is something else (another addon perhaps?) that is grabbing the keystrokes (not sure how it would do this).

H Bob.

I'm going to disable everything but IsBoxer and GnomeSequencer and run another dungeon. I'll let you know if I can replicate it again.

One BRH down and no failures yet. Going to run another and see if I can get this sucker to show again.

Ok, interestingly I disabled everything but ISBoxer and GS and well.. the problem went away.
I then turned on BT4 (bartender) and some smaller addons like tomtom. I'm still looking but I think something with BT4 and the speed of these modifiers are causing the problem. Only speculation but maybe BT4 is a fraction of a second slower than a standard keypress. No idea really but when BT4 is on the problem happens and it also seems to matter the more addons that are enabled the more common the issue is. Whichever it is, some kind of machine delay in processing is causing modifiers to overlap on keystrokes they shouldn't which is causing commands to fail.