Palette Load

Overview

Loads a palette file (GPL/ASE/JASC PAL/HEX text) into the graph. Palette assets created or distributed for Aseprite, GIMP, Lospec, and similar tools can be used directly as a PixPipeline color scheme.

Usage tips

• The file dialog starts in user_data/palettes/. Keep your palette collection there for quick selection.
• A web palette from Lospec or a similar site can be loaded by saving HEX text with one #RRGGBB color per line as .txt.
• With "Copy external reference files into project" ON, the palette is copied to the project's assets/palettes/ directory, keeping the reference with the project when it moves between environments.
• To promote a loaded scheme into a project-managed palette, register it in the Shared Palette panel or indexed colors after loading.

Common pitfalls

• Order does not suit the use: output preserves file order. Reorder it with palette_edit to make a dark → light ramp for gradient_map.
• Loading fails: check the supported format and extension. Non-empty malformed color rows are reported with their line number, and JASC PAL requires its version and declared color count to match.

Supported formats

• GPL
• ASE
• PAL (JASC)
• TXT / HEX

TXT / HEX expects one #RRGGBB or #RRGGBBAA value per line.

Usage

• Use it to bring an external palette file into the graph.
• PaletteCreate is for manual creation/editing; PaletteLoad is only for file loading.
• The palette import/export UI in PixelCanvas uses the same parser / writer foundation.

Notes

• An empty path returns an empty palette.
• A loading failure is reported as a node error.

Related nodes

• palette_save — the reverse operation, writing a palette file
• palette_create — build a palette manually instead of loading a file
• palette_extract — collect colors from an image
• common_palette_ref — reference a project-wide palette