# Lailloken/Exile-UI for Path of Exile 1 and 2

> Lailloken/Exile-UI is an AutoHotkey overlay for Path of Exile 1 and 2 that adds configurable interface projections, item summaries, campaign helpers, and stash price overlays. It is positioned as a personal toolkit rather than a complete game client replacement, and its unofficial status remains an important adoption concern.

**Lailloken/Exile-UI** — UI and QoL overlay for Path of Exile 1 and 2. Emphasizes ease of use, minimalist design, and seamless integration. Formerly Lailloken UI.

- Repository: https://github.com/Lailloken/Exile-UI
- Stars: 1,376 · Forks: 78
- Language: AutoHotkey
- License: MIT
- Published: 2026-10-16 · Updated: 2026-10-16 · Language: en
- Canonical page: https://hysenlabs.com/projects/lailloken-exile-ui

## What Exile-UI Adds to Path of Exile

Lailloken/Exile-UI is a lightweight AutoHotkey overlay for Path of Exile 1 and Path of Exile 2. Its target audience is players who want additional information and controls without replacing the game client. The project focuses on interface customization, item evaluation, campaign progress, and stash pricing, with an emphasis on few required hotkeys and integration into the existing client.

The project is not a full loot filter, build planner, or replacement for Path of Exile. Its scope is narrower and more experimental. The README describes it as a personal toolkit created by a self-taught hobby coder, and it explicitly says that not every feature is necessarily useful to every player. That framing matters when judging the project. A feature can be included because its author finds it interesting, so the project should be evaluated feature by feature rather than treated as a polished, uniform product suite.

The stated center of the author’s ideas is solo-oriented play, although the author is open to trade-league ideas when they are not too complex. The author also says that features perceived as overpowered or abusable are generally avoided. Those are project intentions, not guarantees about game behavior or competitive fairness.

## How the Overlay Reads and Sends Game Information

The README describes a mixed interaction model based on local files, screen inspection, keyboard input, and on-screen text. Exile-UI reads the game's `client.txt` log file for information such as the current character level, area transitions, and NPC dialogue. It does not claim to read or check game values or bars directly.

For interaction with the client, the tool sends key presses. These can copy item information, activate chat commands, or perform in-game searches. It also checks screen content for context sensitivity, including whether interfaces such as the inventory or stash are open. That approach means the overlay can adapt to visible game states without requiring a deep connection to the game client.

When a key is pressed, Exile-UI can read on-screen text, summarize it, and show the result in configurable tooltips. This design supports compact item information without replacing the original item panel. It also creates a clear dependency boundary: the project relies on the client log file, visible screen content, keyboard input, and text recognition, rather than on a documented API for internal game state.

## Clone-frames, Item-info, and Stash-Ninja

Clone-frames projects selected screen areas into separate interface elements. The README gives examples such as rage meters, cooldowns, and charges, with feature pages for both Path of Exile 1 and Path of Exile 2. This is useful when a player wants a particular visible element to appear in a different position or format, but it also depends on screen content and client layout. Resolution changes or interface changes can therefore affect whether a projected area remains correctly aligned.

Item-info provides a compact, customizable tooltip intended to help players judge loot quality at a glance. The README shows examples for rare and unique items in both games. Its usefulness depends on the text that the tool can obtain and summarize, so it should not be treated as a complete replacement for the game's item display. It is better understood as a focused evaluation layer over information already visible in the client.

Stash-Ninja adds a `poe.ninja` price overlay for fixed stash tabs. The documented capabilities include customizable price tags and profiles, conversions, and price history. This differs from a general market browser because it is tied to stash content and the overlay workflow. It is also the feature with an explicit external data dependency, since prices are presented through `poe.ninja`. The README does not describe what happens when that service is unavailable or when displayed prices are delayed.

## Campaign Tools and Path of Exile 2 Support

The Act-Tracker section lists campaign-related tools, including an automated guide, Path of Building tree overlays, gem-setup overlays, and a gem-cutting overlay for Path of Exile 2. Act-Decoder provides campaign layout indicators and full layouts. These features target different moments in campaign play: navigation, build preparation, gem configuration, and understanding of the current act layout.

The README shows both Path of Exile 1 and Path of Exile 2 entries, but the examples are not identical. For example, the gem-cutting overlay is listed only for Path of Exile 2 in the campaign examples. This is useful evidence that support is feature-specific rather than a claim that every module behaves identically across both games. The repository should be checked for the current version of the game and the particular feature that matters.

The project also lists Rune-Ninja, but the README section is cut off before its full description. It would be inappropriate to infer how that feature handles data, supported versions, or failure conditions from the name alone. The documented examples are enough to establish a campaign and stash toolkit, but not enough to validate every listed module.

## Installing Exile-UI and Starting a First Use

