Regarding key presses in an action game.

[LordSunder]

I've been having some trouble with the UI so far, so I have a few questions relating to that.

1. Maybe I missed it, but is there some way to lock the keyboard so that key presses register only in the text editor while the element inspector is open? If I need to hit enter or Z in the game I'm working on, for example, those are confirm buttons that will move me to the next screen. Problem: I may need to use those to input 'z' or 'new line' in the editor, but do not want to move to the next screen. I can only imagine the headache involved in correcting text for a unity game that uses WASD movement controls.

2. Is there any way to expand the text selection portion of the 'actions' editor to be more than a narrow slot? There's so much empty space around it in the element inspector window, but I can't just... drag that corner down and out so I can see a bigger portion of the text list? Super frustrating.

3. This is more of a bug report, but if you drag the element selector around and it gets too close to the top of the game window, it's just stuck there now, because seemingly the only way to move it is by dragging the top section of the box. Any way to forcibly reset its position?

4. What does the 'capture keys only' setting actually do? It says it 'saves text for manual translation' but if so where does it save it to? It's not translations.json, and otherwise, I have no idea. If it works like how it's suggested to, does it capture text from the game window automatically while playing, or do I need to bust out the element inspector to capture each new line of dialogue like it's a polaroid camera?

The scrolling is super fast and imprecise too, which works fine for the options menus, but for the text selection it makes it really easy to skip over text entries entirely if there's more than five or so of them. I can't expect to edit that in options on my end, but it does bear mentioning.

I get that this seems designed more for AI auto-translations than it is for humans to tinker with game text directly, but it's a little painful to try to use it for anything manual at the moment, unless I've missed something?

[djethino]

Hello,

Sorry for the delay, I'm in vacation since the last week and I just see your message.

1. Locking keyboard to the editor only

Unfortunately no, and it's a Unity limitation rather than something I can easily work around. Most Unity games read inputs through Input.GetKey(), which returns true regardless of which UI element has focus. A mod that "consumes" a key would have to globally patch the game's input system, which would break any game that uses Input.GetKey directly in custom ways (which is most of them).

2. Resizing the text list in the Element Inspector (TextEdit mode)

The panel itself IS resizable — grab the bottom edge or corner of the inspector window and drag. If that doesn't seem to do anything, there's a known constraint: the panel's max height is currently capped by the measured content height, so the scrollable text list doesn't claim that "extra" empty space. I'll fix that — the text list should grow to fill the available space when you enlarge the window. Tracking this as a bug. (I'll add it to my list)

3. Inspector stuck at the top of the screen

Confirmed bug — if the title bar goes above the screen edge, you lose the drag handle. Two ways to recover right now:

• Open config.json in the mod folder, find the window_preferences section, and delete the entry for "Element Inspector" (or just delete the whole window_preferences block to reset all panels). Restart the game.

• Or change your game's resolution — the mod detects resolution changes and re-centers panels. I'll add a safeguard so the title bar can't be dragged off-screen.

4. What "Capture keys only" actually does

The label is misleading, sorry. It does NOT capture from the Element Inspector — it works automatically as you play. Concretely:

• Every text the mod scans from the game (via its normal scanner) gets added to translations.json with an empty value, tagged as "H" (Human-to-fill).

• It does not call the AI, so no translations are generated.

• The idea is to harvest the full text inventory of the game while you walk through it, then fill the empty values manually in the file (or via the in-game editor) afterward.

• keys are saved in translations.json.

5. Scrolling speed in the text selection list

Fair point — the scroll sensitivity is currently hard-coded and tuned for short option lists, which makes long lists overshoot. I'll either lower it for the text list specifically or add a sensitivity setting. Thanks for flagging it.

6. AI-first vs. manual workflow

You're not wrong — the UI was built around the AI/online sync workflow first, and the manual editing path has rough edges. To edit the keys manually you have to do it on the website in the edit translation view (in "my translations") or directly on the translations.json file. I was thinking about adding an editor with captured keys dictionary in the UGT game UI, but the problem with keyboard focus will be the same as you mentioned before.

The 3 issues above (resize, stuck panel, scroll precision) are all real and I'll prioritize them since they make the manual workflow much more painful than it needs to be.

Keep the feedback coming, this kind of report is exactly what helps me prioritize !