Files
my-botty/docs/d2r_window_input_troubleshooting.md
T

19 lines
968 B
Markdown

# D2R Window and Input Troubleshooting
Botty expects Diablo II: Resurrected to expose a stable 1280x720 client area. If
the live D2R window reports a slightly different client size, template matching
can still succeed while mouse clicks land at the wrong monitor coordinate.
At startup and before creating a game, Botty now resizes and positions the D2R
client area to the configured `config/game.ini` dimensions. The expected size is
`1280x720`, matching `assets/d2r_settings.json` and the template assets.
If a UI click is detected but the cursor does not visibly move, the native input
layer first tries `SendInput` and then verifies the cursor position. When
`SendInput` misses the target coordinate, Botty falls back to `SetCursorPos` and
logs the fallback.
If movement or clicks still do not reach D2R, check that D2R and the bot process
are running at the same privilege level. Windows can block input from a
non-admin process into an elevated game window.