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.

Procedural Vegetation

Every Procedural Vegetation command in CodeFizz Editor Agent, with parameters and examples.

9 commands. Each shows its parameters and an example, and has a copyable deep link, so you (or an AI agent) can jump straight to one.

search_pv_nodes

Search the Procedural Vegetation add-node menu (UE 5.8 only)

Enumerates the vegetation graph's add-node menu exactly as the editor renders it, by driving the plugin's own UPVEditorSchema rather than a hardcoded table, so titles, categories and descriptions are always what this engine actually has. Pass --filters to run several keyword searches in one round trip; each is capped at --max-results and reports total_matches plus a truncated flag so nothing is dropped silently. Categories include Foliage, Growth, Growth Settings, Mesh, Mesh Builder Settings, Distribution Settings, Post Growth Modifiers, Input Output, Seed, Params, Math, Control flow, Subgraph and Development. Requires UE 5.8 and the Procedural Vegetation Editor plugin enabled; on 5.6/5.7 it reports that it is 5.8 only.

Parameter	Type	Required	Description
filter	string	No	Single keyword matched against title, class name, category or description
filters	stringlist	No	Batch form: one search per keyword, each capped at max_results
category	string	No	Restrict to one exact menu category, e.g. "Growth Settings"
max_results	int	No	Maximum results per keyword

example

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

list_pv_node_categories

List Procedural Vegetation node categories with node counts (UE 5.8 only)

Returns the add-node menu's real category names and how many nodes each holds. Use this before search_pv_nodes --category so the category string is exact rather than guessed.

Parameter	Type	Required	Description
filter	string	No	Case-insensitive substring on the category name

example

cfa list_pv_node_categories

describe_pv_nodes

Get full schema for one or more Procedural Vegetation nodes (UE 5.8 only)

Returns each node's title, category, description, pins, and its editable property schema, dotted property paths, types, defaults, per-property descriptions, and the valid values inline for every enum. The paths returned are exactly what set_pcg_node_property_path and get_pcg_property_valid_values accept, so discovery chains straight into editing. Pass --nodes to describe several in one round trip. Unknown names come back with found=false and a pointer to search_pv_nodes rather than failing the whole batch.

Parameter	Type	Required	Description
node	string	No	Single node class name, title or class path
nodes	stringlist	No	Batch form: several node names in one call
include_pins	bool	No	Include input/output pin names
include_properties	bool	No	Include the editable property schema
max_depth	int	No	How deep to walk nested property structs (4 reaches every real setting; 5+ pulls in curve key arrays)
max_properties	int	No	Cap on properties returned per node; check total_properties and properties_truncated
category	string	No	Only properties in this Details-panel category, e.g. Bifurcation, Gravity, Phyllotaxy

example

cfa describe_pv_nodes --nodes PVGrowerSettings,PVFoliageDistributorSettings --max-depth 3

export_pv_schema

Write the full Procedural Vegetation node schema to a JSON file (UE 5.8 only)

Dumps the complete schema, every node, every pin, and every editable property with its category, type, default, Epic's own description, enum values, UI/clamp ranges and edit-condition, to Saved/CodeFizzEditorAgent/Exports/<name>_<stamp>/<name>.pvschema.json, and returns only the file path plus counts. Use this instead of describe_pv_nodes when you want everything: the Grower alone has over 600 properties, so reading them inline would bury the context that is supposed to be using them. Omit --nodes to export every vegetation node in one file.

Parameter	Type	Required	Description
nodes	stringlist	No	Nodes to export; empty exports every vegetation node
name	string	No	Base filename (default ProceduralVegetationSchema)
max_depth	int	No	How deep to walk nested property structs

example

cfa export_pv_schema --nodes PVGrowerSettings,PVMeshBuilderSettings --name GrowerAndMesher

create_procedural_vegetation

Create a Procedural Vegetation asset (UE 5.8 only)

Creates a new Procedural Vegetation asset headlessly, with no modal dialog. Without --sample you get an empty graph holding only the Input and Output nodes. With --sample the asset is duplicated from an existing one, which is how the editor's "create from sample" works, run list_pv_samples to see what is available, including Epic's four shipped starter trees.

