LivestockLock
LivestockLock
Livestock Lock lets players 'claim' animals so that no other players may damage or otherwise interact with them. Players can keep a list of other trusted players that are allowed to use their animals, and limits can be placed on how many animals a player can claim based on group memberships.
Features
- protect animals from theft, and damage
- configurable costs in money, XP or items for each type of animal
- any living entity can be configured as a claimable type.
- Players can 'trust' other players with their animals
Commands
All commands are under the main /livestocklock
or /lsl
command
/lsl claim [<player>]
- enter this comand and right click on an animal to claim it. players with livestocklock.claimforothers can use the option player argument to claim an animal for another player./lsl abandon
enter this command and right click an animal to un-claim or abandon it. the animal will lose all protection and can then be claimed by another player./lsl addplayer <player>
- trust <player> to interact with your animals./lsl removeplayer <player>
- stop trusting <player> to interact with your animals./lsl list
- list your animals and trusted friends./lsl ignoreclaims
- override claim permissions (for staff use)
Permissions
- livestocklock.use - this permission is required to make use of any of the
/livestocklock
commands. - livestocklock.commands.* - allows access to ALL
/livestocklock
commands. - livestocklock.commands.claim - allows usage of
/lsl claim
- livestocklock.commands.abandon - allows usage of
/lsl abandon
- livestocklock.commands.addplayer - allows usage of
/lsl addplayer
- livestocklock.commands.removeplayer - allows usage of
/lsl removeplayer
- livestocklock.commands.list - allows usage of
/lsl list
- livestocklock.commands.ignoreclaims - allows usage of
/lsl ignoreclaims
- livestocklock.claimforothers - allows a player to claim an animal for another player using
/lsl claim <player>
- livestocklock.claim.<entityId> - allows claiming of the specified entity type by its numeric id.
Source Code & Development Builds
Source code is available on Github
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.
What should I do about:
[21:23:29] [Server thread/ERROR]: Could not pass event PlayerInteractEntityEvent to LivestockLock v0.0.7 org.bukkit.event.EventException at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:320) [craftbukkit.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) [craftbukkit.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:486) [craftbukkit.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:471) [craftbukkit.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at net.minecraft.server.v1_7_R1.PlayerConnection.a(PlayerConnection.java:1068) [craftbukkit.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at net.minecraft.server.v1_7_R1.PacketPlayInUseEntity.a(SourceFile:55) [craftbukkit.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at net.minecraft.server.v1_7_R1.PacketPlayInUseEntity.handle(SourceFile:10) [craftbukkit.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at net.minecraft.server.v1_7_R1.NetworkManager.a(NetworkManager.java:146) [craftbukkit.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at net.minecraft.server.v1_7_R1.ServerConnection.c(SourceFile:134) [craftbukkit.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at net.minecraft.server.v1_7_R1.MinecraftServer.u(MinecraftServer.java:655) [craftbukkit.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at net.minecraft.server.v1_7_R1.DedicatedServer.u(DedicatedServer.java:250) [craftbukkit.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at net.minecraft.server.v1_7_R1.MinecraftServer.t(MinecraftServer.java:545) [craftbukkit.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at net.minecraft.server.v1_7_R1.MinecraftServer.run(MinecraftServer.java:457) [craftbukkit.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] at net.minecraft.server.v1_7_R1.ThreadServerApplication.run(SourceFile:617) [craftbukkit.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] Caused by: java.lang.IndexOutOfBoundsException: Index: 0 at java.util.Collections$EmptyList.get(Unknown Source) [?:1.7.0_01] at com.norcode.bukkit.livestocklock.EntityListener.onPlayerInteractEntity(EntityListener.java:132) [?:?] at sun.reflect.GeneratedMethodAccessor272.invoke(Unknown Source) [?:?] at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) [?:1.7.0_01] at java.lang.reflect.Method.invoke(Unknown Source) [?:1.7.0_01] at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:318) [craftbukkit.jar:git-Bukkit-1.7.2-R0.3-b3020jnks] ... 13 more
Having a problem with the latest dev build, #34, and every build previous actually. Every time I try to ride a horse I have claimed it disappears. No console errors, nothing in logs.. just poof
@nicktehbrick
not at present, the animals could be in unloaded chunks so the plugin would have to track its current location at all times, it may not be very accurate or efficient, but I can look into adding it as an option in the future.
Any way to keep track of animal locations with lsl?
For example, doing /lsl list would give:
horse - 345 65 123
horse - 344 65 125
cow - 13 55 34
@Le6barbare
Thanks for the feedback. I think i finally fixed the issue with the leads, it's available in the latest dev builds. I've been trying to track down the error you pasted too, but I haven't had any luck yet. seems like it couldn't find one of your animals or something :\ I'll keep investigating.
Hello !
I have tested the 0.0.8 dev build, there is no more error in the console, but the lead disappear when I right click on an wild animal, and come back when I make a second right click.
after that, I can use the lead on my tamed animal normally.
Your plugin is great ;)
Sorry for my bad english, I hope this can help you for debug ^^"
PS: For the /lsl list, why not display it like this :
"- 5 cow(s)
- 2 pig(s)"
?
PS2: There is also this bug I don't understand : http://pastebin.com/rNYi0Fyy
@cyberze
It doesnt show any more errors so i assume it is fixed already :D btw great work and id say ur one of the best devs around here with ur approach to community :D
i ask the mod that found it to test it again ;d
@cyberze
there's a 0.0.8 development build on jenkins, use the link above.
I haven't published it here because I haven't had a chance to test it yet. if you can let me know whether or not it fixes your problem, I'll publish the fix here. Otherwise I'll test it as soon as I have a chance.
@cyberze
This is a bug w/ the new auto-claim-on-leash functionality. Will release a fix today.
https://pastee.org/y6egz does this have any to do with this plugin or is it related to some other?
@LGCMcLovin
there were 2 issues fixed since the 1.5.2 release.
first, normal players didn't recieve 'livestocklock.claim.*' by default, so you have to assign it to your default permission group to allow people to claim animals.
second, you'll have to give the individual command permissions, since they were changed as well.
livestocklock.command.claim livestocklock.command.abandon livestocklock.command.addplayer livestocklock.command.removeplayer livestocklock.command.list
@metalhedd
could you tell us what the permissions node bug was so taht 1.5.2 users can use the permissions for their players.... ive installed this plugin and for me it works great, but my players with permissions, still cant use the commands
thanks
@elyssah
Yep, I'll add it in the next release
Loving the new expiration! Another suggestion, can you build into the Nametag item the claim command, so that when a player uses the nametag on an animal, it claims it for them, and won't allow them to use more nametags if they can't claim more.
made a ticket, no idea if its just me or common stuff
@metalhedd
The latest Development build (0.0.6-SNAPSHOT) has the expiry options.
@elyssah
I'll add this in the next version.
Just a quick question on this.. is there a way to make it so that if a player doesn't tend to his animals after so many days they lose their claim or "run away" (despawn)?
@metalhedd
Would it be possible to add a perm that would limit how many claims a user or group can have? Like livestock.amount.5 would allow a user to only claim 5 total.
Thanks for this plugin.
Edit - NM I see you have this option in the config :) I missed it at first glance. Implementing this on our servers now :)