Is there a free trial?

Yes. Start a free 3-day trial from your account at codefizz.dev/account, no credit card required. The trial unlocks the full Pro plugin for UE 5.6, 5.7 and 5.8 on one machine. When it ends, upgrade to a paid plan and the same key keeps working with five machine seats. There is also a separate free, open-source community edition (Unreal MCP).

Which Unreal Engine versions are supported?

UE 5.6, 5.7 and 5.8 on Win64. Each release ships as a separate binary plugin matched to the engine ABI, and the cfa CLI downloads the build that matches the engine you point it at. Future engine versions are added as they release.

Which platforms are supported?

Right now, Windows 64-bit only. The plugin is built and tested on Windows for this first release. Linux and Mac support are on the roadmap and will be added when there is clear demand from paying customers. I would rather wait until I can properly test those builds end to end than ship binaries I have not run myself. If you are on Mac or Linux and would buy the plugin today, drop a note in Discord or send me an email. That is how the priority for adding those platforms gets set.

Do I need a license key, and how do I enter it?

Activate from the CLI with your CodeFizz website account. Install or update the free cfa CLI, run cfa login, and sign in in the browser. That machine is activated and the editor plugin reads the same sign in, with nothing to paste inside Unreal. Offline grace still applies. A license key remains under License and billing for recovery and older cfa builds (cfa login --key), but new setups should use browser login only.

What MCP clients work with the plugin?

Any MCP-compatible client. The plugin exposes a TCP bridge and the Go CLI ships separately, so Claude Code, Cursor, VS Code, Gemini, and other MCP hosts all work out of the box.

Can I cancel anytime?

Yes. Open your account at codefizz.dev/account and click Manage billing to open the Polar billing portal, then cancel in one click. You keep access through the end of your billing period and stop being charged afterward.

What happens to my installed plugin if I cancel?

You keep the version you installed and it keeps working. Your license stays valid after you cancel, so the plugin does not switch off. You stop receiving new releases and you lose access to the private Discord and roadmap. The plugin you paid for is yours to keep.

Do you offer refunds?

No refunds on subscriptions, since the plugin is downloadable software you get immediately. You can cancel any time and keep access through the end of the period you have already paid for. Lifetime Pro is a one-time purchase with nothing to cancel: it is fully refundable within fourteen days if you have not downloaded the plugin yet, and a refund ends the licence. If you ran into a real bug or a feature you reasonably expected to be there, email me and we will figure it out. Full policy on the Refund Policy page in the footer.

Why is Patron more expensive when I get the same plugin?

Patron is for people who want to influence the direction of CodeFizz Editor Agent, with voting, a private roadmap, priority answers, and direct input on new APIs. If you just need the plugin and updates, stay on Pro.

Is there a free version?

Yes. There is a free, open-source community edition (Unreal MCP) that gives you the core bridge and a basic command set, which is great for trying the workflow. The paid Pro edition is the fully maintained build with the complete toolset (Niagara, PCG, StateTree, Insights, and more), regular updates, and support. The open-source edition is linked in the footer.

Studio / team licensing?

For studios needing multiple seats, an enterprise tier is available off-platform. Contact directly for pricing.

Is there a lifetime or one-time payment option?

Yes. Lifetime Pro is a one-time payment of $399 USD (list price $499) that gives you the full CodeFizz Editor Agent plugin and every future update permanently, with no subscription and nothing to renew or cancel. It covers UE 5.6, 5.7 and 5.8 plus engine versions added later, five machine seats, and Pro Discord access. Prices are localized, so you are charged in your own currency at checkout.

What does Lifetime Pro include?

Lifetime Pro is the complete Pro plugin for every supported Unreal Engine version, yours permanently. That means all 900+ commands across Blueprints, Materials, Niagara, PCG, StateTree, Control Rig, Mutable, audio and Insights profiling, every future update and every new command at no extra cost, five activated machines, and Pro Discord channel access. There is no renewal date, no expiry, and no second invoice. You pay once and it keeps working, including on Unreal Engine versions that do not exist yet.

Grow a Tree with AI

A guided example: build a Procedural Vegetation graph from empty, grow a trunk that branches and droops, skin it into a mesh, scatter foliage, and export the plant to mesh assets.

