Stables
What does it do?
Stables is a plugin that assists with Horse ownership, protection, and other horse related things. Vanilla has no ownership or tracking of horses, only if it has been broken or not. Stables changes this behavior.
Important MC1.11 Notes!
This new version (1.9.11) MAY NOT WORK WITH OLDER MC VERSIONS! It has ONLY been tested with MC 1.11!
MC 1.11 changed a lot with horses. As of Stables v1.9.11, some changes must be made in order to accommodate Llamas, Donkeys, Mules, Zombie horses and Skeleton Horses. In your config.yml, In the "animals" section, you MUST add these to the "allowed" list. Anything NOT in the allowed list will NOT be covered by Stables! (example: allowed: HORSE, ZOMBIE_HORSE, SKELETON_HORSE, LLAMA, DONKEY)
Again, as far as 1.11 is concerned Mules, Donkeys, Zombie/Skeleton horses are NOT Horses, and must be entered SEPARATELY into the config!
As of right this moment, Llama carpet does NOT save. Testing of this version has been VERY limited. Please report any and all bugs via tickets - Be as specific in your reports as possible!
Another note: v1.9.11 will create a new table in your database for stored/stabled horses, and copy all the values over, converting what needs to be converted. For safety purposes, the old table will NOT be removed. It will just no longer be used. I would suggest NOT deleting it yourself for a bit, in case you need to restore a previous version.
All localization messages are still 'Horse' and 'Steed' specific. New default messages will be added in time. As always, you can edit them yourself in the 'language.yml' file.
Requirements
- To use COST based virtual stables, Vault is required. Free storage does not require any additional plugins.
Current Features
- Protect Horses from configurable outside damages, including PVP, Environmental (falling/lava) and Monsters
- Adds recipes for Horse Armor (Barding), Name Tags and Saddles
- Now has customizable recipes for these items!
- Adds 'ownership' to horses so others cannot steal them - Use a name tag on a horse to claim it!
- Store horses in virtual stables, and recover them!
- Abilities for Admin/Staff to Remove Ownership
- Sets a max amount of horses one player can own
- Anyone with the stables.admin permission can use horses without permission
- Allow a friend to ride a claimed horse
- Lure a horse from the wild using an item (defaults Golden Carrot - Other suggestions would be Emeralds, Golden Apples)
- Horse Spawning, including ZOMBIE and SKELETON horses!
- Teleport, Summon and Locate your claimed Horses!
- Allows staff to rename horses without changing ownership
- UUID storage for databases -
- Uses connections to 'api.mojang.com' and 'sessionserver.mojang.com' if UUID cannot be resolved on the server.
What's in store for new releases?
- Horse Trading
- (NPC) Races
- Horse purchasing (from NPC)
Permissions & Commands
Please see the Permissions & Config Page here.
How does it work?
Name a horse to claim it as your own. Hit it (as the owner) with a new Name Tag (un-renamed) to free it!
- To name a horse, you have to get a NAME TAG. Use the NAME TAG in an ANVIL and change it's name to what you want the horse to be called. Then USE (Right Click) The Horse with the NAMED NAME TAG to name it. This is a VANILLA MINECRAFT feature - it is not included with Stables. This action, however, is what will claim a horse with the Stables plugin.
- You can also set the config to 'AutoOwn = true' - This will automatically claim a horse as soon as it is tamed!
Stables also prevents horses from being killed by players, mobs, environmental, or any combination of these. All options are 100% toggle-able through the config.
Virtual Stables
This feature can be disabled by the admins by setting the 'allowCommand' config option to false, and then just not creating any stable signs.
To create a stable, simply place a sign with [stables] as the first line. Stables will take over from there. If 'allowCommand' is disabled, you can ONLY use the Virtual Stables feature with a sign. Punch the sign, or type /stables store to store a horse. Please note: Storage does *NOT* save chests right now, nor will it save saddles. This is a known bug.
- Please note: The stables does *NOT* save Horse Speed. This is a Minecraft/Bukkit shortfall, and will be addressed as soon as there is a way to do so.
The Config
Please see the Permissions & Config Page here.
Recipes
Stables makes several items craftable - specifically Saddles, Barding (Horse Armor) and Name Tags.
Setting the config option for hard mode recipes will change all ingots/bars to blocks instead.
Localization & Custom Messages
Upon the first run, a file called 'language.yml' will be generated. This will have all the phrases, in English. You may change the phrases to whatever you'd like, or any language you'd like.
@raum
when set to stables.VIP1 I still have no luck.
I even can get more horses then the MaxOwned value.
MaxOwnedVIP: 5 is template setting from your plugin, I assumed this should be a valid setting then.
While making this message pimsserver beat me to it lol
I gave my VIPs stables.vip, stables.vip1, stables.vip2 and stables.vip3 :p
@zizitt
The only recipe that isn't directly from Mojang is the nametags. The saddles and the armor are from original snapshot recipes that ended up getting pulled.
I'll add that to the todo list, but it's by no means a priority.
We want a feature to change the recipies...!!
@dutchy1001
Give stables.VIP1, not just .VIP - Hopefully I'll finish up the additions and re-upload it tonight .... if the Steam Sale doesnt' get int he way.
I have the same issue as Nex01 and Pimsserver. I do use Groupmanager.
MaxOwned:3
MaxOwendVIP:5
permission given "stables.VIP"
Can't get more then 3 horses
Setting MaxOwned:10 will give the 10 horses while Vip is still on 5 with the same permission.
@raum
Thanks. Because I don't wanna use an other permission plugin because I always used pex on my server and don't want to redo all permissions and give every single user a new rank X_X Unless the permissions.yml of PEX is compatible with group manager too.
Can I change the "MaxownedVIP" into "Maxownedmyrank" in the config, ofcourse using then "stables.myrank" as permission?
And/or can we add VIP4, VIP5 , etc etc?
If I give "MaxOwnedVip: -1" will this be unlimited?
great plugin +1
Same issue as posted by @Nex01 here.
When using PeX, you cannot give anyone more horses than set by MaxOwned, regardless of the vip settings and permissions.
@Nex01
That's definitely a PeX issue .. I'm using GroupManager and it's working as intended. I'll install PeX and see if I can't figure out what the issue is.
@raum
If I set MaxOwned to 1 everyone can only have 1 horse. no matter if they have VIP1 VIP2 or VIP3
@morlanius
Gah. That should only happen if you've got the item in your hand that lures ... DIsable luring for now, and I will post a new release in a few minutes. I gotta stop publishing late at night :/
Erm .. so I'm testing it out and cannot reproduce that. It is only luring if the required item is in hand. Post the Horse.lure section of your config, please. :)
just updated, first thing i notice, every click (right or left) is giving the message "You begin trying to lure out a horse"
@TheCoolGuy123_5_Minecraft_
Re: Nametag on any pet: What version of Stables are you using? As of 1.5, it will not look at anything that isn't a horse.
Re: Protection for Cats & Dogs isn't really something in this scope - but I could probably make it a toggleable feature, but it is not a priority right now, as I'm more concerned about making sure Horses are safe, since Dogs & Cats are a dime-a-dozen.
Re: Maxed Own permissions - I am rewriting this system so that you can define as many VIPs as you want - It will likely come in with 1.6
If you use a name tag on any pet it thinks it's a horse.
Can you fix that? It's annoying! Also, could you make the admin permissions give infinity mobs?
(I also want protection for cats/dogs, if you want to set that up too, I bet you won't do it, but maybe?)
For the config the "MaxedOwnedVIP1,2,3," could you add more to that (we can?)
(Repost 2 )
@Nex01
Hm. It might be an issue with the way the plugin is talking to PeX - wouldn't be the first time I've had this sort of issue with one of my plugins.
If you'd like to do a little bugtesting, Set Max Owned to 1 - then see how much each group can actually have by spawning horses and naming them.
As I mentioned, I will be rewriting this section of the code ... I realize that doesn't help you NOW, but it's something.
@raum
Builders should have max 2 horses, they're VIP1 then there are Donators/Premium (VIP2), they should have 5 horses. And mods should get 10 horses (VIP3) Admins/owners should get unlimited, if that is possible I had it set to:
MaxOwned: 999 MaxOwnedVIP: 2 MaxOwnedVIP2: 5 MaxOwnedVIP3: 10
and gave the permissions - stables.VIP1 to - stables.VIP3 to the specific group in the permissionsex permission file.
but its not working. owners hold max 5 horses (my friend already had 4), and Builders can hold more than 2 but theyre supposed to have 2 only ...
@Nex01
How many are the builders with VIP1 getting? (And what should it be?)
The way it handles currently - it's a bad way, but it was thrown together quickly - is it checks if you have VIP3 - if not, it checks if you have VIP2, then VIP1 - if you don't have any of those, it uses the regular 'MaxOwned'.
I'll rewrite the code for ownership numbers in an upcoming release , but in the mean time, I'll try to track down what your issue is.
I'm having a problem on 1.6.2.
The plugin works, but I can't set the correct amount of horses in PEX.
Admins/ops that have access to all existing permissions get the limit of stables.VIP2 even though I haven't set this permission for Admins.
Builders that have the stables.VIP1 permission get a even higher limit that is actually set for VIP1.
This really confuses me. Isn't there a way to exclude specific permissions?
@Kolgrath
Huh ... That shouldn't happen .. That's just a message being sent. .. there's no place for there to be an NPE... What were teh circumstances of the error, if you know?
In the mean time, you can disable the Luring option in the config for now to prevent that.