Commands and Permissions

Commands and permissions

All commands live under /vengine, alias /ve. They default to operators.

Commands

Command	Description	Example
/ve help	In-game command overview	/ve help
/ve list	Registered effects, plus currently running instances with their IDs	/ve list
/ve play <name> [scale] [duration]	Plays an effect at your position. scale multiplies the size, duration overrides the effect's duration in ticks (20 ticks = 1 s)	/ve play torus 2.0 200
/ve stop [all|<id>]	Stops one running effect by ID, or everything with all	/ve stop torus#3
/ve reload	Reloads config.yml and every file in plugins/VEngine/effects/	/ve reload

Notes:

• /ve play is a player command - effects always spawn at the caller's position. To place effects at fixed coordinates use the DSL (Location.playEffect) or command blocks via a helper plugin.
• Running effects finish by themselves; /ve stop is only needed to end them early. Finished effects disappear from /ve list automatically.

Permissions

Permission	Allows	Default
vengine.use	Using /ve at all	op
vengine.effect.spawn	/ve play	op
vengine.effect.stop	/ve stop	op
vengine.list	/ve list	op
vengine.reload	/ve reload	op

Configuration

plugins/VEngine/config.yml:

Key	Default	Description
view-distance	64	Particle view-distance culling radius in blocks. A player farther than this from a particle receives no packets for it. Raise for huge shows, lower to save bandwidth

Changes apply with /ve reload.

PlaceholderAPI tokens that read this value, and the rest of the engine state, are listed in Placeholders.

Effect files

• Every file in plugins/VEngine/effects/*.yml is one effect; the file name (or its id: field) is the name used with /ve play.
• Bundled examples are copied only when missing - your edits are never overwritten, and new bundled files appear after updates.
• /ve reload reloads all effect files. Broken files are skipped with a clear warning in the console - see the troubleshooting section in Writing your own effects.