FiveM particle effect list

RequestNamedPtfxAsset only asks. Until HasNamedPtfxAssetLoaded returns true the effect name resolves to nothing, every start call quietly fails, and there is no error in the console to tell you why. Wait for the load. One Wait(0) loop is the whole fix, and skipping it is far and away the most common reason a correct effect name draws nothing.

It is not a mode you switch on. It points the next start call at an asset and is then spent, which the native documentation says in as many words. Two effects means two UseParticleFxAsset calls, and a loop that starts effects per frame needs one inside the loop — not above it.

StartParticleFxLoopedAtCoord hands back a handle. Lose the handle and the effect is permanent for that client: StopParticleFxLooped takes the handle and nothing else can find it. Keep every handle you create, stop them when the thing they belong to ends, and stop them again in an onResourceStop handler.

StartParticleFxLoopedAtCoord and StartParticleFxNonLoopedAtCoord are client-local. Nobody else sees them, however correct they look on your screen. The networked variants replicate — but there is no networked looped at-coord native at all, so a looped effect at a fixed world point has to be started by every client that should see it, usually off a server event.

Scale is a multiplier on an effect that was authored at a particular size, so an effect built for a car explosion at 0.1 is a few invisible pixels. The three booleans after it invert the effect on the X, Y and Z axis; almost every working snippet passes false for all three, and flipping one by accident turns a plume upside down into the ground.

An effect name carries no flag for looped or one-shot, and some names only behave in one of the two. Nothing on this page claims to know which: try the one-shot first because it cleans itself up, and if it flashes and vanishes when you wanted a plume, run the same name looped.

Runs until stopped. Returns a handle you keep and later pass to StopParticleFxLooped. For anything persistent: a burning barrel, a leaking pipe, a smoke column over a fixed point.

One shot, then gone. Nothing to keep, nothing to stop, nothing to leak. For impacts, bursts and anything that happens once.

The same one shot, replicated to other players. This is the one to use for an effect other people are supposed to witness — an explosion, a firework, a splash.

The only networked looped family, and it must be attached to an entity rather than a coordinate. If your looped effect needs to be visible to everyone, either hang it off an entity with this, or broadcast an event and have each client start the local version itself.