A bunch of ideas #14


  • Enhancment
  • Accepted
Open
  • _ForgeUser10299688 created this issue Aug 5, 2013

    This is a list of ideas I had for improving the plugin. None of them are necessarily related to each other, but I decided to put them all in one ticket for the sake of convenience, hence the ticket's name. I'll write out each idea in a list form.

    1. A more LWC-like approach to locking horses.

    • For example, having public and private horses.
    • Public horses cannot be claimed or locked by anyone, but they can be ridden by anyone. Their inventory can also be opened by anyone, should they have one.
    • Private horses also cannot be claimed or locked by anyone. However, unlike public horses, they cannot be ridden upon or accessed by anyone, unless they have permissions to do so.
    • An "addowner/removeowner" command, to remove or add owners, of course. Each owner has equal access to the horse itself, so any one owner can kill the horse, or access its inventory, or etc. The "setowner" command would throw out the entire list of owners and set the owner to whatever name was specified.
    • An "addfriend/removefriend" command. Works similarly to "addowner/removeowner", except that "friends" can only ride the horse. They cannot do anything else to it.
    • A flag, used in conjunction with "addfriend/removefriend" to specify whether a "friend" can also access the horse's/mule's inventory.
    • Leads should receive the same protections that the horse it's connected to has. As if it were a part of the horse.

    2. A "stay" command for horses, like "/myhorse stay". Let's face it, not all of us want to use a fencepost and a lead to make our horses stay still everywhere we go.

    3. "/myhorse list" should also show each horse's coordinates.

    • Or you could include a "/myhorse whereis <id>" command. Or both features.

    4. Having your horse teleport with you when you teleport via another plugin.

    5. Horse invulnerability being a flag that can be applied to certain horses.

    • You could also include specific invulnerability flags, like being invulnerable only to fall damage, or something like that.
  • _ForgeUser10299688 added the tags New Enhancment Aug 5, 2013
  • Forge_User_09714816 posted a comment Aug 6, 2013

    Thanks for the ideas!
    I think that a "mh setpublic" command would be next on the list.

    After that, probably lead protection.

    You can set your damage protections as you wish in the config since version 0.1.0

    The addfriend features are already implemented since 0.0.9 but I have not advertised it too much since I have not tested it deeply enough yet.


    Edited Aug 6, 2013
  • Forge_User_09714816 removed a tag New Aug 6, 2013
  • Forge_User_09714816 added a tag Accepted Aug 6, 2013
  • _ForgeUser10299688 posted a comment Aug 7, 2013

    For damage protections, I already know that you can set it in the config with v0.1.0; I meant damage protection flags. For example, you can set one horse to be impervious to lava while the rest aren't.

    You could probably use this feature to create horses designed for minigames, such as a race track surrounded by lava where falling it won't kill the horse (just slow you down), or an arena with skeletons that are supposed to damage the player and not the horse.

    Also, thanks for considering these ideas. Really appreciate it. :)

  • RuiNtD posted a comment Aug 15, 2013

    Is it possible for a plugin to hook into LWC and set an entity as lockable? That would probably make thing easier. Just be sure not to "Please left click your [horse] to lock it."


    Edited Aug 15, 2013

To post a comment, please login or register a new account.