ZHorse
ZHorse's job is to provide an enhanced management of horses in Minecraft. It ranges from giving custom names to your horses to teleporting them if you happen to lose one. This plugin is highly customizable since you can edit any word showing up in the chat and define how ZHorse should work by editing the config.
- Claim any wild horse, donkey, mule or llama.
- Spawn horses with custom appearance and statistics.
- Name, rename and edit at will your claimed horses.
- Watch your horses names take the color of your permission group.
- Exchange your horses with other players...
- Or put them up for sale !
- Protect your horses against a customizable list of damages.
- Lock your horses to prevent any theft attempt...
- But share them with your friends !
- Teleport your horses to you, or yourself to your horses.
- Send them back to their stable.
- Resurrect them with their full inventory.
- Set you preferred language and horse.
- Store your data with MySQL or SQLite.
- Go through the list of commands to discover all the features !
- Spigot 1.14.x
- Vault 1.7.x
- Java 8
- (MySQL 5.7+)
- Check the To Do list on GitHub !
- Take a look at the Config, Locales (EN, FR, DE, NL, ES, HU, PL, CN) or the Tips and tricks page if you encounter any difficulty !
- Feel free to suggest me your ideas or report your bugs via a new issue on GitHub !
- Please note that English is not my native language, so let me know if I wrote something weird in this page or anywhere else ;)
@Z3dd7
I reloaded it both serverwise and stop-start. but you might address a valid point. I am using a spigot 1.8.1 SNAPSHOT version. I will try an older version to see if it works! Thanks!
Edit: Nope, this is on every version for me.
@IIsnickerII
Hi, unfortunately I won't be able to work on this issue until friday.
In the meantime, could you tell me if you are using CB/Spigot 1.8.3 + ZHorse 1.2.2 ?
And by "reload", do you mean "/zh reload" (zhorse), "/reload" (server) or "/stop" (server) ?
Config file gets rewritten to default after every reaload. Please fix this :). Great plugin whatsoever!
@LegendaryAdmin
When an issue like this occurs, the safest option is to use /zh tp instead of /zh here.
There are not many events able to make ZHorse delete an horse from users.yml, but death is one of them. I had this issue once, and it occured because one of my plugins was deleting animals close of each others...
The simpliest way to (try to) fix this is that I check this myself on your sever ;)
@Z3dd7
Sweet, thanks!
New issue popped up tonight though. After the server restart, all horses were gone from their pens and we could not summon them >.<
Log: http://paste.ubuntu.com/10157506/
@LegendaryAdmin
Snapshot 5 is done and your color issue should be fixed.
You can now use color codes like '<4>', 'ยง4', '<dark_red>', '<darkred>', 'dark_red', 'darkred' or even 'DarKReD' instead of 'DARK_RED' in the Group section of your ZHorse's config ;)
@LegendaryAdmin
I still need to rework group colors for 1.2.0 release anyway. When it's done I'll mp you the snapshot 5 ;)
Concerning your screenshot, this is not a bug : just remove "-t DragonZsBallz" from your command to teleport your horse of id 1 to you.
If you execute /zh here -t DragonZsBallz -i 1 (-a), it tries to teleport the horse of id 1 of the player DragonZsBallz to you :p
-t playerName is used to manage other players horses, or execute commands on them (like /zh give -t DragonZsBallz = give the horse I am mouting to DragonZsBallz)
Now that we can claim horses, we cannot tp them to us:
screenshot: http://gyazo.com/dbf1677bc60e73ac4bfe23f00395e1e0
log: http://paste.ubuntu.com/10082741/
Also, the colors do not seem to be working for the names. I am using AQUA, GOLD, DARK_PURPLE, RED, and MAGIC.
@Z3dd7
That worked out, thank you!
@LegendaryAdmin
With snapshot 4, your issue might finally be fixed :p
I am not 100% sure that your issue is connected to this, but ZHorse was case sensitive regarding groups. It is not anymore, so you can belong to the group leGEnD according to Vault, and still define a maxClaims limit for the group LegeNd in ZHorse's config.
So, this is what you have to do now :
@Z3dd7
omg, I forgot to paste in the console log, sorry... here you go:
http://paste.ubuntu.com/10069562/
And the users.yml:
http://paste.ubuntu.com/10069576/
@LegendaryAdmin
Yes this is what I think :/
Still, I will need you tu run the latest debug snapshot, execute /zh claim and copy paste the result here in order to find the best way to debug this (maybe with permissions) :)
wasn't able to run to work on this yesterday, here is the latest:
http://paste.ubuntu.com/10060779/
My suspicion is, that it is not recognizing the groups. And even though I am op, it is not recognizing my status >.<
@LegendaryAdmin
Here is the 1.2.0 snapshot 3 debug 3.
I added debug messages about max claims and I think I have an idea of where your issue come from.
Try it just like before, but send me your users.yml too.
@LegendaryAdmin
Ok so this is the maxclaims that is involved. Il will add a ton of debug messages on the concerned methods in 7-8 hours and upload the debug 3 snapshot asap.
EDIT : I will do that tomorrow. I had a lot to do on my own server tonight, and I am too tired to work on ZHorse right now.
It seems as though there was a bit of a language barrier between us. It sounded to me like the 2.0 snapshot was the debug, I was so confused lol. The latest upload has provided the debug info here:
http://paste.ubuntu.com/10009283/
This is the config:
http://paste.ubuntu.com/10009355/
I am of course OP, so that is a bit strange...
@LegendaryAdmin
As I said this isn't a debug version, just a 1.2.0 snapshot so we'll work on the same version when I add the debug messages :p
EDIT : Here is the debug version (linked with this comment)
Just to be on the safe side, save any ZHorse's file you'd want to keep, then delete everything related to ZHorse (plugins/ZHorse<any_version>.jar AND plugin/ZHorse)
Now you can
Feel free to use the chat room (http://www.e-chat.co/room/55662) after that !
@Z3dd7
I took another stab at it today, I deleted the language files, tried /zh claim, I have deleted them and then /zh reload-then tried /zh claim. I have renamed them and done the same thing, I have deleted the entire config and tried the same steps. Something is just not right. I have followed your instructions step by step and tried every possible variation of renaming/deleting/reloading/not reloading of each file separately and it is not working =[ I am receiving no debug information in my logs or on my console...
@LegendaryAdmin
In order to have a chance to make this snapshot work, you have to delete/rename locale_EN.yml and locale_FR.yml.
This won't fix you issue but this will make you ready for the debugging snapshot ;)
Thanks for working with me on this. Bad news though, after I received your message, I renamed the files, ran reload-it generated the new configs, and I am still not receiving any debug information =[
http://paste.ubuntu.com/9975001/
I will be back in 6 or 7 hours to work on this some more. Maybe I can catch you then!