Feature suggestion: Export to GGG's .build (in-game Build Planner) format

[chesler410]

Hi PoB team, thanks for keeping the PoE2 fork active. Wanted to float something that came up while I was building adjacent tooling.

GGG ships a new .build file format consumed by PoE2's in-game Build Planner. The format is documented in their Developer Docs → Build Planner section (https://www.pathofexile.com/developer/docs/game). Currently PoB doesn't export to it, so users who want their PoB-designed build to surface in-game have to round-trip through external tooling.

Why it might be worth considering

Native export from PoB would make the workflow seamless: design in PoB → click Export → drop file in Documents\My Games\Path of Exile 2\BuildPlanner\ → load in-game

Prior work (not asking you to use it, just noting it exists)

I built a third-party converter: https://github.com/chesler410/poe2-build-forge (live at https://chesler410.github.io/poe2-build-forge/). It takes a PoB XML export and outputs a schema-validated .build file.

The non-trivial part is mapping PoB's integer tree node IDs to GGG's PassiveSkills.id strings — I use repoe-fork/poe2's Default.json (https://github.com/repoe-fork/poe2/blob/master/data/passive_skill_trees/Default.json) for that lookup. PoB has its own GGPK-extracted data that would serve the same purpose internally. The schema itself is captured at packages/schema/src/poe2-build.schema.json (https://github.com/chesler410/poe2-build-forge/blob/main/packages/schema/src/poe2-build.schema.json) if useful as a reference.

Asking

1. Is .build export on the roadmap already in any form? Don't want to duplicate effort.
2. If it'd be welcome as a community contribution, happy to describe the mapping algorithm in more detail and/or help test against PoB's existing data. (My code is TypeScript; PoB is Lua so a direct port doesn't make sense — but the algorithm is the small part.)

Either way, no pressure. Feel free to close out if it's out of scope.

Thanks!