<h1>Notice</h1> ParticleGrenades <strong>REQUIRES</strong> ParticleProjectileApi: <a href="https://modrinth.com/plugin/particleprojectileapi"> https://modrinth.com/plugin/particleprojectileapi</a> <hr /> <h3>Optional</h3> <strong>WorldGuard</strong> for region protection flags <br /> <br /> Flags: <ul> <li>block-break</li> <li>damage-animals</li> <li>pvp</li> <li>potion-splash</li> </ul> <hr /> <h1>Description</h1> <p>Particle Grenades is a plugin designed to allow servers to craft custom grenades that explode with custom particles projectiles that apply effects to entities. These grenades are highly configurable via a configuration file. This config file allows the editor to set almost everything about the grenade. Once a player crafts a custom particle grenade, all they need to do to launch it is to drop it whilst sneaking, as long as they have the correct permission node. This will in turn fire the dropped grenade in the direction the player was looking and will proceed to explode after its timer has expired. There can be multiple grenades with multiple effects in the config as well, thus allowing a whole host of fun and exciting options</p> <h2>Features</h2> <ul> <li>Have multiple grenades</li> <li>Different particles (Some can be colored)!<br /> (0.3.4 adds the ability for grenades to have multiple particles)</li> <li>Different sounds for explosions</li> <li>Each grenade requires a permission node<br /> particlegrenade.use.&lt;node&gt; (Look at configuration below for help)</li> <li>Multiple effects</li> <li>Colored smoke trails</li> <li>Give command<br /> (Requires permission node)</li> <li>Grenades push entities when exploding</li> <li>Custom crafting recipes</li> <li>Custom display name and lore for grenades</li> <li>Color code support for display names and lore</li> <li>Optional and highly configurable block damage</li> <li>Crafted grenades can be placed as custom tnt blocks! (Since 0.3.4+)</li> <li>Grenades can be used with dispensers! (Since 0.3.4+)</li> <li>Highly configurable</li> <li>WorldGuard Support!</li> </ul> <h2>Commands</h2> <ul> <li><b>/pgreload</b><br /> Reloads the config.yml to update changes and change recipes on the fly<br /> Requires the permission <i>particlegrenades.reload</i></li> <li><b>/pglist</b><br /> Lists availble grenades to that player if they can use commands to give<br /> Requires the permission <i>particlegrenades.list</i></li> <li><b>/pggive &lt;grenade&gt; </b><br /> Allows players with proper permissions to give specified amount of grenade to themselves<br /> Requires the permission <i>particlegrenades.give.&lt;internal name&gt;<br /> (Internal name is found in config)</i></li> <li><i><b>/pgspawn &lt;grenade&gt; &lt;x&gt; &lt;y&gt; &lt;z&gt;</b><br /> Spawns the specified grenade at the chosen coordinates</i></li> </ul> <h2>Configuration</h2> <h3>default.yml</h3> ``` name: '&4&lGrenade' description: - '&6A throwable explosive' - '&6Warning: &cContains Explosives!' distance: 1.5 behavior: # Ticks before the grenade explodes fuse: 100 # Should the grenade explode when a player/mob gets to close? proximity: false # If so how close do they need to be? radius: 2.0 # Should it explode upon hitting something? impact: false cooldown: 60 sound: entity.generic.explode:10.0:0.5 effects: - weakness:1:60 - slowness:1:60 particles: # Explosion particles explosion: # List of materials affected by the explosion # A question mark '?' can be used as a wildcard # Using 'RED?' will include 'REDSTONE' but not 'POWERED_RAILS' # Using '?RED' will not include 'REDSTONE' or 'POWERED_RAILS' # Using '?RED?' will include everything with 'RED' in its name # Using '?' will include all blocks # Other available placeholders include: # 'burnable' (Includes all blocks that can burn away # 'flammable' (Includes all blocks that can catch fire) # 'logs', 'leaves' , 'planks' (Are self-explanatory as they include every type they describe) # a hyphen ('-') can be used to negate a certain block/placeholder such as '-logs' will not include any logs # Adding %<#> to the end of a query can add a chance for that material to be affected such as 'stone%10' will add # a 10 percent chance for stone to be affected blocks: # When a particle hits a block... on_hit: # Break it naturally IE item drops if applicable break: - leaves - ?stone? - diorite - andesite - granite - dirt - grass_block - logs # Converts from one set of blocks to another at random # '?,-logs:air%10' will convert all blocks except logs to air with a 10 percent chance of becoming air convert: - grass_block:dirt - dirt:gravel - gravel:sand - sand:air%50 # Destroy i