Puff
Puff
Puff
(also called Smoking Mod by some of my friends)
What does it do?
- If a moderator moves, he/she will leave a trail of smoke!
Why would you want this?
I originally made this for my own server SuCraft to make myself look cool. ;) You may have the same inclinations to distinction.
Installation
Just drag the Puff.jar into your /plugins folder. It's that easy!
Commands
None.
Permissions
Ops automatically have permissions.
- puff.move - the player can leave a trail of smoke
Future possibilities
- More ways to leave or create smoke
- Implement some more permissions
- Make a decent config
Suggestions and feedback
Leave it in the comments below!
I've been looking for a mod I've seen in a few youtube videos, that is simply a player holding an item (it's usually just a stick or some other placeholder) and when they right click puffs of smoke are created near their head. To me, this seems like it would be a relatively easy plugin to make for bukkit servers, without any client mod.. But I have yet to find one. :/
Is there any way you could add other effects? Like fire for example?
You you possibly add VanishNoPacket support? So the particles don't show when vanished?
@imilkywayz
Thanks, I didn't think of that at all!
The plugin should not be too intensive at the moment. Have tested it today and there is no CPU usage difference. Also I wonder how most authorisation plugins (like AuthMe and xAuth) are written cause they constantly check for player move events too (as a player that moves but is not logged in should be put back in place). But perhaps they found another way.
I'll see what I can do, thanks anyway!
Seems Extremely server resource intensive.. Every time a player moves (with permission) but still. Firing an event every time a player moves, wether its that simple or not is bound to use lots of resources. How about this, instead of ranting, ill purpose a fix. Make a cool down in between the check for player move, and subsequent 'smoke'. Playermove -> Checks if player is in hash map, by default isnt.. -> smoke -> puts player in hash map - > a runnable runs after a set amount of time -> takes player out of hash map. Seems a lot more practical. I mean i doubt having this plugin will make any real impact on performance but hey what if you have 10 ops and 10 moderators all flying around with there flymod.