Patch notes, manifestos and the class build-guide subforums, straight from GGG


  • Path of Exile Forums screenshot

Overview

The official forums: patch notes, development manifestos, per-class build guide subforums, bug reports and the sequel's early access boards.

  • forum
  • patch-notes
  • build-guides

You might also want

  • Community-maintained Wiki reference for classes, ascendancies, skills, items, mechanics and patch history, run by the same team as the original game's wiki.

  • Community-run Discord server with build help, campaign, endgame, news and looking-for-group channels for both games.

  • Community-maintained Wiki reference for items, skills, mechanics, leagues and version history, hosted by Grinding Gear Games since the move off Fandom.

Every tool listed here is made by the community, not by Grinding Gear Games. This site is not affiliated with or endorsed by GGG. Path of Exile is a trademark of Grinding Gear Games.

Submit a tool

The catalogue keeps each tool and its images in one directory. Add a tool by creating tools/<tool-id>/about.yaml.

  1. 1 Fork the repository, or use the edit link below and GitHub will fork it for you.
  2. 2 Run bun run new-tool for an interactive scaffold, or create the directory and about.yaml manually:
name: Your Tool
description: One factual sentence, 10 to 300 characters.
url: https://example.com
games: [poe1, poe2]
category: overlays-and-companions
tags: [overlay, price-check]
platforms: [windows, linux]
pricing: free
openSource: true
source: https://github.com/you/your-tool
status: active
lastVerified: 2026-09-15

url is the primary website or repository link. category must be one of: build-planning, trade, crafting, atlas-and-maps, regex-and-search, loot-filters, overlays-and-companions, economy-and-data, leveling-and-guides, community, league-specific. platforms: windows, linux, web, macos, android, ios. pricing: free, freemium, paid. openSource is required, and a source link is only valid when it is true. alsoIn lists extra categories; rank orders a tool within one section, keyed by section id.

  1. 3 Run bun run validate to check the entry parses.
  2. 4 Open a pull request. Listings are checked before merge.