The README points to AutoHotkey, a setup guide, a repository archive, and the releases page. It does not provide a command-line installation procedure or a documented set of dependencies beyond the AutoHotkey reference. The repository root includes `Exile UI.ahk`, along with `data/`, `modules/`, and image directories, which indicates that the project is distributed as an AutoHotkey codebase rather than as a conventional package install.

A first use should begin with the setup guide linked from the README, because the README itself does not spell out every configuration step. The available download path is:

```text
https://github.com/Lailloken/Exile-UI/archive/refs/heads/main.zip
```

This downloads the default-branch archive. The README also links to the releases page, where versioned artifacts are available. No exact `curl`, installer, package-manager, or AutoHotkey invocation is documented in the README, so none is added here.

After obtaining the files, AutoHotkey is the documented prerequisite indicated by the setup table. The exact launch command, hotkey configuration, and first-run initialization sequence are not documented in the README, so they cannot be stated as confirmed instructions. The relevant files for reviewing the distribution are `Exile UI.ahk`, `LICENSE.md`, and the `modules/` directory.

## Limitations, Licensing, and Upgrade Cost

The most significant limitation is not a missing feature but the boundary of the integration method. Exile-UI reads `client.txt`, inspects visible screen content, sends key presses, and summarizes on-screen text. Changes to client log formats, screen layout, resolution, or interface behavior could make individual features less reliable. The README does not provide a compatibility matrix or explain how the project handles those changes.

The project is explicitly not affiliated with or endorsed by Grinding Gear Games. Its transparency notice says the author is unaware of GGG approving any local third-party tool and makes no claim that users cannot be banned. It links to GGG's developer policy and says the author follows it, but that is not equivalent to approval or a guarantee of compliance for every user configuration. This is the main reason to read the linked policy before deploying the overlay in a game account that matters to you.

The repository is licensed under MIT. That permits use and modification under the license's terms, including distribution and sublicensing subject to its conditions. The MIT terms do not grant rights from GGG, grant approval for third-party tools, or resolve game policy questions.

The repository is not archived, and its last push was on 2026-10-14. Recent releases include `v1.65.1` on 2026-10-08, `v1.65.0` on 2026-09-03, and `v1.64.3` on 2026-08-29. The release history shows recent project output, but upgrade cost remains feature-dependent because the README does not document migration procedures, compatibility guarantees, or a rollback process.

## Why Choose Exile-UI Instead of a Manual Workflow

A real alternative is to use the game's own interface plus manual clipboard operations and external planning tools. That approach has fewer third-party overlays and avoids reliance on screen projection, but it does not provide Exile-UI's compact item summaries, projected frames, automated campaign guide, or `poe.ninja` stash tags.

The difference is workflow placement. Exile-UI sits over the running client and reacts to local context. A manual workflow leaves more steps in the player-controlled process. In return, the manual approach exposes each action directly and does not depend on Exile-UI's log parsing, screen inspection, or keyboard automation.

Exile-UI is therefore best suited to players who repeatedly work with loot, stash organization, campaign progression, or compact in-game information. It is the wrong choice for a player who wants an official feature set, a server-side data interface, or a complete build-planning system. The README presents Stash-Ninja as a `poe.ninja` overlay, not as a general replacement for Path of Building, and the documented tools remain local AutoHotkey modules.

## Conclusion

Adopt Exile-UI if you play Path of Exile 1 or 2 and want narrowly scoped overlay and quality-of-life features with a low number of hotkeys. Do not adopt it as a game replacement, an official GGG product, or a source of guaranteed account safety. Verify first that the current release supports your game version, that AutoHotkey is available on your system, and that the documented behaviors fit the rules you are willing to follow.

## FAQ

### What is Lailloken/Exile-UI?

It is a lightweight AutoHotkey overlay with UI and quality-of-life features for Path of Exile 1 and Path of Exile 2. The project was formerly known as Lailloken UI.

### Does Exile-UI work with Path of Exile 2?

Yes. The README lists Path of Exile 2 support and provides feature examples for both games. Support differs by feature, as shown by the campaign examples where the gem-cutting overlay is listed for Path of Exile 2.

### Can using Exile-UI get a Path of Exile account banned?

The README says the author cannot make claims about whether a user will be banned. It states that the project is unofficial, is not affiliated with or endorsed by GGG, and follows the linked GGG developer guidelines, but approval or account safety is not guaranteed.

## Sources

- [Issues](https://github.com/Lailloken/Exile-UI/issues)
- [Lailloken/Exile-UI on GitHub](https://github.com/Lailloken/Exile-UI)
- [License: MIT](https://github.com/Lailloken/Exile-UI/blob/main/LICENSE)
- [README](https://github.com/Lailloken/Exile-UI/blob/main/README.md)
- [Releases](https://github.com/Lailloken/Exile-UI/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/lailloken-exile-ui