Skip to content

bro69noscope/deadlock-movement-tracker

Repository files navigation

Seamlessly Switch between different in game locations and track your progress on movements routes by marking your attempts as successful/failed.

1770051523.-.February.02.17h58.mp4
Currently, improvement feedback is mostly achieved by aiming for the correct route multiple times in a row. Default is 3. A popup shows up to indicate we've successfully ran the same route x times in a row.
Coming soon: graph your progress with accuracy % per instances.

Setup

Requirements


Download

  • Click Code → Download ZIP on GitHub, or clone the repository
  • Extract it wherever you want

Configure Deadlock path and hotkeys

  1. Locate user_settings.ini in the repository root
  2. If you've installed Deadlock in a different location that the steam default, adjust:
    [deadlock]
    root=C:\Program Files (x86)\Steam\steamapps\common\Deadlock
  1. You can copy and backup user_settings.ini To be able to revert to defaults or repair a broken config easily. This file will be used to change all the settings for this script.

Enable console logging (required)

The tracker reads positions from Deadlock’s console.log.

In Steam:

  1. Right-click Deadlock → Properties
  2. Open Launch Options
  3. Add: -condebug

First run

  • Double-click deadlock-movement-tracker.ahk in the repository root.

On first run the tracker will:

  • Install or update mvtrack.ps1 in your Deadlock folder
  • Install or update mvtrack.cfg and mvtrack_pos.cfg in game\citadel\cfg
  • Prompt to add required lines to autoexec.cfg

Accept the prompt unless you already managed these lines manually.


Using the tracker (some default hotkeys)

You can change them in user_settings.ini.

  • F4 — Save current position as a new route start
  • F3 — Switch to an existing route start
  • F1 — Mark failed attempt and reset to start
  • F2 — Mark successful attempt and reset to start
  • F5 — Undo last success/fail entry
  • F9 — Close the tracker

Troubleshooting

If positions are not saved or restored correctly:

  • Verify Deadlock launch options include -condebug
  • Ensure you accepted the autoexec.cfg modification (or manually added sv_cheats 1 and exec mvtrack.cfg)
  • Check that the root= path in user_settings.ini is correct
  • Enable debug logging in user_settings.ini and open an issue/send a discord msg with the contents in: src\logs\debug.log
  • Keep in mind conflicts could be possible if you run your own scripts in autoexec.cfg that also bind the same keys as this script in deadlock

Uninstalling

  • Run uninstall.ahk in the repository root to automatically delete the auxiliary script/cfg files generated by this script.
  • After that you can delete the whole repository directory.
  • (If you want to keep your instances data for later use, save src/tracker_data)

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published