Spaekona's downpress toggle

I've been seeing that a lot of BLM use a toggle to equip spaekona's +1. I was thinking it would be better to have something where I press down on a key, and while it's pressed down, it will equip spaekona's +1. Then when I let up, it will unequip it. Would anyone mind writing that code, or at least pointing me in the general direction of how to do that? Would be much appreciated. I'm using mote's blm lua if that makes any difference.

bind k input /equip "Spaekona's +1"
bind k up input /equip "Idle Gear"

I'm afraid you've misunderstood what I'm asking. I'm not asking for code to merely equip the gear. I'm asking for code that will equip it when I'm holding down the key, and then when I release the key, it unequips it.

Let me try it. I'll see if it does what I had in mind.

Since I'm using Spaekona's coat, it has a ' in there. It should be something like this 

send_command('bind !n input /myrkr')

But because Spaekona's is in there, it prematurely thinks the command is ending.

I've been seeing that a lot of BLM use a toggle to equip spaekona's +1. I was thinking it would be better to have something where I press down on a key, and while it's pressed down, it will equip spaekona's +1. Then when I let up, it will unequip it. Would anyone mind writing that code, or at least pointing me in the general direction of how to do that? Would be much appreciated. I'm using mote's blm lua if that makes any difference.

you would need to use

windower.register_event('keyboard', function(dik, flags, blocked)
end)

Thank you, but I'm going to need a little more guidance sdahlka. I'm not even a padawan lua coder.

Thank you, but I'm going to need a little more guidance sdahlka. I'm not even a padawan lua coder.

the only thing i can tell you is that

dik = key(number)

flags = key orientation(number)

blocked = is this key blocked so FFXI does not see it(bool)

what you can do is

windower.register_event('keyboard', function(dik, flags, blocked)
    print(dik,flags)
end)

it will print out the key id and the flag info to the windower console

but as i have no idea what the key id's are or what the flags are thats all i can tell you

unfortunately this page has no info on the key id's in number form http://wiki.windower...wer:key_mapping

tho these might be what your looking for for the dik key codes https://community.bi...ki/DIK_KeyCodes

and this page has no info on anything eather http://dev.windower....pi:events:start
 

Since I'm using Spaekona's coat, it has a ' in there. It should be something like this 

 

send_command('bind !n input /myrkr')

 

But because Spaekona's is in there, it prematurely thinks the command is ending.

Escape the single quote (\'s Coat), or use double quotes.

The link for the dik values looks correct. There's also a (less complete) table in Yush.

I'm pretty sure there's a fourth parameter for the keyboard event.

dik(number): indicates the dik code for the key pressed

down(boolean): indicates if the key is up or down

flags(number): a bit field which indicates which, if any, modifier keys are pressed

blocked(boolean): indicates whether the key stroke should be sent to the client (note: windower doesn't currently block the input even if blocked is true. It's still useful for determining if another addon has already successfully processed the key stroke. Return true (defaults to false) from the keyboard event to set blocked.)

Arcon explained that the flags parameter is passed a seven bit long bit-field with the following flags:

    flags |= ShiftIsDown << 0;
    flags |= AltIsDown << 1;
    flags |= ControlIsDown << 2;
    flags |= WinIsDown << 3;
    flags |= AppsIsDown << 4;
    flags |= ChatOpen() << 5;
    flags |= down << 6;

The sixth bit (starting from 0) indicates whether the key is down or up, and is pulled off by Luacore and used to determine the down parameter.

I think I remember there being a bug with the flags value. If you press a modifier key and then press and hold a non-modifier key, flags might have been 0 sometimes. I haven't checked in the last year, though.

Iryoku's suggestion will work. You could switch the equip command to a gearswap command if you use gearswap, which would avoid some client spam.

Escape the single quote (\'s Coat), or use double quotes.

 

 

The link for the dik values looks correct. There's also a (less complete) table in Yush.

 

I'm pretty sure there's a fourth parameter for the keyboard event.

if thats true the someone needs to update the dev wiki really badly

because all it has is

event name--

keyboard

Arguments--

number dik
number flags
bool blocked

Return--

bool

Description--

Triggers on any keyboard action, including release of a button. Optionally returns a bool indicating whether or not the keyboard action has been caught. If true, it will not be passed on to the next stage, so the keyboard action would never reach the game.

Iryoku's suggestion will work. You could switch the equip command to a gearswap command if you use gearswap, which would avoid some client spam.

What would be the gearswap command for this? I am interested as being able to hold a key down to ensure my Automaton Enimty+ gear stays on when it performs Provoke/Flash or under certain situations would be really handy rather than what I currently have which is a toggle system.