What Just Happened

You clicked Transform. Particles appeared. Now we look inside your Part to see what changed.

In Studio’s Explorer window, find your Part and click the small arrow next to it to expand. New children are there that weren’t there before.

The pieces, one at a time

PartIcleProperties — a Configuration instance.

This is where every value the property panel writes ends up. Lifetime, Rate, Color, Size, every graph, every toggle. Each one a separate attribute on this Configuration. The panel reads from here when you select your Part, and writes back when you change a field.

You can open PartIcleProperties in Studio and inspect the attributes directly. One thing to know: most of them match the panel labels (Lifetime, Rate, Color), but some don’t — the panel uses friendlier names where the underlying attribute is more compact. Anim. Steps is stored as TotalKeyFrames. Linger is PartLife. Direction is EmissionDirection. Pos. Mode is PosMode. The per-property tables in the Particiliary list both names side-by-side so you always know which is which.

RenderTemplate — a clone of your Part with most things removed.

This is the visual the plugin duplicates each time a particle is born. It looks like your Part, but stripped down: its Anchored is forced to true, its CanCollide to false, its attributes are cleared, and its non-visual children are gone. The next chapter covers why it’s stripped — it’s the most important design decision in the plugin.

EmitParent — an ObjectValue, currently empty.

If you set this to point at a Folder somewhere in the workspace, emitted particles will be parented to that Folder instead of the plugin’s default location. Useful for keeping your scene organised. Leave it empty for now.

Link — an ObjectValue, also currently empty.

This is how you bind an emitter’s output to another instance — so particles follow that instance as it moves. Linking gets its own chapter (chapter 7). Leave this one empty too.

MeshFlipbooks — an empty Folder.

For frame-by-frame texture animation. You drop numbered Decals in here when you want sprite-sheet behaviour on your particles. We’ll cover flipbooks later.

What happened to your Part itself

Your original Part is still there. The plugin set its Transparency to 1 so it’s invisible without being deleted. Its CanCollide and Anchored stay whatever they were — the source isn’t physically altered, just hidden. Any visual children attached to it (SpecialMesh, Decal, Texture) are moved into the RenderTemplate clone, and the source-side originals are removed so you don’t end up with two of them. Studio’s Ctrl+Z undoes the whole Transform, source children and all.

So you have two copies of the same shape, with different jobs:

• Your Part is the one you edit. Move it, change its size, swap its mesh, pick a different material — those changes flow through to the emitted particles.
• The RenderTemplate is the lightweight copy the plugin duplicates each emit. Its Anchored is forced true and CanCollide forced false so emitted clones don’t drop under gravity or collide with the world.

The plugin uses Roblox’s standard ChangeHistoryService, so Ctrl+Z and Ctrl+Y work as you’d expect on every step the plugin takes.

A side note on selection

If you click on PartIcleProperties or RenderTemplate in the Explorer, the plugin redirects your selection up to the owning Part. You can’t accidentally edit the internals — they always behave as if they’re part of the emitter, not separate things. This is by design.

What’s next

So why is RenderTemplate stripped down? Why not just clone your fully-decorated original Part directly? The next chapter answers, and the answer reshapes how you’ll think about emission speed.