This walkthrough grows a tree from an empty asset: a trunk that branches and bends under its own weight, a mesh skinned onto it, foliage scattered over the result, and an export to real mesh assets with no click. Every command here needs Unreal Engine 5.8 or later. They are all listed in the Procedural Vegetation reference.

A vegetation asset is a PCG graph

This is the thing worth knowing first. A Procedural Vegetation asset derives from the same graph type PCG uses, and every vegetation node from the same settings type, so the whole PCG command set works on one. You add nodes, wire pins, set properties, lay the graph out and batch edits exactly as you would anywhere else. There is no separate add node command for vegetation, and none is needed.

Read a node before you touch it

These nodes are large. The Grower alone carries 179 properties, many of them gated behind a condition that decides whether they do anything at all. Discovery is not optional here, it is how you avoid setting things that quietly have no effect.

Search the menu the editor renders

Node titles and categories come from the plugin's own add node menu, so they are always what your engine really has. Several searches in one call.

bash

cfa search_pv_nodes --filters "grower,mesh,foliage" --max-results 5

Read one node's schema

Every property path with its type, default, Unreal's own description, the valid values of every enum, the slider and clamp ranges, and the edit condition. Narrow by category, because the full set will not fit in one answer.

bash

cfa describe_pv_nodes --node PVGrowerSettings --category Growth

Or write the whole thing to a file

Every node and every property, written to disk so it never floods the conversation. Read the file instead of asking again.

bash

cfa export_pv_schema --name FullSchema

Build the pipeline

The chain runs Grower, then any post growth modifiers, then Mesh Builder, Bone Reduction, and Foliage Distributor. The Mesh Builder wants a cross section on its Profile pin, and the Distributor wants a palette on its Foliage pin.

Create an empty asset

Without a sample you get just Input and Output. Prefer empty while learning, because a duplicated sample hides over a hundred authored values you did not choose.

bash

cfa create_procedural_vegetation --asset-path /Game/Veg/PV_Oak

Add the nodes

Ordinary PCG node adds. Read the stable names back rather than predicting them, because they follow the node title and not the class.

bash

cfa add_pcg_node --graph-path /Game/Veg/PV_Oak --settings-class /Script/ProceduralVegetation.PVGrowerSettings
cfa add_pcg_node --graph-path /Game/Veg/PV_Oak --settings-class /Script/ProceduralVegetation.PVMeshBuilderSettings
cfa read_pcg_graph --graph-path /Game/Veg/PV_Oak

Wire it

Pin labels matter. The Mesh Builder's inputs include Profile, BranchRadius, MeshDetails and MaterialDetails, and one of them is spelled with spaces.

bash

cfa connect_pcg_pins --graph-path /Game/Veg/PV_Oak \
  --from-node-name ProceduralVegetationGrower_0 --from-pin-label Out \
  --to-node-name ProceduralVegetationMesher_0 --to-pin-label In

Give the trunk a shape

The Plant Profile Loader takes its shape from a data asset, and its output pin is named after the profile you author. The points are a cross section measured around the branch, not a taper running up the trunk, so they have to close back on themselves.

Author the profile in a data asset

Roughly a hundred samples around the ring. A constant radius is a circle, and gentle variation reads as bark.

bash

cfa create_data_asset --asset-path /Game/Veg/PPD_Oak \
  --class-name ProceduralVegetationPlantProfileDataAsset

cfa set_asset_property --asset-path /Game/Veg/PPD_Oak --property-name Profiles \
  --property-value '((Name="Trunk",Points=(1.0,1.02,0.99,...)))'

Point the loader at it, then wire the named pin

The output pin appears once the asset is assigned, and carries the name you gave the profile.

bash

cfa set_pcg_node_property_path --graph-path /Game/Veg/PV_Oak \
  --node-name ProceduralVegetationPlantProfileLoader_0 \
  --property-path PlantProfileData --property-value '"/Game/Veg/PPD_Oak.PPD_Oak"'

The loader's own Profiles array is a mirror, not an input

The node shows a Profiles array, but the pins are built from the data asset it points at, not from that array. Writing to the node directly succeeds and produces no pin. Author the profile in the data asset and assign it.

