PlayerParticles Minecraft Plugin

repository·master·Indexed 41 days ago

https://github.com/rosewood-development/playerparticles

A highly customizable Minecraft plugin for creating complex particle effects around players and blocks. Compatible with Spigot, Paper, and Minecraft versions 1.7.10 and newer (requires Java 8+). Features include a variety of pre-crafted styles, support for all in-game particle types, and a comprehensive command system for adding, editing, and managing both player-centric and fixed-location particle effects.

Tokens
5.7K
Snippets
24
Records
36
Agent score
51%

What's inside PlayerParticles

  1. Check Server Compatibility for PlayerParticles

    master

    Before installing, ensure your server environment meets the following requirements:

    • Server Software: Compatible with Spigot and its forks. Paper is the recommended server implementation. Note that CraftBukkit is not compatible.
    • Minecraft Versions: Supports version 1.7.10 and all newer versions.
    • Java Version: Requires Java 8 or newer.
  2. Use the `/use` command to modify particle effects

    master

    The /use command allows players to apply or modify the particle effect, style, or specific data (like color or material) of their active particle group.

    Command Syntax: /use <type> <value>

    Available Types:

    1. effect: Sets the base particle effect.

      • Example: /use effect <effect_name>
      • Requires permission for the specific effect.
    2. style: Sets the visual style of the effect.

      • Example: /use style <style_name>
      • Requires permission for the specific style.
    3. data: Sets specific parameters for the currently active effect. The required format for <value> depends on the dataType of the current effect:

      • COLORABLE:
        • If the effect is NOTE: Use <0-24>, rainbow, or random.
        • Otherwise: Use RGB values (<0-255> <0-255> <0-255>), a color name, or a hex code (<#hexCode>).
      • COLORABLE_TRANSPARENCY: Use RGB and optional Alpha (<0-255> <0-255> <0-255> [0-255]), color names, or hex codes.
      • BLOCK: Use a valid block material name.
      • ITEM: Use a valid item material name.
      • COLORABLE_TRANSITION: Sets a color transition. Typically starts with an OrdinaryColor followed by additional color parameters.
      • VIBRATION: Use a duration value (e.g., 20, 40, 60).

    Note: This command cannot be executed by the console; it must be run by a player.

    /use effect <effect_name>
    /use style <style_name>
    /use data <value>
  3. Use the `add` command to create particle effects

    master

    The add command allows players to add a new particle effect to their active particle group. The command requires an effect type and a style, and optionally accepts data specific to the chosen effect type.

    Usage Syntax: <effect> <style> [data]

    Command Requirements:

    • You must have permission to use the specified <effect>.
    • You must have permission to use the specified <style>.
    • You must not have reached your maximum allowed particle limit (configured via PermissionManager).
    • This command cannot be executed from the server console; it must be run by a player.
    add <effect> <style> [data]
  4. Create a fixed particle effect with /pp fixed create

    master

    To create a new fixed particle effect, use the following syntax:

    /pp fixed create [looking] <location> <effect> <style> [data]

    Arguments:

    • looking (Optional): If used, the effect is created at the location the player is currently looking at. This simplifies coordinate input.
    • <location>: The coordinates for the effect. If not using looking, you can use relative coordinates (e.g., ~ ~ ~) or absolute coordinates. If using the console, you must provide <x> <y> <z> <world>.
    • <effect>: The type of particle effect to use (e.g., NOTE, BLOCK, ITEM).
    • <style>: The visual style of the effect. Note that not all styles are compatible with fixed effects.
    • [data]: Additional parameters required by the chosen effect type, such as colors, materials, or vibration settings.

    Example (Player): /pp fixed create looking flame circle (Creates a flame circle effect where the player is looking) /pp fixed create ~ ~ ~ heart circle (Creates a heart circle effect at the player's current position)

    /pp fixed create [looking] <location> <effect> <style> [data]
  5. Manage fixed particle effects with /pp fixed

    master

    The /pp fixed command suite allows players and administrators to create, edit, remove, and manage particle effects that remain at fixed locations in the world.

    Available Subcommands:

    • create: Creates a new fixed particle effect at a specified location.
    • edit <id> <property>: Modifies an existing effect (e.g., location, effect, style, or data).
    • remove <id>: Deletes a specific fixed effect by its ID.
    • list: Displays a list of all fixed effect IDs owned by the player.
    • info <id>: Shows detailed information about a specific effect, including its ID, location, effect type, and style.
    • clear <radius> [location]: Removes all fixed effects within a specified radius of a location (requires specific permissions).
    • teleport <id>: Teleports the player to the location of a specific fixed effect.
  6. Use the edit command to modify particle properties

    master

    The edit command allows you to modify an existing active particle's effect, style, or specific data (like color or material) using its unique ID.

    Command Syntax: <ID> <effect|style|data> <args>

    Subcommands:

    • effect: Changes the ParticleEffect of the particle.
    • style: Changes the ParticleStyle of the particle.
    • data: Changes specific data associated with the effect (e.g., color, block material, or item material). The required arguments for data depend on the current effect's DataType.
    /edit <ID> effect <effect_name>
    /edit <ID> style <style_name>
    /edit <ID> data <data_args>
  7. Use the default PlayerParticles command to open the GUI

    master

    The base PlayerParticles command (the command without arguments) acts as a shortcut to open the main plugin GUI. When executed, it redirects the player to the gui command module, allowing them to interact with the plugin's visual interface.

    # Execute the base command to open the GUI
    /playerparticles
  8. Manage particle groups with /pp group commands

    master

    The /pp group command allows players to manage collections of particles, including saving their current setup, loading previously saved groups or presets, unloading specific particles, and removing groups.

    Sub-commands:

    • save <groupName>: Saves the player's currently active particles as a new group. The name is truncated to 100 characters. You cannot save the default group name.
    • load <groupName>: Loads a saved group or a preset group into the player's active particles. This replaces the current active particles.
    • unload <groupName>: Removes all particles from the player's active set that match the effect and style of the particles defined in the specified group or preset.
    • remove <groupName>: Deletes a saved particle group. Note that removing a preset group may behave differently depending on permissions.
    • info <groupName>: Displays detailed information about a group, including the ID, effect name, style name, and data string for each particle in the group.
    • list: Lists all of the player's saved particle groups and available presets.
    /pp group save <groupName>
    /pp group load <groupName>
    /pp group unload <groupName>
    /pp group remove <groupName>
    /pp group info <groupName>
    /pp group list
  9. Clear fixed effects in a radius with /pp fixed clear

    master

    Administrators can remove multiple fixed effects within a specific area using the clear command.

    Syntax: /pp fixed clear <radius> [location]

    • <radius>: The distance from the center point within which effects will be removed.
    • [location]: The center point for the clearing operation. If omitted, it defaults to the player's current location. If used via console, a specific location must be provided.

    Example: /pp fixed clear 50 (Removes all fixed effects within a 50-block radius of the player)

    /pp fixed clear <radius> [location]