Start with a tiny PoE2 .build template.

Example template

{
  "game": "poe2",
  "format": "buildfileconverter.sample.v0",
  "class": "Mercenary",
  "skills": ["Explosive Shot"],
  "notes": "Sample only. Replace with your real build data."
}

What to edit

• Replace the class with your character class.
• Add your core skill names and notes.
• Keep the file parseable as JSON.
• Run the checker before importing.

Template safety

This sample is not a recommended character build. It is intentionally small so you can test the import workflow without confusing placeholder data for a real build guide.

What a real .build file may contain

A real planner file may include fields for game version, class, ascendancy, active skills, support gems, passive choices, items, notes, and tool-specific metadata. Different community planners can use different names and nesting structures. That means a tiny sample is useful for testing JSON parsing, but it is not proof that every planner will import the same file.

The safest starter template keeps fields obvious and human-readable. Start with `game`, `format`, `class`, `skills`, and `notes`, then add planner-specific fields only when you know the target schema. If you copy data from a guide, keep the guide URL in notes or source metadata so the build can be checked against the original context later.

How to use the template responsibly

• Use it to test whether your import folder and file handling work.
• Replace placeholder skills with real build data before sharing.
• Add a patch or league note when the source build depends on current balance.
• Run the checker after every manual edit.

If your final file still says `buildfileconverter.sample.v0`, it should not be treated as a finished build. Rename the format or add real planner metadata once you have a target schema.

From sample to real build notes

A practical template usually grows in layers. First, keep identity fields such as game, format, class, and source. Second, add the main skill setup and any notes that explain why the build works. Third, add planner-specific data only when you know the importer accepts it. This keeps the file readable for humans and reduces the chance that one invalid nested field breaks the whole import.

If you are adapting a build from pobb.in, poe.ninja, or a written guide, add the original URL before you add detailed fields. Source attribution is not just courtesy; it is a debugging tool. When a later patch changes a skill or item, the source URL helps you decide whether the file should be updated, archived, or deleted.

Validation checklist for templates

• The file parses as JSON.
• The top-level object includes enough context to identify the build.
• The notes say whether this is a sample, source capture, or finished planner file.
• The source or patch context is preserved.

FAQ