Horses
Description:
Horses is a Virtual Stable Management system which allows players to buy, store and summon horses. Horses will provide you, the server owner, the ability to create a mmorpg style mount and stable system.Features:
- Yaml or MySQL Data storage
- Powerful configuration system. Setup special configs for different worlds/permissions
- Buy horses via a command
- Customisable starting HP per Horse type
- Keep your horses safe from other players
- Rename your horses (With colours!!)
- Swap out your horse for another in your virtual stable
- Anti-grief protection for players horse
- Collect and store horses in your virtual stable
- Horses can be bought by breed type
- Allow tamed wild horses to be added to your virtual stable
- Customise what happens when horses are hurt. (Ignore damage?, Transfer to rider?)
Planned Features:
- Buy health for your horse
Commands:
- /horses help [command] Lists information about sub-commands
- /horses buy <Name> <Breed Type> Buys a horse of the given breed
- /horses delete <Name> Deletes the given horse from your virtual stable v0.4.0
- /horses types Lists the horse types the player has permission to use
- /horses summon <Name> Summons one of the players horses to them
- /horses dismiss Dismisses the summoned horse
- /horses heal [Amount] Heals the players active horse (For a configurable price)
- /horses rename <Name> <NewName> Renames one of the players horses
- /horses list [Player] Lists all the players horses
- /horses give <player> <name> <type> Gives a player a horse Since v1.1.9
- /horses reload Reloads the configuration
Permissions:
- horses.set.user Grants the player permission to use all player sub commands
- horses.set.admin Grants the player permission to use all admin sub commands
- horses.command.buy Grants permission to use /horses buy
- horses.command.delete Grants permission to use /horses delete
- horses.command.summon Grants permission to use /horses summon
- horses.command.dismiss Grants permission to use /horses dismiss
- horses.command.heal Grants permission to use /horses heal
- horses.command.rename Grants permission to use /horses renamed
- horses.command.list Grants permission to use /horses list
- horses.command.types Grants permission to use /horses types
- horses.command.list.all Grants permission to list other players horses
- horses.command.reload Grants permission to reload horses config
- horses.command.give Grants permission to use /horses give
- horses.type.<HorseType> Grants permission to buy the given horse types
- horses.colour Grants permission to use & colours codes in your horses name
- horses.formattingcodes Grants permission to use & formatting codes in your horses name
Configuration:
- TODO
Stats collection:
Horses collects anonymous stats from your server such as player count, version numbers for horses and CraftBukkit also which type of database you are using. All data is sent to MCStats.org and is publicly viewable. You can disable Stats collection by going to plugins/PluginMetrics/config.yml and change opt-oit to true.Developer Builds
Development builds of this project can be acquired at the provided continuous integration server.These builds have not been approved by the BukkitDev staff. Use them at your own risk.
Dev Builds
Configuration | Translations | Statistics | ChangeLog | Videos
-
View User Profile
-
Send Message
Posted Jul 25, 2013@ShadowDog007
I believe I had maxhorse set to 0, and they could still claim horses, ill update to v1.1.0+ later tonight and see if i can prevent this exploit, ill let you know the results.
-
View User Profile
-
Send Message
Posted Jul 25, 2013@jakenem12
Sorry, that was not clear when I read your last comment.
You can set maxHorses to 0 in the creative world so they can't claim horses there. Else if your using v1.1.0+ you can create a separate stable group in the creative world to separate survival/creative horses.
-
View User Profile
-
Send Message
Posted Jul 25, 2013@ShadowDog007
Like i said, my issue is not regarding the summoning of the horses. Because i neglected the supper perm horses.* players cannot summon or run any other horses related commands, but they can still claim new horses, regardless if i deny the claiming of wild horses with name tags, in the creative worlds config. So in a way i guess im asking for a horses.claim permission node, which makes users not be able to claim a wild horse if that node is neglected.
-
View User Profile
-
Send Message
Posted Jul 25, 2013@MinecraftAllen
Yep, I got this planned. Not sure when I will get it done.
@Mintaru
What do you mean? Right click with a name tag and wild horses will be moved into your virtual stable.
You have to enable it in the config though.
-
View User Profile
-
Send Message
Posted Jul 25, 2013how do you put tame horses in your virtual stable?
-
View User Profile
-
Send Message
Posted Jul 25, 2013Would it be possible to add a feature to define regions where horses are not allowed? Like have them despawn when the horse enters the region
-
View User Profile
-
Send Message
Posted Jul 25, 2013@conflictxinside
Ahh, you would have not updated the settings from the last version. I moved some stuff around in the config.
@jakenem12
You should deny the permissions for summoning. horses.command.summon
Also, in the latest build you can disable certain commands from the config (So disable the summon command via your creative config)
@Dstates4
Right click with a named name tag. Just like as you would when you name a horse.
@Silial
No idea why you are just seeing this. I haven't changed permissions.
@Silial
It doesn't say you have to grant them, it just states what they are. Its so much easier just defaulting on basic permissions.
You can remove the 'default' by denying horses.set.user
-
View User Profile
-
Send Message
Posted Jul 24, 2013@midnightfang22
Ahh... Strange awkward way to do it, when the plugin states otherwise, with a permission node specifically stating "To Grant"
Thank you for your help.
-
View User Profile
-
Send Message
Posted Jul 24, 2013@Silial
They are granted permission to buy all horses by default. To deny players from a horse, you NEGATE the permission.
-
View User Profile
-
Send Message
Posted Jul 24, 2013It seems in your latest update, that the horse permission nodes do not work. Currently my players have the following. - horses.type.donkey - horses.type.mule - horses.type.gray - horses.type.black - horses.type.brown - horses.type.chestnut - horses.type.creamy - horses.type.white However, despite this they can all buy the Undead and Skeleton mounts. I am using Permissions EX, 1.19.6, and the fact that it is currently 1.5 shouldn't influence it's recognition of command usage.
-
View User Profile
-
Send Message
Posted Jul 24, 2013@ShadowDog007
I went to go paste my config file and in doing so found my problem. When I updated the plugin didn't update the configs settings, It appended the settings at the end of the file. Here is the file is you are still curios. http://pastebin.com/SJmiDFjk. Thanks for the great plugin!
-
View User Profile
-
Send Message
Posted Jul 24, 2013Just wondering I see that in planned features you removed store wild horses tamed into virtual stable how do I do that? /horses dismiss or what?
-
View User Profile
-
Send Message
Posted Jul 24, 2013Hello, i seem to have a problem.
Currently my users can claim a horse in our creative world, as i cannot find away to prevent them from claiming wild horses, via nametags. I have neglected the horses.* permission in that world, to prevent them from summoning horses(and other commands), and that works fine. But users can still claim wild horses with name tags... I have created a separate config for my creative world and disabled the ability to claim with nametags, however they can still claim horses with name tags. This is a very Serious exploit, im glad i found it before it was exploited on my server. PS here are my Configs if its helps... Main config: http://pastebin.com/PPFVz6ms Creative World Config: http://pastebin.com/sJZb7LMK
-
View User Profile
-
Send Message
Posted Jul 24, 2013@ShadowDog007
Yes, I have the latest version of Vault and your plugin. Still charges only 10 coins for any type. Config file prices are completely ignored.
Deleting the config.yml, restarting, and re-configuring the prices a second time fixed it.
-
View User Profile
-
Send Message
Posted Jul 24, 2013@midnightfang22
That was a mistake on my part, I just put the nodes below it in the wrong place. Have it fixed for the next build.
@judgmentrealm
That should work fine D: I will test it myself tomorrow if I get the chance.
fyi, horses.set.user is set by default so you don't need to add it to your permissions file.
@SpookyPirate
Post your config on pastebin please? (Change the delay to 0 then post it, don't let Horses reset it)
-
View User Profile
-
Send Message
Posted Jul 24, 2013In the latest dev build the custom summon delay time doesn't seem to be working anymore. I had it to zero but now it defaults back to 10 seconds no matter what I set it to.
-
View User Profile
-
Send Message
Posted Jul 23, 2013@midnightfang22
I changed the commands to their desired true/false state. I only have created a separate config for the creative world, and not the main world, as I assume the main world follows the main config since a separate one has not been defined. That being said, I have the heal command and buy command disabled in both configs, however, the summon command is only available in the main world, but set to false in the creative world. After reloading the plugin and testing it out, horses can still be summoned in both worlds. Here is a paste of the Main Horses Config, the horses config for the creative world, as well as a small part in my PEX file. [EDIT] I did try negating the summon permissions in the creative world earlier, however horses could still be summoned.
http://pastie.org/8169815
-
View User Profile
-
Send Message
Posted Jul 23, 2013@judgmentrealm
just change the true/false options below that. I'm not sure about the Commands: {} actually.
-
View User Profile
-
Send Message
Posted Jul 23, 2013@midnightfang22 I installed the newest dev build, and i see the changes made to both the world and regular configs. I am not sure how to properly configure the blocking of a command. In the world config (world is called "Plotworld"), how do I set up:
Commands: {}
So that it denies the summoning of horses in that world.
-
View User Profile
-
Send Message
Posted Jul 23, 2013@judgmentrealm
It would be easier with the newest dev build in the link above the comments. There are now options in there to allow/deny commands in a world config. On the other hand, you can just negate/deny the permission to use the summon command in the creative world with a permissions plugin.