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. 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.

Create a Niagara System

A guided example: create a Niagara system, add an emitter and modules, set inputs, and compile a working effect.

This walkthrough creates a Niagara particle system from scratch: make the system, add an emitter, add a module to its stack, set a module input, and compile. Niagara is the largest command category, so the Niagara reference is the place to see every stack, renderer, and parameter operation.

Create the system

A new Niagara system asset. Start empty or from a template.

bash

cfa create_niagara_system --asset-path /Game/VFX/NS_Sparks

Add an emitter

Add an emitter to the system's stack.

bash

cfa add_niagara_emitter --system-path /Game/VFX/NS_Sparks --name Sparks

Add a module

Add a module to the emitter's stack (spawn, velocity, color, and so on).

bash

cfa add_niagara_module --system-path /Game/VFX/NS_Sparks --emitter Sparks --module SpawnRate

Set a module input

Set a value on the module you added.

bash

cfa set_niagara_module_input --system-path /Game/VFX/NS_Sparks --emitter Sparks --module SpawnRate --input SpawnRate --value 200

Compile

Compile the system so it is ready to use.

bash

cfa compile_niagara_system --system-path /Game/VFX/NS_Sparks

Exact parameters

Module and input names vary by module; the exact parameters for each command are in the Niagara reference, or run cfa describe add_niagara_module.

Loading…

PreviousAuthor a Material Graph NextReference