TLI ToolkitTorchlight: Infinite companionDownload

Trust

Safety & privacy

TLI Toolkit runs on your PC and works mainly from the log file Torchlight: Infinite writes itself once you press Enable Log; two advisors can also read the game window’s picture. Your sessions, prices and settings stay on your computer. Little goes online, and only what’s listed below.

What it does and doesn't do

  • Reads the game log and game-area images when screen reading is used. Capture first uses the game window; if that fails, it automatically uses the game’s monitor and crops locally. Windows also supplies the game window’s position and size.
  • Never reads or changes game memory, never injects anything, and never sends keys or clicks to the game. The only keys it listens for are its own hotkeys.
  • Draws its rings and mini windows in its own transparent windows on top of the game.
  • Works offline. Everything it sends is listed below and in the privacy policy. Run and price sharing, minigame sharing and diagnostics are on by default, with separate switches. Run and price uploads and the daily check-in wait until the community notice is closed or has been visible for a minute. Diagnostics has its own notice and runs independently (Diagnostics (main menu)).
  • Windows only, portable, no installer. The .exe is not code-signed yet, so Windows may warn about an unknown publisher: check its SHA-256 as the Download page shows, and use the VirusTotal scan link in each release’s notes.

What the app reads

  • The game’s own log file (UE_game.log), which the game writes once you press Enable Log. Everything the tracker and the log-aware advisors know comes from there: maps entered, items picked up, exchange prices you looked up, minigames opening.
  • Where that file is. To find it, the app looks in your Steam library folders, the standalone launcher’s and TapTap’s install folders, and the folder of the running game.
  • Where the game window is (its position and size), so the mini window and the on-game rings that mark the best move line up with the game.
  • 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.
  • Boards you type in, wherever screen reading and the log don’t cover them (Arcana’s cells, the Void Sea’s flames and cards, or anything screen reading isn’t sure of).

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 click, type or move for you: no macros, no automation. Every move in the game is yours.

The app reads a text file the game writes on purpose, looks at the game window’s picture the way a streaming program does, and draws its own windows on top. It doesn’t read or change game memory, inject anything or send clicks or keys to the game, so there is nothing on the app’s side that touches the game client. It is an unofficial tool, though, so use it at your own risk.

