Guide
Overlay & safety
The mini window and the rings over the game: what they are drawn from, how the game window is captured, and what the app never touches.
Also called: TLI overlay
TLI overlay, mini window, screen reading, is it safe, log file, UE_game.log
Last checked against SS14 Tartarus · 8 min read · updated
On this page
The short answer
TLI Toolkit’s “overlay” is two things drawn in the app’s own transparent windows on top of the game: a small mini window with the move to make and your FE per hour, and rings that mark the best move on the game screen. The app learns what is going on from the log file the game writes, and for Vorax and Tartarus it can also look at the game window’s picture, the way a streaming program does. It never reads or changes the game’s memory, never injects anything and never clicks or types for you.
From the first read to the first move
Set up one tool at a time. The useful test is whether the app describes the board currently in front of you, not whether a highlight appeared.
Visible game → Read now → compare fields → correct if needed → decide → read changed state
Suppose the game shows 3 Activity and 4 Quantity, but the reader shows 4 Activity and 3 Quantity. Both give 12, so the total cannot confirm the read. Correct both fields or re-read the offer before following the highlighted card. If the numbers and the offer match but the ring is offset, adjust the highlight instead.
- Prepare the source.Keep the game open in windowed or borderless mode, not minimised. Enable Log in the game for the events the tracker and advisors follow. In the Toolkit, check Settings → Highlights → Game window if the window was not found.
- Open a real choice.For example, leave a Vorax potion offer visible and move the pointer off the cards and numbers. On that tool’s page, use Read now or Ctrl+Alt+R. Auto-read has a separate setting for each supported tool; check that setting instead of assuming one switch covers all of them.
- Compare before accepting.Check the phase, every offered card and the board fields against the game. In Vorax, check Activity and Quantity separately as well as their product. An unsure field is a request for your check; a confident field is still worth comparing when something looks wrong.
- Make the game action yourself.Use a suggestion only after the input matches. After choosing a card, check the changed board and phase before following the next suggestion. The old target is not a command for the new screen.
If you cannot obtain a matching read, use the tool’s manual fields where available or continue in the game without its advice. You do not have to upload a picture to use screen reading. Local picture retention and online diagnostics have separate controls, described below.
What you see, and how the app knows
| On screen | What it is | Where the information comes from |
|---|---|---|
| Mini window | A small always-on-top window: FE per hour, the advisor’s best move | The game log; for Vorax and Tartarus also the window’s picture |
| Rings on the game | A highlight on the card, cell or button the advisor picks | The same read, placed as a fraction of the game window |
| Price check | A small window with an item’s price | The price feed and your own searches |
| Advisor boards | Vorax tanks and cards, the Tartarus ring | The log; screen reading fills what the log doesn’t say; you type the rest |
What the app reads
- The game’s log file (
UE_game.log), which the game writes once you press Enable Log in the game’s settings. Maps entered, items picked up, minigames opening and the Trade House’s lines all come from it. It is a plain text file the game writes on purpose. - Where the game window is: its position and size, asked from Windows, so the rings line up.
- 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; Read now (Ctrl+Alt+R) also starts a read.
How the picture is taken, in detail, since it is the part players ask about:
- The app first requests the game window’s stream. If it cannot open, the app automatically captures the monitor holding the game and crops each frame on your PC to the game area. Other desktop pixels can enter that monitor stream before cropping. There is no second confirmation for this fallback.
- A source request is armed for about 8 seconds; an opened stream normally stops about 20 seconds after the last read, sooner when the minigame closes. It also stops when the app quits or the PC sleeps or locks.
- Frames are taken until two in a row look alike, so nothing is read mid-animation, and only the settled frame is read.
- Text recognition runs on your PC with the bundled offline engine. 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.
- Settings lets you hide the mini window, price check and highlights from screen captures. With that setting on, OBS display capture leaves them out. Use the OBS browser source in Settings to put statistics on a stream; screen reading works with either capture-exclusion setting.
What it never does
- It does not read or change the game’s memory.
- It does not inject anything into the game or hook into it, and it does not change game files.
- It does not click, type or move for you: no macros, no automation. The only keys it listens for are its own hotkeys.
Everything the advisors suggest is a suggestion on your screen. Every move in the game is yours.
What goes online
Screen reading works offline. The app downloads prices, release information and a status file. Run and price sharing, the daily check-in, minigame sharing and diagnostics are on by default, with separate switches. Run and price uploads and the check-in wait for the community notice to close or remain visible for a minute; diagnostics has its own notice and schedule. New log-line types and Google Analytics usage statistics are off by default. Details and controls: Safety & privacy and in the privacy policy.
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.
Limits worth knowing
- Screen reading needs windowed or borderless mode; a minimised game cannot be read. Offline models are bundled for English, Simplified and Traditional Chinese, Korean and Russian. Chinese and Korean recognition accuracy is still being checked.
- When the reader isn’t sure of a value, it shows its guess with a button to use it instead of filling it in.
- If a ring is a little off on your setup, nudge it in Settings → Highlights; it is placed by fractions of the game window, so resolution and UI scale don’t matter.
- The .exe is not code-signed yet, so Windows may warn of an unknown publisher. Check its SHA-256 as the Download page shows.
Diagnose the symptom you can see
- No game window or no read.
- Restore the game, check the selected window and the tool’s Auto-read setting, then try Read now with the choice visible. A successful capture still needs a usable, settled screen.
- The ring is misplaced.
- First check that the advice names the current card. If the advice is right but the ring is offset, check the game-window selection and the Highlights adjustment. Do not change correct board values to move a ring.
- The board is wrong or advice waits.
- Move the pointer away, let the animation finish and re-read. Compare any missing or unsure fields and the current phase. If it remains wrong, correct the data or stop using that suggestion.
- The mini window is absent from OBS.
- Check “Hide mini window and highlights from screen captures” in Settings. Use the OBS browser source in Settings for stream statistics rather than changing reader inputs.
Sources: TLI Toolkit’s capture and highlight settings, Read controls and screen-reading design notes, checked 15 November 2026.
Sources
Mechanics and reference
| Source | Used for |
|---|---|
| TLI Toolkit’s Safety & privacy page and privacy policy | What the app reads, never does and sends |
| The app’s screen-reading design notes (TLI Toolkit, 0.1.0-beta.42) | How and when the picture is captured, the 8 and 20 second windows, the hidden windows |
How TLI Toolkit helps

- The mini window and rings work for the Vorax and Tartarus advisors, with screen reading on or off.
- The Vorax and Tartarus guides explain the minigames the advisors play.
- The FE tracker guide explains the numbers the mini window shows.
Try it in the app
It’s part of TLI Toolkit, free for Windows 10 and 11.
FreeWindows 10/11, no installWhat’s new
TLI Toolkit is a Windows PC app: open tlitoolkit.com on your PC to download it. The guides and strategies work on any screen.
Written from the game’s own texts, patch notes and community research. Mechanics change between seasons; if something here is out of date, tell us on GitHub.
