Minecraft Particle Commands Tutorial - Bedrock Edition

A tutorial for Minecraft`s Particle Commands. Featuring a selection of these commands and potential applications in-game.

[@gangstercat7725]

Thanks man was building a map Which needed some polish . The only thing Which didn’t work was the endrod particle effects.

[@neighborboar744]

Intro goes hardddd

[@mcweebking7913]

Thanks man this helps

[@Xylem-dc1fo]

/particle minecraft:large_explosion ~ ~2 ~

[@kvng.badass1593]

For me it says that all players are requested to create a certain command. How do i fix this?

[@dylanchavez1539]

yea me too. i am trying to find a solution but i dont think there is

[@paulmcj]

Hi are trying to use the commands on a server? And are you using Bedrock or Java. The closest answer I can find gaming.stackexchange.com/questions/163531/how-do-i-keep-players-from-accessing-certain-commands 5 By default, the majority of commands (with the exception of /me, /tell, /help, and /trigger for some reason) are restricted to server ops. Players are, by default, not allowed to use any other commands on a server. Server ops can use other commands. You can specify ops in the ops.txt file, or by using the command /op in the console, or in-game (assuming you have added yourself as an op). By default, server ops have access to all commands, including commands like /stop. You can change this by modifying the op-permission-level in your server.properties file. Setting it to 4 (which is the default) allows ops to use all commands. Setting it to 3 restricts the /stop command, setting it to 2 restricts server moderation commands (/kick, /ban, /op, /deop), and setting it to 1 removes all special permissions from ops other than the ability to bypass spawn protection. You can still use all of these commands in the server console.