What goes online

  • The price feed. The app gets public item prices from api.tlitoolkit.com. You can turn off the feed in Settings. If an item icon is missing locally, the app may download it from a saved image address, including one on tlicompanion.com.
  • The update check. The app asks GitHub’s public API which versions of SheF1k/tli-toolkit-releases exist. It downloads a new version only when you click Update, and installs it only if its SHA-256 matches.
  • The patch status. When it starts and every 6 hours the app downloads tlitoolkit.com/status.json, the public list behind the status page of which parts of the app work with the game as it is now. It’s a plain download of that file: no id, nothing about you or your play. Offline, the app keeps the last copy.
  • Run sharing, on by default. With Settings → Community → Share my runs on, finished maps are sent anonymously for the farming-strategy tables (details below). It is on unless you turn it off: the first time the app starts, a notice says so with See what’s sent and Turn off right there, and no community upload is sent until that notice has been on screen for a minute or you close it. Turning it off later in Settings → Community stops it at once. While it is on, the app also checks in once a day: it tells the server that a copy is running, with the same random id, the app version and the UI language, and nothing else. Maps you finished before are sent only if you ask for it (Also share my earlier maps): this season’s and the last one’s, the same way, once each and over a few days. Opening the Community page downloads the published tables, just like this website does.
  • Minigame run sharing, on by default. A separate switch (Settings → Community → Share minigame runs to improve the advisors), on for new installs and off with one click: finished Vorax and Tartarus runs, never practice runs, are sent with the same random id so the advisors can be checked against real games. Each run is the boards the advisor saw (game ids and numbers), its advice and your moves, and how the run ended; never names, screenshots or the time to more than the hour.
  • New game-log lines, only if you turn it on. A separate switch (Settings → Community → Record new game-log lines), off by default and working only while Share my runs is on. At most every 6 hours it sends the kinds of game-log lines the app cannot read yet, each kind once, with the same random id: the line’s leading code name (digits replaced by #), the names of its fields and up to two shapes with every value replaced by ?. Never a whole line, your character name, ids or anything you typed. See exactly what’s sent shows the next upload, and Delete my data removes the counter kept under your id.

Optional analytics, sync and account services have their own controls in the privacy policy. A bug report (Ctrl+Alt+B) is a zip saved on your PC, with character names, account ids and IP addresses taken out of the log lines in it; you decide whether to attach it to a GitHub issue. Settings shows the last lines of the app’s error log that a bug report includes. Screen reading needs no internet: its text-reading engine and supported language models ship with the app. The OBS browser source, if you turn it on, is served only to your own PC.

Download only from the official page

The one official source is the GitHub releases page. Each release lists the SHA-256 of its .exe, and the Download page shows how to check yours in PowerShell in a few seconds. TLI Toolkit is closed source; the releases repository hosts the downloads, release notes and bug reports.

Community tables: how run sharing works

The farming-strategy tables come from real maps played by TLI Toolkit users who share them. Until enough runs are in, the tables say they are still collecting data rather than show any numbers.

Where the numbers come from

  1. The desktop app reads the game’s own log file to track each map: what was spent opening it and what was picked up.
  2. While a player’s sharing is on, each map they finish is sent in small anonymous batches (or kept for later when offline). If they ask for it, the maps they finished earlier this season and last season follow over a few days.
  3. The server checks every upload, drops duplicates, limits how much one install can add, and stores the maps as they came.
  4. A few times a day everything is recalculated: each map is valued with that day’s reference prices, and setups are compared by their median profit per map, the spread and how many players play them.

What is sent

  • The hour a map started (not the minute), its zone, Timemark tier, and how long it took.
  • The items spent and dropped, as item ids and counts. For a map, the Netherrealm Resonance spent opening it and on rerolls, as separate numbers (the sum was already in the items spent).
  • The Pactspirits and Void Chart constellations the app knows about (ids from the game’s log, or what the player picked), and the player’s hero and its trait (game ids).
  • The app version, the season, an optional game-server region, and a random id made by the app that the player can reset.
  • For a map, the Vorax and Tartarus entry tokens it earned, so the minigames they pay for are credited back to it, and its boss fight: the seconds to the fight and to the kill.
  • For a map, the Cube Greeds the game log showed during it (won and lost); for a Tartarus run, with Share minigame runs on too, how many Warden’s Caches of each rarity its Riot opened. Both for the measured odds on the Odds Lab.
  • With Share minigame runs on, the TOWER Sequence rounds the calculator read: the R&D type, the hour and the chips each round offered.
  • Once a day while sharing is on, a check-in that a copy of the app is running: that same random id, the app version and the UI language.
  • Once a day at most, unless you turn it off (Diagnostics (main menu)): what failed in the app, as kinds of failures, item ids, counts, the app version, the game and the screen’s size, with the same random id. No paths, names, item names or pictures; a frame from the separate failure-frame cache only if you press Send this frame.
  • 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.
  • With the same switch, how many times each page or tool of the app was opened (a fixed list of short names such as “page.arcana” or “calc.cube”), and how many times Vorax or Tartarus showed advice. Only counts, added up per day on the server with no install id.
  • While sharing is on, your Trade House price searches: the item, the prices listed (the 40 cheapest), the season and when, with the same random id and the app version, in batches every few minutes. They make TLI Toolkit’s own item prices: each player’s latest search of an item counts once, joke listings and prices far from everyone else’s are left out, and each price says how many players it comes from. A price is public market data, so it is shown even when it comes from one player.
  • For earlier maps a player asked to share: the same, plus the price the app had saved for each of their items (used only for days before the reference prices began, and only within a limit).
  • With Share minigame runs on (a separate switch): each finished Vorax and Tartarus run’s boards as the advisor saw them, its three best moves and the move made, how the run ended, the hour it started, and the app version, language, advisor settings and game window size. The same switch also sends, once a day at most, the small grids of numbers the Vorax screen reader learned for card names and instrument pictures (never a picture of the screen), so it recognises more cards for everyone.

What community run sharing leaves out

  • Community run uploads and daily diagnostic summaries do not include character/account names or player/account ids as fields. A shared game image can show character names or chat.
  • IP addresses: used only, salted and hashed, to slow down floods; never stored.
  • The labels players write for their own strategies.

The server keeps a keyed hash of the random id, not the id. Raw maps are kept for two seasons; the published tables only hold totals.

Delete my data

In the app: Settings → Community → Delete my data. Every map sent with that install’s id is left out of the next tables (within a day) and removed from storage at the next clean-up, and so are its daily check-ins, and so are its Trade House searches (the prices made from them no longer count them from the next hour); its minigame runs are deleted at once; its diagnostics and frames are deleted at once; the app then makes a new id.

Fair numbers

  • Medians, not averages: one lucky drop doesn’t move them.
  • Gameplay statistics use minimum sample sizes only: season strategy rows and choices need 2 installations and 10 maps; period rows need 2 installations and 15 maps, or 3 installations and 10 maps; equipment shares and mixes need 2 installations and 5 maps; hero rankings need 2 installations and 20 maps, or 3 installations and 10 maps. Ordinary season totals keep their 2-installation/10-map floor. Other tables retain their own contributor and statistical quality minimums. No gameplay result is published from one installation alone, including explicitly published setups. Names, installation IDs and fingerprints are not public. Small groups may estimate each other’s results by comparing tables or releases. Sharing controls, opt-out, withdrawal, deletion and retention are unchanged; historical coverage can have gaps.
  • No install counts for more than its latest 300 maps of a setup.
  • Map cost is subtracted; “after tax” values drops after the 12.5% Trade House tax.

Contact

Write to hello@tlitoolkit.com, or ask in public on GitHub issues (bugs, questions and ideas), or use the Request a feature page. The details of what is kept and for how long are in the privacy policy; the terms of use are short.

Credits. Historical prices from tlicompanion.com and community prices from TITrack (read once an hour by our server, with its author’s agreement); Pactspirit and Void Chart names from tlidb.com; zone and item names from open-source TLI trackers. The open-source work the app builds on, and its licences, are on Credits & licences.