Constant movement can be misclassified as AFK and dropped as a target #11

Bug

AFK detection in src/bot/bot.ts is based on how long the observed input has remained unchanged.

inputIdle() treats a player as idle once seen.changed is older than AFK_TICKS. A player can still be actively moving while holding the same direction/aim/hook state for that entire period.

User effect

An opponent who continuously moves with an unchanged input pattern can be classified as AFK and filtered out by target selection even though they are visibly playing.

This can look like the bot randomly stops fighting a moving player.

Reproduce

1. Let an opponent hold one movement direction continuously.
2. Keep aim/input otherwise stable and avoid attacks long enough to exceed AFK_TICKS.
3. Observe target selection / AFK state.

Expected

Movement/activity should not be inferred only from input changes. Consider observed position/velocity and other actual activity signals as well.