FleetingDisguises
This plugin uses DisguiseCraft's API in order to set a per-mob time limit on disguises. It also adds a cool-down between disguises.
Development of this plugin was sponsored by Aerocraft.
Features:
- Allows you to set a time limit on disguises.
- Allows you to set a cool-down between disguises.
- A permission node allows for exempt from the time limit or cool-down.
Permission Nodes:
Defaulted to ops
- fleetingdisguises.*: Has full FleetingDisguises privileges
- fleetingdisguises.timelimit.exempt: Has no disguise time limit.
- fleetingdisguises.cooldown.exempt: Has no disguise cooldown.
How-To:
- Download the plugin and place it in your "/plugins" folder.
- Restart or reload the server.
- Edit the configuration to choose disguise and cool-down lengths.
- Restart or reload the server.
@np98765
What version of DisguiseCraft are you using?
Hi,
When my users disguise, I get:
Anything I'm doing wrong, or any other information you need? Thanks.
@JayFight
Thank you for your support :)
I do many times forget that there are still people out there that know we're just trying to help and can't cater to everybody.
And yes, it is completely true that having functions in separate plugins allows certain parts to keep working through updates. This reduces critical "down time" and allows us to work directly with the issue without panicking as much about time.
i would just like to say as a server owner that i ,for one, don't mind extra jars. mainly because if one plugin is broken by a minecraft update and another isn't then i can keep using the one and not the other and there would be less problems but if they're all in the same jar (like with essentials) then if one part breaks the whole thing generally breaks and that means i have to downgrade my server until a new update for the one thing is ready or else my whole server goes kaput
so please don't be upset because some server owners are kind of all about the "ME ME ME" because there are some of us out here who know that with out people like you then we wouldn't be able to run a server with all of the cool stuff on it
in other words i just wanted to say THANK YOU for everything you do and i hope you guys feel appreciated so that you'll never hate making or updating your plugins because they are awesome (plus disguisecraft is a thousand times better then mobdisguise, no offense ment to them) :D
@domingo15
This plugin is not a temporary fix for the PVP issue. It was made to present a new set of functions to MobDisguise. It was merely ported over to work with DisguiseCraft. If you really don't want to have to place another file into your "plugins" folder. Just edit the DisguiseCraft code to include the event handlers in this plugin's source. Both the plugins are open-source, so you should have no issues editing it for yourself.
Heh... the majority of our team is not pinoy. We've turned into a group of developers who sometimes release plugins here mainly to share knowledge with other developers. We really like when people look through and learn from our source.
@Devil_Boy
well its not about being needy its to make a temporary fix on the pvp issue without adding another .jar to the plugins because by the looks of things the bukkit team is busy with some other things.
Note: I've check out that logo on your signature and looked like you guys are pinoy, which is great :), just nice to hear seeing other pinoys interested on creating bukkit plugins and etc...
@domingo15
I can, but I won't. DisguiseCraft is a client-side disguise handler system. It was not designed to be a plugin customizable to everybody's needs. (And it has been shown that you server admins are very needy.) We utilize the API to handle anything beyond its original functionality.
You'll have to get used to this.
@Devil_Boy
why can't you just add this with DisguiseCraft rather than making a new plugin for it, including the MobDisguisePvPControl?
but for MobDisguisePvPControl, have the option to enable it or disable after the pvp issue is fixed, if it will ever be fixed.
@JayFight
It's a great idea, but the method you suggested would be a bit buggy on the permissions end. (Dynamic permissions aren't supported all the time)
I think if we find the time to add it, we would make multiple configuration files and allow you to list which config applies to which players.
hey there i just wanted to say this is awesome and everything, but i was wondering if you might be able to do a permission based timing for this. you know something like in the config it would be like (all times in the example are in seconds)
Guest:
- Creeper: 20
- cooldown: 560
- Wolf: 30
- cooldown: 340
Player:
- Creeper: 60
- cooldown: 400
- Wolf: 120
- cooldown: 200
Moderator:
- Creeper: 120
- cooldown: 10
- Wolf: 0 (0=unlimited)
- cooldown: 0 (0=no cooldown)
and then in permissions it would be like
fleetingdisguise.group.player
or maybe have it in the config
Player: 1
where 1 is the permission you guys would have it for and the permission would be
fleetingdisguise.rank.1
btw these are just suggestions for permission based timing so that higher ranked people could have longer lasting disguises and can transform more often if you don't impliment it then it's all cool i just figured if you guys haven't thought of this yet then i might as well put it here for you to think about.
thank you for your time, efforts, and awesome plugins
Best thing ever <3
Awesome. Hehe now we can trust players with this.