Build a RuneLite Goal Planner import code from a structured goal spec — either ONE section (goals[], GPSHARE1 wire, imports on every plugin build) or MULTIPLE sections at once (sections[], GPSHARE2 wire, including default-plan targeting with reuse-dedup). By DEFAULT (no confirm) it returns a rendering of the goal list as it will appear — section header, each goal with its type/target, prerequisites nested as a guide tree, and per-goal tracking badges — plus warnings, and NO code. Show that to the user so they can adjust the goals; re-run for an updated preview. Only once they confirm it matches their intent, call again with the same goals and confirm:true to receive the paste-ready code. Supports simple goals and complex prerequisite trees (wire via id + requires/orRequires). CRAFTING CONVENTIONS: (1) Keep sections FLAT — never invent parent/summary CUSTOM goals (e.g. an "X log complete" goal requiring the items) unless the user explicitly asks for that structure; a list of items is just the item goals. (2) Prefer typed goals over CUSTOM with a narrative name — account-shaped goals ("maintain quest cape", "reach elite combat achievements", "2100 total level") should be type ACCOUNT with the PHRASE as name: the resolver implies the metric AND milestone, and the goal displays the canonical metric name. Only pass an explicit accountMetric constant when you need a custom display name — usually you don't.

Decode a GPSHARE1:/GPSHARE2: code back into a readable breakdown (sections, goals, identifiers, descriptions/tooltips, prerequisite tree, cross-section dependencies) for verification. Tolerates surrounding text — paste the whole message containing the code.

Report which goal kinds the crafter auto-tracks (typed core) vs. emits as CUSTOM, plus the recognized skill names. Use this to decide whether a requested goal will track on the recipient's account.