Change the Escape native input to open Nanos Settings to F1
planned
louzzy
Most of the users have a natural habit of using Escape to close the current UI in most games.
Studies indicate that 40% to 60% of users frequently use the "Escape" key to quickly close modal dialogs, dropdowns, or tooltips.
Either change the Nanos settings input or give us the ability to use Escape input without triggering the opening of Nanos settings (I can understand that in that case if a script is broken the user will have to alt + f4, maybe we can find a way to bypass this issue).
Edit: third option could be giving the user the ability to change the input to open the Nanos settings
GTNardy
planned
I intend to provide a way to bind to that input to allow your custom implementation, but also to keep the Escape functionality so people won't get stuck on it
Aerox
It's possible to disable it in blueprint and rewrite on it in blueprint according to NegativeName
louzzy
Aerox I did not knew that, but I imagine I would need to rewrite in blueprint to make it do nothing and then bind to it in my lua script to be able the call my lua function. I would prefer Nanos to include a way of handling this. Thank you for the info !
shavkat
Or just have the possibility to rewrite it