Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ParticleHat Suggestions #16

Open
bigdaddyky opened this issue Apr 22, 2023 · 3 comments
Open

ParticleHat Suggestions #16

bigdaddyky opened this issue Apr 22, 2023 · 3 comments

Comments

@bigdaddyky
Copy link

Here is a bunch of suggestions that I've compiled over a couple months using this plugin on my server.

  • A way for a single player to disable themselves from seeing particles all together. Although, Minecraft settings is probably their best bet at obtaining such a option, it would be nice for players to view Minecraft particles normally and not have the potential increased lag that comes with having to see an intensive amount of particles coming from somebody else's enabled particle hat.

Suggested command usage: /h view <enable|disable>

  • Configable values for 'demo' methods. I found that the demo part of the command to be very useful and would love to be able to see API usages of this along-side a way for me to set an amount of time instead of it being a fixed value from the author. I saw you mentioned you'd like for me to elaborate on this suggestion so here's at it:

Suggestion usage: /h demo <tellPlayer true|false>
Suggestion API usage:

    /**
     * Creates a new hat from the given label and equips it
     *
     * @param player The player this new hat will be given to
     * @param label The unique label that defines this hat
     * @param tellPlayer Shows the player the HAT_EQUIPPED message
     * @param long You can decide how long you'd like to display this label for in ticks.
     * @throws InvalidLabelException If label doesn't not exist
     * @throws IllegalArgumentException If any arguments are invalid
     */
    public abstract void equipHatFromLabel(Player player, String label, boolean tellPlayer, long ticks) throws InvalidLabelException, IllegalArgumentException;
  • MiniaturePets support. The MiniaturePets plugin is a great way for us to create different models using armor stands. Being able to attach particles would be an absolute bonus. It would be cool to have a configuration file seperately for MiniaturePets and a menu similar to the CitizensNPC usage.

image
image

  • Animations from files. Right now ParticleHats have it so if you put a PNG image into the 'types' folder, you can use that image as a type for your particle. It would be cool if you could put folders inside of the type folder and have numerous PNG files that the plugin loops over to create an animated image. I would believe this to be a complex idea but here's kind of a better understanding:

image
image

Please read with a grain of salt, these are just ideas that I have ran into issues with that I personally would love to be implemented. Again, thank you for such an awesome plugin :)

@MediusEcho
Copy link
Owner

A way for a single player to disable themselves from seeing particles all together. Although, Minecraft settings is probably their best bet at obtaining such a option, it would be nice for players to view Minecraft particles normally and not have the potential increased lag that comes with having to see an intensive amount of particles coming from somebody else's enabled particle hat.

I'm not sure if there is a way to spawn particles through the API that only specific players can see.

Configable values for 'demo' methods. I found that the demo part of the command to be very useful and would love to be able to see API usages of this along-side a way for me to set an amount of time instead of it being a fixed value from the author. I saw you mentioned you'd like for me to elaborate on this suggestion so here's at it:
Suggestion usage: /h demo <tellPlayer true|false>

in v5.0 you will be able to change most of the particle properties by command through what I call "flags". So something like /h set <player> <label> <demo true|false> <tellPlayer true|false> will become /h hat <label> give <player> <flags>. So changing the demo duration would be as simple as including it as a flag: /h hat <label> give <player> duration:60, or /h hat <label> give <player> duration:60 type:halo animated:true. The syntax is not 100% decided on yet but the flags will function the same.

MiniaturePets support. The MiniaturePets plugin is a great way for us to create different models using armor stands. Being able to attach particles would be an absolute bonus. It would be cool to have a configuration file seperately for MiniaturePets and a menu similar to the CitizensNPC usage.

I'll look into this, my goal for v5.0 is to decouple the particle spawning from players so that particle effects can be attached to anything.

Animations from files. Right now ParticleHats have it so if you put a PNG image into the 'types' folder, you can use that image as a type for your particle. It would be cool if you could put folders inside of the type folder and have numerous PNG files that the plugin loops over to create an animated image. I would believe this to be a complex idea but here's kind of a better understanding:

I like the idea, but I'm not sure it would work for someone using the MySQL database. Combining images into animations will come in v5.0.

@bigdaddyky
Copy link
Author

A way for a single player to disable themselves from seeing particles all together. Although, Minecraft settings is probably their best bet at obtaining such a option, it would be nice for players to view Minecraft particles normally and not have the potential increased lag that comes with having to see an intensive amount of particles coming from somebody else's enabled particle hat.

I'm not sure if there is a way to spawn particles through the API that only specific players can see.

Configable values for 'demo' methods. I found that the demo part of the command to be very useful and would love to be able to see API usages of this along-side a way for me to set an amount of time instead of it being a fixed value from the author. I saw you mentioned you'd like for me to elaborate on this suggestion so here's at it:
Suggestion usage: /h demo <tellPlayer true|false>

in v5.0 you will be able to change most of the particle properties by command through what I call "flags". So something like /h set <player> <label> <demo true|false> <tellPlayer true|false> will become /h hat <label> give <player> <flags>. So changing the demo duration would be as simple as including it as a flag: /h hat <label> give <player> duration:60, or /h hat <label> give <player> duration:60 type:halo animated:true. The syntax is not 100% decided on yet but the flags will function the same.

MiniaturePets support. The MiniaturePets plugin is a great way for us to create different models using armor stands. Being able to attach particles would be an absolute bonus. It would be cool to have a configuration file seperately for MiniaturePets and a menu similar to the CitizensNPC usage.

I'll look into this, my goal for v5.0 is to decouple the particle spawning from players so that particle effects can be attached to anything.

Animations from files. Right now ParticleHats have it so if you put a PNG image into the 'types' folder, you can use that image as a type for your particle. It would be cool if you could put folders inside of the type folder and have numerous PNG files that the plugin loops over to create an animated image. I would believe this to be a complex idea but here's kind of a better understanding:

I like the idea, but I'm not sure it would work for someone using the MySQL database. Combining images into animations will come in v5.0.

Thank you for the response and acknowledging my suggestions. Much love.

@bigdaddyky
Copy link
Author

Oh I thought of another cool suggestion which is more of a QOL change but it would be nice for users to mimic particle nodes within the particle's node menu.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants