LOCKIN

LOCKIN is a Valorant agent instalocker. Pick one global agent, or assign agents per map, arm it from the dashboard, and LOCKIN automatically locks the right agent when a match is found.

Features

• 100% automatic: arm once and LOCKIN handles detection, selection, locking, and re-arming between matches, even when alt-tabbed.
• Plug and play: automatically detects your Valorant session, region, client version, and Riot connection details.
• Smart lobby detection: uses live Riot Client events with polling fallback for reliable pre-game detection.
• Map-aware locking: lock one global agent on every map, limit that agent to selected maps, or assign a different agent per map.
• Auto-updating agents and maps: pulls current agents, maps, and ranked map pool data at startup.
• Minimal background footprint: stays lightweight while waiting for a lobby.

Requirements

• Windows
• Valorant running

Run

Download the latest .exe from the releases page, and run it.

For development runs from the project directory:

cargo run --release

Or build the binary:

cargo build --release
.\target\release\LOCKIN.exe

When LOCKIN starts, it prints the dashboard URL:

LOCKIN dashboard: http://127.0.0.1:8787

If port 8787 is busy, LOCKIN tries the next local ports automatically.

Basic Usage

1. Start Valorant and reach the game menu.
2. Start LOCKIN.
3. Open the printed dashboard URL.
4. Choose a selection mode.
5. In Global mode, choose one agent and optionally choose allowed maps.
6. In Per map mode, choose an agent for each map you want LOCKIN to handle. Maps with no agent are skipped.
7. Choose detection mode.
8. Press Arm.

When a pre-game lobby is detected, LOCKIN resolves the match, checks the active selection mode, then sends the lock request or skips that map.

Dashboard Controls

• Selection mode:
  • global: choose one agent, then optionally filter which maps it can lock on.
  • per_map: choose a separate agent for each map. A map set to No agent is skipped.
• Agent list: in global mode, choose the single agent LOCKIN should lock.
• Maps: in global mode, choose maps where LOCKIN is allowed to lock. No selected maps means all maps are allowed.
• Per-map agents: in per-map mode, click a map's agent picker to open the agent grid and assign or clear that map's agent.
• Select before lock: sends a select request before the lock request.
• Auto re-arm: after a terminal outcome, waits until game is over and arms again.
• Detection mode:
  • websocket: listens to Riot Client local websocket presence updates.
  • polling: checks the pre-game player endpoint repeatedly.
  • hybrid: uses websocket detection with a polling fallback.
• Arm: starts live detection.
• Disarm: stops detection and clears runtime state.
• Event Log: shows recent runtime events, warnings, and errors.

Runtime States

Common states shown in the dashboard:

• idle: not armed.
• arming: refreshing Riot live data.
• detecting: waiting for a pre-game lobby.
• resolving_match: pre-game was detected and LOCKIN is resolving match data.
• locking: match data is ready and LOCKIN is sending select/lock requests.
• locked: selected agent is locked or already locked.
• locked_other_agent: your player is already locked on a different agent.
• skipped_map: the lobby map is filtered out in global mode, or has no assigned agent in per-map mode.
• waiting_menus: waiting for Valorant to return to menus before auto re-arm.
• warning / error: a recoverable warning or hard failure occurred.

Configuration

LOCKIN stores settings in lockin-config.json next to the executable during normal runs, or in the project root when run through Cargo.

Example:

{
  "selection_mode": "global",
  "selected_agent_uuid": null,
  "selected_map_urls": [],
  "per_map_agent_uuids": {},
  "select_before_lock": false,
  "auto_rearm": true,
  "poll_ms": 250,
  "detection_mode": "hybrid"
}

Most users should change settings through the dashboard instead of editing JSON manually.

Troubleshooting

• Valorant session was not found: start Valorant before pressing Arm.
• Riot lockfile errors: make sure Riot Client is running.
• No agents or maps shown: check internet access; public data is fetched at startup.
• Websocket detection misses a lobby: switch to hybrid or polling.
• Lock did not happen immediately after pre-game: Riot endpoints can lag behind presence. Try to switch to websocket or hybrid modes.
• Wrong map skipped in global mode: clear map selection or verify the map is selected in the dashboard.
• Map skipped in per-map mode: assign an agent to that map. No agent means LOCKIN should skip it.

Development

Useful commands:

cargo test
cargo build --release

LOCKIN runs on your machine and reads Valorant local state through Riot Client local APIs.

Important files:

• src/main.rs: startup, config location, dashboard binding.
• src/app.rs: app state, config, UI phase model.
• src/detection.rs: detection modes, lock sequence, auto re-arm flow.
• src/riot.rs: Riot local/auth/API/websocket helpers.
• static/index.html: dashboard UI.

The dashboard API is local-only and served on 127.0.0.1. State updates are streamed with server-sent events from /api/stream.