Hihi!
I am aware of an issue where, if you're not tabbed in to EQ, the client is the foreground window and you send a message to that client, it will cause a misread on the client-side and connect/disconnect rapidly due to how we handle inputs.
This is due to the foreground window being hit for input always. Just make sure your clients are tabbed in to EQ before sending them any messages (clicking cool buttons).
If this happens to you and you find yourself stuck with the dreaded "duplicate handle" error, save any hotbar(s) you have open and restart your host-side.
Next update will implement a fix for this.
[CODE title="Nitty-Gritty of why this is happening"]IonBC doesn't inject, so it actually doesn't recognize it needs to send the input to EQ specifically.
We could circumvent this by using a p/invoke in C# called SendMessage/PostMessage.
The issue is these send virtual keystrokes.
Virtual keystrokes are picked up by the DirectInput wrapper and immediately rejected without even considering it as an actual key, so it's impossible to pass a message to the EQ client this way without injecting.
The p/invoke we DO use circumvents this as it goes at a lower level than Send/PostMessage and totally avoids the wrapper DirectInput/EQ holds over native process for handling inputs.
If we were to inject, that would break Daybreak's EULA and the whole point of IonBC was to create a program that eased boxing without injecting, like MQ or ISBoxer.
The cool thing about this, though, is it means this program isn't limited to just EQ. You can use it in any game or application you'd run over multiple PCs.[/CODE]
Next update will also come with some new features including individual event button toggles, in-line command targeting (think /bct) and some other jank!
If you have any questions, problems or concerns please shoot me a PM. Thanks fellas!