Grow it

The simulation runs in cycles. One cycle grows one segment, so the number of cycles is the budget the whole plant is built from, and the trunk spends it first.

Set the cycle count first

This is the master switch and its default is the minimum. Everything else you tune is judged against it.

bash

cfa set_pcg_node_property_path --graph-path /Game/Veg/PV_Oak \
  --node-name ProceduralVegetationGrower_0 \
  --property-path GrowerParams.GrowthCycles --property-value 45

Shape it

Height, spread, thickness and branch depth. Set several in one batch so they land as a single undo step.

bash

cfa set_pcg_node_property_path --graph-path /Game/Veg/PV_Oak --node-name ProceduralVegetationGrower_0 \
  --property-path GrowerParams.TrunkGrowth.PlantTargetLength --property-value 11.0

Clear the lower trunk

Root zone auxin suppresses sprouting near the base, and apical dominance keeps a single leader. Together they give a clean trunk with the crown above it.

bash

cfa set_pcg_node_property_path --graph-path /Game/Veg/PV_Oak --node-name ProceduralVegetationGrower_0 \
  --property-path GrowerParams.Auxin.RadicalAuxin --property-value 0.3

GrowthCycles defaults to 1, and 1 grows a bare spike

At the default you get a single stem with no branching at all, no matter what else you set. Its usable maximum is 45, which is what Epic's own shipped trees use. Raising it from 1 to 45 on a test tree took it from one branch to over three thousand. If a tree looks like a stick, check this before anything else.

Segment length trades height against branching

One segment per cycle means a short segment length spends the whole budget climbing and leaves nothing for branches. Longer segments finish the trunk sooner and leave cycles for the crown. Raising MaxGeneration or branch length will not help once the cycles are gone.

Look at it without regrowing it

Selecting a node is what drives the viewport, so you can inspect any stage by asking for that node. It reads what is already there rather than running the graph again, which is the difference between a wait of over a minute and about half a second. The graph regenerates by itself whenever you change a property, so you never need to ask for that.

Preview a stage

The Grower for the branch skeleton, Bone Reduction for the bone colouring, the Foliage Distributor for the finished plant.

bash

cfa open_asset --asset-path /Game/Veg/PV_Oak
cfa preview_pv_node --graph-path /Game/Veg/PV_Oak --node-name ProceduralVegetationFoliageDistributor_0

Tidy the graph

Nodes added over the bridge all land at the origin on top of each other. Lay it out, then save, because layout is an unsaved edit.

bash

cfa layout_pcg_graph --graph-path /Game/Veg/PV_Oak
cfa save_asset --asset-path /Game/Veg/PV_Oak

Export it

Unreal offers no scripted way to export a plant, so this drives the editor's own Export command and answers its dialog for you. It works the same whether the editor is in front of you or running unattended.

Name the output, then export

The graph needs an Export node with a mesh name set. Export reads evaluated data, so on a graph that has not generated yet the first call starts generation and reports needs_generation. Call it again once that finishes.

bash

cfa set_pcg_node_property_path --graph-path /Game/Veg/PV_Oak --node-name Export_0 \
  --property-path ExportSettings.MeshName --property-value '"SM_Oak"'

cfa export_procedural_vegetation --asset-path /Game/Veg/PV_Oak

Learn from a working tree

Dumps only the values that differ from their defaults, plus the wiring. Epic's shipped tree collapses to 143 authored values, which is what makes two plants comparable.

bash

cfa export_pcg_graph_config --graph-path /Game/Veg/PV_Oak

Check assets_created, not success alone

Verify an export by the assets it wrote. If foliage is missing from the result, the export setting that builds Nanite foliage is on by default and stores leaves as assembly parts rather than geometry, which can render as no leaves at all. Turning it off merges real geometry instead, at the cost of a much heavier export, so thin the foliage first.

Unreal Engine 5.8 and later

Every command here needs 5.8. On 5.6 and 5.7 each one returns a message naming the version and changes nothing, so a script written against 5.8 fails clearly rather than halfway through.

Loading…

PreviousBuild a Modular Character NextReference