Building stylized vegetation usually means jumping between the engine and a sprite editor, managing exported sheets, and accepting that every variation becomes another asset. For Feather Engine, I wanted a tighter loop: choose a visual language, shape the tree, and plant it without leaving the editor.
Nine leaf languages, five growth habits
Pixel Art Trees offers nine procedural leaf styles—broad, star, fine, blossom, jungle, ribbon, needle, pod, and quill—alongside five growth habits: young, spread, candelabra, leaning, and ancient. That gives 45 base combinations before changing the palette, seed, scale, or density.
Painted by code, still real 3D
The plugin generates a deterministic 32×32 leaf atlas from code instead of importing bitmap sprites. The live preview uses the same Feather tree renderer that the project will use, so creators are not approving a disconnected thumbnail. The result stays a compact recipe that can be regenerated reliably.
A short editor loop
Install Pixel Art Trees from Feather’s Asset Store, open it from View → Extensions, select a leaf style and growth habit, then adjust the seed and palette while the tree updates. A creator can plant one tree or place a terrain-snapped grove in a click, then continue fine-tuning with the main Tree Builder.
Built for projects, not screenshots
The generated trees use linked tree assets and a shared nearest-filtered atlas. They support wind, chopping, lower-detail rendering, and export. Because the recipe is deterministic and stored as normal project data, it also behaves naturally in Feather’s live collaboration workflow.
Why a plugin?
Keeping this feature in an enableable plugin lets the core editor stay focused while giving environment artists a purpose-built studio. The vegetation logic began in my RPG Mania project; bringing it into Feather turns that game-specific work into a reusable tool for more creators.
Pixel Art Trees is now available in Feather Engine. Grow the world, and keep every tree editable.
https://feather-engine.com/#pixel-trees
