I think Ashita would benefit from having a chat mode check before handling keybinds.
If a key is bound you can never unbind it since you can't type that letter into chat, also when attempting/typing it executes your bind instead.
Info:
I noticed when hovering an npc it shows like a circle icon to indicate that you can interact with the NPC.. but when in chat mode that icon doesn't show ;)
I think Ashita would benefit from having a chat mode check before handling keybinds.
If a key is bound you can never unbind it since you can't type that letter into chat, also when attempting/typing it executes your bind instead.
Info:
I noticed when hovering an npc it shows like a circle icon to indicate that you can interact with the NPC.. but when in chat mode that icon doesn't show ;)
This should now be fixed in Ashita v3.0.0.14 that was just pushed.
As for your mouse mention, that is how the game reacts the mouse when there are menus open. They take priority over npc hovering when any type of menu system is open in the game. (The chat bar counts as a menu.)
This should now be fixed in Ashita v3.0.0.14 that was just pushed.
As for your mouse mention, that is how the game reacts the mouse when there are menus open. They take priority over npc hovering when any type of menu system is open in the game. (The chat bar counts as a menu.)
Sorry to say, but this update broke keybinds in Final Fantasy 11. Since Ashita has updated all keybinds are non-functional, including print screen and the F-key default binds.
Sorry to say, but this update broke keybinds in Final Fantasy 11. Since Ashita has updated all keybinds are non-functional, including print screen and the F-key default binds.
Another note, if I do a command to add a bind, like /bind ] /map It will work 1 time, then no more until I type the command /bind ] /map again. Strange.
Another note, if I do a command to add a bind, like /bind ] /map It will work 1 time, then no more until I type the command /bind ] /map again. Strange.
This update also refixes the IsInputOpen function not working properly.
I have adjusted this to now require users to enable this feature manually via the new command:
/bindblock
More information can be found here:
http://ashita.atom0s.com/forums/viewtopic.php?f=2&t=139
This update also refixes the IsInputOpen function not working properly.
atom0s
I think Ashita would benefit from having a chat mode check before handling keybinds.
If a key is bound you can never unbind it since you can't type that letter into chat, also when attempting/typing it executes your bind instead.
Info:
I noticed when hovering an npc it shows like a circle icon to indicate that you can interact with the NPC.. but when in chat mode that icon doesn't show ;)
This should now be fixed in Ashita v3.0.0.14 that was just pushed.
As for your mouse mention, that is how the game reacts the mouse when there are menus open. They take priority over npc hovering when any type of menu system is open in the game. (The chat bar counts as a menu.)
Sorry to say, but this update broke keybinds in Final Fantasy 11. Since Ashita has updated all keybinds are non-functional, including print screen and the F-key default binds.
Another note, if I do a command to add a bind, like /bind ] /map It will work 1 time, then no more until I type the command /bind ] /map again. Strange.
I have adjusted this to now require users to enable this feature manually via the new command:
/bindblock
More information can be found here:
http://ashita.atom0s.com/forums/viewtopic.php?f=2&t=139
This update also refixes the IsInputOpen function not working properly.
@LyleVertigo - This should also fix your issues with the map binding you mentioned.
Thank you very much for the quick fix!