Mouse Clicking Issues

Mr.Freddy,

Hey there, I'm back finally and working away trying to get click healing working with your addition of mouse keys. I seem to have stumbled on an issue though. I need a combination of keys to be able to be broadcast, for example:

<Hotkey RButton>
<SendWinM wow1>
<ClickMouse RButton>
<SendWinM wow2>
<ClickMouse RButton>

BUT.. What if I wanted the click to be performed as Shift+RightButton. The addon Clique is based on having combinations of keys and a mouse click to perform an action.

So.. I would try something like this:


<Hotkey Shift RButton>
<SendWinM wow1>
<ClickMouse Shift RButton>
<SendWinM wow2>
<ClickMouse Shift RButton>

That causes an unrecognized paramater error however. I may have overlooked something so please advise.

Secondly, sometimes it just fails to click through untill I manually click on the frame on the background character. I am unsure what causes it to stop working like this.

Lastly, How can I improve the speed or reliablity of it clicking through. I understand a pause put in for situations where you would click, then the mouse would be moved somewhere else and the click performed on the background screen. However, for my needs I simply and clicking right in the same exact place, I would think the NoMove parameter would increase the reaction time of the background click, but it does not seem to do so. Physically, the mouse stays in the same position on my screen, so clearly the need for the program to move a mouse is not needed. Shouldnt there be a way to make it VERY reliable and speedy without any pauses? Perhaps not! Let me know!

Thanks so much

little more info,

it just does seem to randomly stop responding. I have toyed with increasing the delay while using the MF command, but like I said, just sometimes its straight not working. I can spam the hotkey, no errors when looking at the hotkeynet gui, but I wont get any ingame reactions. Then it will start working again randomly.

This is build 116.

Sorry for the delayed response. I haven't been checking here recently. It sounds like the problem may have been due to a bug that was fixed in build 119. If that's not the case, please let me know.