TLI ToolkitTorchlight: Infinite companionDownload

Trust

What the app reads and sends

TLI Toolkit is closed source, so you can’t read its code. What this page gives you instead is the plain list: what the app looks at on your PC, what it never touches, what it sends out and when, why Windows or your antivirus may warn about the .exe, and how to check that the file you have is the one that was published. The longer versions are Safety & privacy and the privacy policy.

What it reads

  • The game’s log file (UE_game.log), which the game writes once you press Enable Log. The tracker and the log-aware advisors work from it: maps entered, items picked up, exchange prices you looked up, minigames opening.
  • Game-area pictures for screen reading. Auto-read is on by default for Vorax, Tartarus and TOWER, and off by default for Arcana and Void Sea. Each tool has its own toggle. It reads when Auto-read is on and the advisor is open (or the log shows that minigame), or when you press Read now (Ctrl+Alt+R). The app first requests the game window. If that stream cannot open, it automatically captures the monitor containing the game and crops each frame locally to the game area. The monitor stream can include other desktop content before cropping; only the cropped game area is passed to the reader. Text recognition runs on your PC, offline. A separate failure-frame cache may keep pictures on your PC (up to 30). Its local-retention switch is on by default in Diagnostics (main menu). Cached failure frames are uploaded only with Send this frame; review the selected image first. Save frame also saves game images you may choose to attach in a bug-report archive.
  • Where the game window is (position and size), so the mini window and the rings on the game line up with it.
  • Its own files: its settings, history and saved prices, in the app’s data folder in your Windows user profile.

What it never does

  • It doesn’t read or change the game’s memory.
  • It doesn’t inject anything into the game or hook into it, and it doesn’t change game files.
  • It doesn’t send keys or clicks to the game: no macros, no automation. The only keys it listens for are its own hotkeys.
  • It doesn’t ask for or read your game account, your password or your login, and it doesn’t look into your browser or saved passwords. You don’t need an account to use it.

It is still an unofficial tool, so use it at your own risk.

What it sends, and when

Community and diagnostic uploads use a random install id. Linking the app to an optional account associates its community data with that account. Optional sync, publishing and account features are described in the privacy policy.

  • Public downloads. Prices and item icons (the price feed has a Settings switch), GitHub release information for update checks, and status.json from this site. They fetch public lists and send nothing from your game. A new version is downloaded only when you click Update, and installed only if its SHA-256 matches the one published with the release.
  • Run sharing, on by default. Finished maps go under a pseudonymous random install id (linked to your account only if you link the app) into the community tables (the hour a map started, its zone, items spent and dropped as ids and counts, your setup as game ids, the app version), with a once-a-day check-in. The first time the app starts, a notice says so with See what’s sent and Turn off, and no community upload is sent until it has been on screen for a minute or you have closed it. Settings → Community turns it off at once.
  • Minigame runs, on by default. A separate switch: finished Vorax and Tartarus runs (not practice runs) as boards, advice and moves, so the advisors can be checked against real games. No names, no screenshots.
  • Trade House price searches, while sharing is on. The item, the cheapest prices listed, the season and when, for TLI Toolkit’s own item prices.
  • Daily diagnostic summary, on by default, once a day at most. Failure kinds, item ids, counts, app version, screen size, and page and tool-use counts, with the random install id. No paths, names or pictures in this automatic summary. It uses its own switch in Diagnostics (main menu), independently of community sharing; its own notice offers Turn off.
  • Automatic reader incident reports. With diagnostics on, the app automatically sends private reports for problems observed during Vorax or Tartarus reads. Each report uses predefined codes for the observed steps, field results and image status, with the app version and random installation ID. The report can also include time between steps, capture dimensions, attempt numbers and response status codes. It contains no image, recognized text, paths or raw log lines. If a replay image exceeds its size or daily limit, the incident report can still be sent.
  • Manually shared developer logs. An approved installation can send selected game or app log lines only after you review the editable preview and press Send.
  • Private read replay bundles. Supported uncertain or rejected reads can keep a local replay: reader evidence, board changes and solver/advice state, and may include the full analyzed game-client image only from a verified game-window capture. Window borders are cropped; the HUD can remain. Desktop fallback and unverified captures keep state only. Private replay sharing is on by default on new installations. When both local retention and diagnostics are on, the beta.51 update turns replay sharing on once, including PCs where it was off. If either control is off, replay sharing stays off until you choose to enable it. You can turn it off again in Diagnostics (main menu), and that choice is saved. Sharing requires both local replay retention and Send diagnostics and feature counts. Only new captures made while all three switches are on enter the upload queue. Previously saved bundles stay on your PC. Game images may show character names or chat. New bundles expire locally after 14 days: at most 30 bundles of 36 MB each, up to 300 MiB of payload plus file overhead, in addition to the separate failure-frame cache. Uploaded replay access expires after 14 days; scheduled cleanup removes expired copies and retries after failures. Legacy manual frame uploads keep their 90-day policy.
  • New game-log lines, off by default. A separate switch in Settings → Community, working only while run sharing is on. It sends the kinds of log lines the app can’t read yet, never a whole line, your character name or anything you typed.
  • Usage statistics, off by default. A separate switch in Settings → General sends app starts and page opens to Google Analytics, with the app version, UI language and a separate random id.

Settings → Community → Delete my data deletes data shared with the community service under this install id. Google Analytics, accounts and sync have separate controls. Exact fields, retention and controls: Safety & privacy and the privacy policy.

Why Windows or your antivirus may warn

  • The .exe isn’t code-signed yet (signing is planned), and each new version is a file almost nobody has downloaded yet. Windows SmartScreen shows “Windows protected your PC” for exactly that, and antivirus tools sometimes flag such a file as a precaution. That is a false positive, and common for new Windows apps.
  • What the app does can look odd to a security tool. It captures the game window’s picture, listens for global hotkeys, draws transparent windows over the game, and starts a small hidden PowerShell helper to ask Windows where the game window is (and to swap in a new version when you update). That is what the sections above describe, and nothing more.
  • If your antivirus quarantines it, you can restore the file, add an exception and report the false positive to the vendor (Microsoft Defender has a file submission form). The SmartScreen steps are on the Download page and in the FAQ.

How to check your download

  1. Get the .exe only from the official GitHub releases page or from the Download page, which links to it.
  2. Every release’s notes end with the SHA-256 of its .exe.
  3. Work out the SHA-256 of your file (the Download page shows the one PowerShell line for it) and compare. If the two are the same, you have exactly the file that was published.

The app makes the same check itself before it installs an update, and refuses a file whose SHA-256 doesn’t match.