Parameter	Type	Required	Description
asset_path	string	Yes	Destination, e.g. /Game/Vegetation/PV_MyTree
sample	string	No	Optional source asset to copy from; empty creates an empty graph

example

cfa create_procedural_vegetation --asset-path /Game/Vegetation/PV_MyTree --sample /ProceduralVegetationEditor/SampleAssets/StarterContent/ConiferTree_01/PVE_Sample_Conifer_Tree_01

export_procedural_vegetation

Export a Procedural Vegetation asset to mesh assets (UE 5.8 only)

Runs the vegetation editor's own Export action, the same code path as clicking Export in the toolbar, and auto-confirms its modal dialog, so the whole thing completes without a human click. Epic exposes no scripted export entry point, so this drives the real UI command rather than reimplementing the mesh writer. Validates first and fails loudly on the conditions Epic's own handler treats as a silent no-op: no Export node in the graph, or an Export node with no MeshName. --force-append (default) sets ReplacePolicy=Append so the overwrite dialog never appears. Per-asset results land in the PVEditor message log, read them with read_message_log --log-name PVEditor. Two-call pattern: export reads the graph's EVALUATED mesh data, so on a graph that has not generated yet the first call opens the asset editor, starts generation, and returns needs_generation=true with assets_created=0. Wait for generation to finish, then call again and it succeeds. It cannot wait internally because generation runs on the same game thread the command occupies. Verify by reading assets_created / created_assets, never by success alone.

Parameter	Type	Required	Description
asset_path	string	Yes	Procedural Vegetation asset to export
force_append	bool	No	Set ReplacePolicy=Append so the overwrite dialog never appears

example

cfa export_procedural_vegetation --asset-path /Game/Vegetation/PV_MyTree

preview_pv_node

Preview a node's output in the open editor viewport (UE 5.8 only)

Selects a node in the open asset editor, which is what drives the 3D viewport preview, select the Grower to see the point/branch skeleton, Bone Reduction to see bone colouring, the Foliage Distributor to see the finished tree. This reads cached inspection data and does NOT re-run the graph, so switching preview is cheap. Use it instead of reopening the asset. Note the graph already regenerates by itself whenever you change a node property, connect a pin, or add/remove a node, you do not need to trigger that. Selection lands over the next few editor ticks, so pause briefly before screenshotting.

Parameter	Type	Required	Description
graph_path	string	Yes	Vegetation asset or PCG graph whose editor is open
node_name	string	No	Node by stable name (preferred)
node_index	int	No	Node by index; -2 = graph input, -1 = graph output

example

cfa preview_pv_node --graph-path /Game/Vegetation/PV_MyTree --node-name ProceduralVegetationFoliageDistributor_0

export_pcg_graph_config

Dump a PCG/vegetation graph's AUTHORED configuration to a file (UE 5.8 only)

Writes every node's non-default property values plus the full wiring to a JSON file. Only values that differ from the class default are emitted, which collapses thousands of properties down to the handful the author actually set, that is what makes two graphs diffable. Use it to learn from a working asset: dump Epic's shipped sample, dump yours, and compare. Each entry carries the current value and the default it replaced.

Parameter	Type	Required	Description
graph_path	string	Yes	Graph or vegetation asset to dump
name	string	No	Base filename; defaults to the asset name
max_depth	int	No	How deep to walk nested structs

example

cfa export_pcg_graph_config --graph-path /ProceduralVegetationEditor/SampleAssets/StarterContent/DeciduousTree_01/PVE_Sample_Deciduous_Tree_01

list_pv_samples

List Procedural Vegetation assets available as creation samples (UE 5.8 only)

Lists every Procedural Vegetation asset the asset registry knows about, including Epic's shipped samples under /ProceduralVegetationEditor. Feed a path straight into create_procedural_vegetation --sample.

Parameter	Type	Required	Description
filter	string	No	Case-insensitive substring on the asset name
max_results	int	No	Maximum number of results

example

cfa list_pv_samples --filter Tree

Loading…

PreviousPCG NextMaterials

Parameter

Type

Required

Description

filter

string

Single keyword matched against title, class name, category or description

filters

stringlist

Batch form: one search per keyword, each capped at max_results