Disable keyboard shortcuts for menu/auto/skip/etc?

Help
1

I’m encountering issues with text inputs where typing “a”, “s”, “m,” “n,” etc in the text input field activates the keyboard shortcuts as noted on the buttons. That is, if I type “Tom” in the input field, the m also opens the menu.

Is there a way to disable these shortcuts, either in general or while the text input field is active? Apologies if this is obvious. I can’t find mention of this in the docs or forum, can’t find any yaml files that reference this either–there is an option to hide the image of the shortcut key but that doesn’t turn off the functionality.

2 Likes
2

I tried to turn mine off using the following in my common.yaml
I don’t know off-hand if this is correct or accurate.

hotkeys:
  skip: false
  autoPlay: false
  viewportSelect: false
  subNextTab: false
  subPreviousTab: false
  nextTab: false
  previousTab: false
  menu: false
  system: false
  cancel: false
  continue: false
  up: false
  down: false
  left: false
  right: false
  debug: false
2 Likes
3

I also ran into this and came here looking for an answer!

I’ll give the common.yaml edit a shot. I didn’t even know AutoPlay was a thing in VNs.

4

It’s a thing in most of them, and a built in feature in many engines like renpy

1 Like
5

I thought I had fixed this bug with the keys interfering… In any case there is a way to disable those hotkeys in the settings as other games did it as a solution

1 Like
6

Thanks for this, adding this into common.yaml worked. No need to expand on this since the problem is solved, but just for my own curiosity, how did you know to add that to the file? Is there some list of configurations that can be added to common.yaml aside from what’s there by default?

7

I can’t remember if I found it in the documentation, or if if I had asked @Liana for help. The documentation is pretty comprehensive though.

Also, for what it’s worth, I created a new narrat project and added the text_field command, and did not have this issue. An existing game I had that I upgraded narrat on still has this issue, so I’ll have to look into it more.

But if a new narrat project isn’t having this issue, then I’m fairly certain the problem is with something I’m doing on my end. And since I have some custom JS, it wouldn’t surprise me if I broke something. :rofl:

Perhaps it’s an old version causing your issue?

8

I don’t think it’s an old version. The project this occurs in was created on 10/30/24 and I installed Narrat for the first time on 10/15/24.

Also confirming I found the hotkeys section of the documentation–I think this was an example of me not remembering the name “hotkeys” and instead looking for “keyboard shortcuts,” lol. Though the documentation seems to suggest that hotkeys are off by default–the example shows how to enable “m” as the menu shortcut by adding to the common config despite it already being enabled in a new project. Not like that really matters too much though.

1 Like
9

For other improvements and fixes, can you check your version anyway?

I’ve pulled down old versions using npm before. I don’t understand why it’s happened, but it has. I fought an old bug for over a day before realizing I had pulled a version several years old. :rofl:

10

image
image655×326 20.9 KB

version 3.16.1, looks like

11

Thanks for the pointers folks. I did get confused by something - I can disable the hotkeys, so they don’t work when I start the game, but if I use the debug menu to jump to a node, the hotkey seems to be re-enabled. Is that just a consequence of using debug features?

(Also running 3.16.1, if that matters)

12

FWIW I cleaned up some of my code on the upgraded game, and it no longer accepts shortcut keys inside the textbox. That was definitely entirely my fault. :smiley:

Pulling up the debug menu does cause them to work in the textbox again. Thankfully that’s not triggered by people playing the game.

1 Like