Controls

Kin and Conquest Mouse, Keyboard and Gamepad

Kin and Conquest mouse, keyboard, and gamepad guide: click-to-move, auto cursor follow, and why keyboard is often preferred in dense fights.

Last updated:

Kin and Conquest Mouse, Keyboard and Gamepad

This guide breaks down every official input method in Kin and Conquest and when to use it. The Fox Knocks describes the game as an incremental idle action adventure where you guide a fox through mountain floors, defeat floor guardians, and eventually confront the Evil Geomancer. Combat is proximity-based—weapons fire automatically in range—so movement input defines survival. Steam and itch.io list mouse, keyboard, and gamepad support; Settings let you choose click-to-move or auto-follow cursor for mouse players.

Community demo feedback consistently shows a pattern: mouse feels ideal on Floor 1, keyboard often becomes preferred by Floor 2 and Floor 3 when packs compress space, and gamepad splits the difference for controller-first players. This page explains those tradeoffs without prescribing a single meta—pick the scheme that minimizes telegraph deaths on your current floor guide tier.

Mouse: click-to-move

Click-to-move is the precision option. Each click sends your fox toward a destination, which works well when:

  • Mining ore nodes between waves—you click near the node, dodge outward, click back.
  • Learning guardian telegraphs—you choose exact retreat tiles.
  • Pausing movement implicitly by not clicking, letting you read upgrade menus.

Because attacks are automatic, click-to-move players still watch swing arcs and enemy density. Demo reviewers praised readability—easy to see your fox and mobs even in busy scenes—which helps mouse users track where the next click should land.

Weaknesses: Rapid reversals during add-heavy guardians require many clicks. If you mis-click near hazards, pathfinding may take a suboptimal route. Pair with deliberate pacing rather than spam clicking under the fox sprite.

Mouse: auto-follow cursor

Auto-follow cursor (toggle in Settings per store description) moves the fox toward your pointer continuously. This is the game’s idle-friendly mode: hover near safe zones while monitoring blessings, skill tree purchases, and upgrade screens.

Strengths:

  • Lower click fatigue during long incremental farms.
  • Natural pairing with kill-count challenges that extend sessions.
  • Comfortable for players who treat Kin and Conquest as a secondary monitor game.

Weaknesses reported by players:

  • Auto pathing may focus totems or pickups over combat safety—some wished totems could be disabled or unequipped from auto priority.
  • Landing on a new floor can spawn interactables near your feet; demo feedback noted instant totem activation before moving (later patches adjusted timing).
  • Guardian fights need micro-dodges auto-follow handles poorly compared to keyboard strafing.

Recommendation: use auto-follow for Normal farming until deaths spike, then switch to click-to-move or keyboard for guardian attempts.

Keyboard: why many players switch

Store copy explicitly says keyboard is available “if you prefer”—and many players do once difficulty rises. Keyboard typically maps directional movement to WASD or arrow keys (exact bindings may appear in Settings or pause menus; verify in-game after patches).

Why keyboard often wins late:

  • Instant direction changes dodge circular telegraphs faster than pathfinding to cursor targets.
  • Stable spacing for proximity swings—you orbit enemies at consistent range instead of overshooting clicks.
  • Focus on guardians where add waves punish idle drift.

Playtest feedback sometimes wished for hybrid manual attack (e.g., WASD plus mouse button) because automatic weapon targeting occasionally strikes the wrong enemy or ignores boss priority. That feedback reflects genre tension, not broken controls—The Fox Knocks intentionally kept attacks automatic for idle accessibility. Keyboard solves what you can control: position.

If you currently die with mouse auto-follow enabled, try keyboard for ten minutes on the same floor before assuming you need more blessings. Pair with blessing picker planning only after input feels stable.

Gamepad

Gamepad support targets players who want analog movement without a mouse on a desk. Sticks offer fine gradations for kiting—pull back slightly when a telegraph charges, push in when a pack thins.

Tips for gamepad users:

  • Confirm dead zones in Windows controller settings if movement feels sticky.
  • Switch to keyboard or mouse for menu-heavy upgrade sessions if UI navigation feels slower—incremental games spend significant time in menus.
  • Re-center camera or zoom if available; readability was a demo strong point, but living-room distances strain small telegraphs.

Gamepad is viable for Normal clears and many guardians; hardest content may still favor keyboard precision per community reports, not official mandates.

Switching schemes mid-campaign

Kin and Conquest allows changing Settings between runs or floors. Suggested workflow:

  1. Floor 1 Normal — mouse click-to-move or auto-follow to learn proximity combat.
  2. First guardian wall — try keyboard or gamepad for one attempt before farming levels.
  3. Harder difficulties — stick with the scheme that cleared Normal guardians cleanly.
  4. Long idle farms — return to auto-follow mouse for comfort, swap back for guardians.

Log experiments on the progress checklist so you remember which input cleared which guardian tier.

Settings and accessibility checklist

Before judging difficulty unfair:

  • Toggle auto-follow versus click-to-move.
  • Test keyboard or gamepad if mouse deaths cluster in one direction (suggesting pathing issues).
  • Verify PC meets system requirements—2 GB RAM minimum, 4 GB recommended, 2–4 GB VRAM—to avoid frame hitches that look like input lag.
  • Read game review for colorblind-friendly praise in demo builds if visibility concerns you.

Controls in the bigger walkthrough picture

Input choice interacts with every other system:

  • Blessings — mobility picks reward keyboard players who can exploit haste windows.
  • Weapons — cleave weapons forgive positioning; single-target weapons punish auto-follow drift.
  • Floors — tighter arenas on deeper tiers amplify control differences (floors overview).
  • FinaleEvil Geomancer prep assumes you can execute movement under pressure.

Return to the controls hub for a shorter summary or walkthrough hub when routing floors after you settle on a scheme.

Mouse got Kin and Conquest its idle action label; keyboard often earns players their guardian clears. Gamepad sits comfortably between. Test all three—the mountain does not care which device you use, only whether your fox leaves telegraphs fast enough.

FAQ

Frequently Asked Questions

Quick answers for Kin and Conquest players.

Does Kin and Conquest support keyboard controls?

Yes. Steam and itch.io list keyboard movement alongside mouse and gamepad. Many players switch to keyboard for dense Floor 2 and Floor 3 fights even though mouse is featured in marketing.

How do I enable auto-follow cursor movement?

Official store text describes a Settings toggle that makes your fox move toward the cursor automatically instead of requiring clicks. Exact menu wording may vary by patch—check in-game Settings on launch.

Why do players prefer keyboard over mouse in Kin and Conquest?

Proximity combat rewards fast dodging during guardian and pack fights. Keyboard direction changes often beat click pathfinding or auto-follow when totems and pickups distract mouse movement.

Can I use a gamepad for floor guardians?

Yes, gamepad is officially supported. Analog sticks help kiting, though some players still switch to keyboard for the tightest guardian patterns on harder difficulties.

Do I need to click to attack?

No. Attacks trigger automatically in weapon range. Mouse clicks or keyboard directions only move your fox.

What should I do if auto-follow keeps chasing totems?

Switch to click-to-move or keyboard during that fight, or disable auto-follow in Settings. Demo players requested totem priority controls; verify latest patch notes on the [links hub](/links/) for QoL updates.