ctrl button bug

[rock5]

While testing to try and fix the RoMScript problem of sometimes returning nil. I discovered a bug.

When pressing the ctrl key in any application, the rombot stops until the ctrl key is released again. Well it doesn't actually stop but causes communication failures with the client.

I thought rombot was only supposed to detect keypresses in the mm window and client? Or is the ctrl key interfering with the macro execution?

Ok just checked, yes it is because ctrl-0 is mapped in the game client. When that key map is removed it works much better.

On second thought this is probably a known issue. Not really anything we can do about it except remove the ctrl-0 key bind.

Maybe I should add a check when the macro is set up to check for shift, alt and ctrl combos of the command macro hotkey then issue a yellow warning in the mm window. At least users would be aware of the potential problem.

What do you think?

[lisa]

Yeah ctrl + 0 is the default for pet action bar 10, so while you had ctrl pressed and bot was trying to use MACRO key RoM was trying to use a pet action bar. Using alt would have same kind of result as alt + 0 is the default for extra action bar 10.
Having a yellow message pop up would just remind people of this and they would need to go and delete those 2 key bindings from inside RoM.
Fortunately you only need to do this once per PC as the settings changed in key bindings are for any acc/chars played on that PC.

[Administrator]

When pressing the ctrl key in any application, the rombot stops until the ctrl key is released again. Well it doesn't actually stop but causes communication failures with the client.

That's a bug with RoM, not the bot or MicroMacro. The developers thought it would be a good idea to look for modifiers globally.