Inactive [TP] MultiHome v0.11.3 - Multiple personal named home locations [2058 / 1.2.3-R0.2]

Discussion in 'Inactive/Unsupported Plugins' started by MadManMarkAu, Apr 2, 2011.

  1. Offline

    MadManMarkAu

    MultiHome - Multiple named home locations:
    Version: v0.11.3

    This plugin is much the same as other multi-home plugins, except this plugin supports named home locations and home sharing. no longer do you need to keep a list of which home number is for what location; why not simply name the location from the start?

    When the plugin generates it's data files for the first time, it will import and convert your home locations if you use Essentials or MultipleHomes.

    To enable home-on-death, set enableHomeOnDeath, under MultiHome, in the config file to "true" and give the appropriate users the multihome.homeondeath permission.

    All test displayed to the user can be fully customized. This also allows for translations to other languages!

    Acknowledgements
    Sleaker: Too much to list here... Heaps of stuff. You rock!
    HereInPlainSight: Submitting a pull request to add PermissionsBukkit support. Also a pull request for new event system.
    Maxis010: For providing basic support in this thread.

    Donate:
    Donations help with development of this and other plugins, as well as the upkeep of our server. They're completely optional and give you that feel-good feeling we all know and love. :)

    [​IMG]

    Features:
    • Supports multi-world.
    • Multiple per-user home locations.
    • Home locations use names rather than numbers.
    • Can respawn player to their default home upon death.
    • Forwards-compatible with SimpleHome data file format. Simply replace "MultiHome/homes.txt" with the homes.txt from SimpleHome to migrate.
    • Can list and delete home locations.
    • Optional warm-up, cool-down and max-homes settings for all Permissions groups. Global settings for undefined
    • Automatically imports home locations from Essentials, MyHome and MultipleHomes data directories.
    • Can invite players to your home. Can globally invite all players to your home. Can impose a time limit on invites.
    • Every piece of text displayed to the player can be customized!

    Download: http://dev.bukkit.org/media/files/579/623/MultiHome.jar

    Source Code: https://github.com/MadManMarkAu/MultiHome

    Todo:
    • Support for custom commands.
    • User-settable option to enable/disable spawn-to-home.
    • Lockable homes.
    • Persistant, user settable HomeOnDeath option.
    • Option to store home locations in MySQL database.
    • Settable message colors.

    Bugs:
    If you encounter bugs in my plugin, open an issue on GitHub: https://github.com/MadManMarkAu/MultiHome/issues

    Commands (open)

    Commands:
    • /home - Teleport you to your default home location
    • /home <name> - Teleport to a named home location
    • /home <player>:<name> - Teleport to another players home location if you have permission or an invite is open.
    • /sethome - Set your default home location
    • /sethome <name> - Set a named home location
    • /sethome <player>:<name> - Set a home location for another player. Requires permission. Leave <name> blank to set default home.
    • /deletehome <name> - Delete named home location.
    • /deletehome <player>:<name> - Delete another player's named home location. Permission required.
    • /listhomes - List home locations for yourself.
    • /listhomes <username> - List home locations for another player. Requires permission.
    • /invitehome {<user>|*} - Invite another user (use "*" for global invite) to your default home location.
    • /invitehome {<user>|*} <home> - Invite another user (use "*" for global invite) to your named home location.
    • /invitehometimed {<user>|*} <time> - Invite another user (use "*" for global invite) to your default home for a short time.
    • /invitehometimed {<user>|*} <time> <home> - Invite another user (use "*" for global invite) to your named home for a short time.
    • /uninvitehome {<user>|*} - Retract invitation for another player to visit your default home.
    • /uninvitehome {<user>|*} <home> - Retract invitation for another player to visit your named home.
    • /listinvites - List invites open to you.
    • /listmyinvites - List invites you have open to others.
    Permissions (open)

    Permissions:
    • multihome.defaulthome.go - Allow user to teleport to their default home location.
    • multihome.defaulthome.set - Allow user to create their default home location.
    • multihome.defaulthome.invite - Allow player to invite others to their default home.
    • multihome.defaulthome.invitetimed - Allow player to invite others to their default home with a timer.
    • multihome.defaulthome.uninvite - Allow player to retract invitations to their default home.
    • multihome.namedhome.go - Allow user to teleport to a named home location.
    • multihome.namedhome.set - Allow user to create a named home location.
    • multihome.namedhome.delete - Allow user to delete a named home location.
    • multihome.namedhome.list - Allow user to list their home locations.
    • multihome.namedhome.invite - Allow player to invite others to their named home.
    • multihome.namedhome.invitetimed - Allow player to invite others to their named home with a timer.
    • multihome.namedhome.uninvite - Allow player to retract invitations to their named home.
    • multihome.othershome.go - Allow user to teleport to another player's home without invite.
    • multihome.othershome.set - Allow user to create another player's home.
    • multihome.othershome.delete - Allow user to delete another player's named home location.
    • multihome.othershome.list - Allow user to list home locations of another user.
    • multihome.free.defaulthome.go - Teleporting to default home is always free.
    • multihome.free.defaulthome.set - Setting default home is always free.
    • multihome.free.namedhome.go - Teleporting to named home is always free.
    • multihome.free.namedhome.set - Setting named home is always free.
    • multihome.free.othershome.go - Teleporting to other players home is always free.
    • multihome.listinvites.tome - Allow player to list invites open to them.
    • multihome.listinvites.toothers - Allow player to list invites they have open to others.
    • multihome.ignore.cooldown[/B] - Player will ignore the cooldown timer.
    • multihome.ignore.warmup[/B] - Player will ignore the warmup timer.
    • multihome.homeondeath - Player will be taken to their default home when respawning.
    Changelog (open)

    Version 0.11.2
    • Consolidated MultiHome and MultiHome_m commands.
    • Fixed a permissions bug.
    • Improved compatibility for Essentials.
    Version 0.11.1
    • Plugin resends target chunk to clients one second after teleporting. Might fix teleport chunk glitches.
    Version 0.11
    • Updated to latest Bukkit version.
    • Trying a fix to alleviate missing chunk glitches.
    Version 0.10
    • Fixed a typo in handling "{AMOUNT}" payment tags.
    • Added support for Bukkit permissions and SuperPerms.
    • Switched to using "Register" for economy handling.
    • Added permissions list to plugin.yml (for Bukkit perms support).
    Version 0.9.7
    • Rewrote permissions nodes.
    • Fixed permissions loading and economy loading (or lack thereof).
    Version 0.9.6
    • Merged update from Sleaker.
    • Added economy support.
    • Added PermissionsEX support.
    • Bunch of tweaks.
    Version 0.9.5
    • Updated to CraftBukkit 953
    Version 0.9.3
    • Updated to CraftBukkit 798
    • Added importing of newer Essentials home formats.
    Version 0.9.2
    • Fixed cooldowns.
    Version 0.9.1
    • Fixed typo in permissions.
    Version 0.9
    • Massive code rewrite.
    • Added invite system.
    • More permissions.
    • Lots of stuff, some large, some small.
    Version 0.8
    • Optional home-on-death. Players can teleport back home rather than to spawn when dead.
    Version 0.7
    • Imports home locations from Essentials and MultipleHomes.
    Version 0.6.2
    • Fixed a bug where plugin wasn't honoring groups correctly.
    Version 0.6.1
    • Fixed unnecesary warp scheduling when warmup time = 0
    Version 0.6
    • Updated to CraftBukkit 670
    • Implemented new config file.
    • Per-group warm-up, cool-down and max-homes settings.
    • Split create and teleport permissions.
    Version 0.5.2
    • Fixed a bug to do with MultiHome loading before MultiVerse and removing all home locations.
    Version 0.5.1
    • Fixed listing homes when no homes set.
    Version 0.5
    • Added /listhomes and /deletehome
    Version 0.4
    • Added support for Permissions/FakePermissions
    Version 0.3
    • Homing from another world will now teleport between worlds before teleporting to home. Fixes a server bug when changing worlds and locations simultaneously.
    Version 0.1-0.2
    • I honnestly can't remember... Released, I guess?
     
  2. Offline

    monir

    Does it work for 1.8?
     
  3. Offline

    RaymanMaik

    I think the permission-nodes are wrong, because only the admins can do anything (PEX)
     
  4. Offline

    tom

    Please support PEX.
     
  5. Offline

    Darq

    Using PEX 1.14 and this is working just find on Build 1185.
     
  6. Offline

    recon88 Retired Staff

    Is it possible to set 1 home per world?
     
  7. Offline

    fragger505

  8. Offline

    recon88 Retired Staff

  9. Offline

    MadManMarkAu

    I'm still here, will do this tomorrow. Ran out of time last weekend.
     
    recon88 and Darq like this.
  10. Offline

    fragger505

    @MadManMarkAu

    I love your plugin and here are a couple of suggestions.
    •Change how timers, homes, and costs are managed within permissions. I provided an example of how it could work.
    •Add native bukkit permissions (SuperPerms or whatever they are calling it). I understand this contradicts my example I provided in the first suggestion as it is formatted to permissions 3.x
    •Support MySQL for storing home locations. =3

    This is mimicking a feature within MyHomes by Spathizilla on managing variable setting on how timers, homes, and costs are managed. It is kind of long so I put it inside a spoiler
    Show Spoiler

    Here is an example of what it would look like in your standard multihome config file.
    Code:
    member:
        warmup: 3
        cooldown: 60
        maxhomes: 2
        disruptwarmup: 1
        sethomecost: 0
        setnamedhomecost: 0
        homecost: 0
        namedhomecost: 0
        othershomecost: 0
    senior:
        warmup: 0
        cooldown: 0
        maxhomes: 5
        disruptwarmup: 0
        sethomecost: 0
        setnamedhomecost: 0
        homecost: 0
        namedhomecost: 0
        othershomecost: 0
    
    The same configuration options would read like this within permission's group config file.
    Code:
    groups:
        member:
            default: true
            info:
                prefix: ''
                suffix: ''
                build: true
                multihome:
                    timer:
                      warmup: 3
                      cooldown: 60
                    homes:
                      maxhomes: 2
                    costs:
                      sethomecost: 0
                      setnamedhomecost: 0
                      homecost: 0
                      namedhomecost: 0
                      othershomecost: 0
            permissions:
                - 'foo.bar'
    groups:
        member:
            default: true
            info:
                prefix: ''
                suffix: ''
                build: true
                multihome:
                    timer:
                      warmup: 0
                      cooldown: 0
                    homes:
                      maxhomes: 5
                    costs:
                      sethomecost: 0
                      setnamedhomecost: 0
                      homecost: 0
                      namedhomecost: 0
                      othershomecost: 0
            permissions:
                - 'foo.bar'
    
    Or like this within permission's user config file.
    >Notice the difference between the senior members. Derpina inherits the standard values from the group config file, but Hipster donated money to gain access to unlimited homes so without having to create a whole new group for one member to gain additional homes it is added within his personal user settings. Therefore user settings will need to take priority over group settings.
    Code:
    users:
        Herpina:
            info:
            groups:
                - member
            permissions:
        Derpina:
            info:
            groups:
                - senior
            permissions:
        Hipster:
            info:
                multihome:
                    timer:
                      warmup: 0
                      cooldown: 0
                    homes:
                      maxhomes: -1
                    costs:
                      sethomecost: 0
                      setnamedhomecost: 0
                      homecost: 0
                      namedhomecost: 0
                      othershomecost: 0
            groups:
                - senior
            permissions:
    


    Hope all of this makes sense. Thanks for reading and pardon me for any spelling/grammar errors. ^^
     
  11. Offline

    MadManMarkAu

    New update. Check changelog for details.
     
    Saidy99 and Darq like this.
  12. Offline

    Saidy99

    Okay so I got the version with PermissionsBukkit support since that's what I use, but putting the nodes into the permissions file does not grant the permissions. Only ops have access to the commands o-o explain a little of how to set it up for PermissionsBukkit please?
     
  13. Offline

    tom

    Testing with PEX
     
  14. Offline

    childersc

    This is not working with PEX 1.14, Build #1185 and MultiHome 0.10

    No matter what I do with the permissions nodes, they simply will no longer work!

    The issue doesn't seem to be with PEX...

    The issue, as I have found it, is with Essentials.

    Since essentials already had a /sethome option, it seemed to take preference over Multihome's /sethome

    My fix was simply to add essentials.sethome to my permissions list... I cannot seem to download the M jar file to rename these.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 13, 2016
  15. Offline

    ChromWolf

    EXCELLENT plugin, been using it for quite a while, but I do have two issues. I'm running Bukkit 1185/MultiHome 0.9.7/PermissionsEX 1.14 on my test server.

    While it sees the previous list of homes when using /listhomes, using the /home <homename> command reports "A home for the given player does not exist." I seem to be able to create new homes, and can then /home to them, but previous homes seem unavailable except for the /listhomes command.

    Also, I too am getting the "chunk containing home location not loaded, all other surrounding chunks are" issue. As an admin running various sk98 plugins, using the compass to //jumpto a solid block one chunk over seems okay. If it helps, I curiously seem to take falling damage when doing so, but that may just be expected behavior for a chunk not loading correctly. Manually traveling to the chunk in question, or using other TP mods, seems to load the chunk fine. It's possible this might be distance based (i.e. not as likely when not traveling as far). Sometimes, it *does* load the chunk (in that I can interact with stuff), but for example, it rains through the ceiling. Traveling out of range of the chunk and returning (such that the chunk is unloaded and then reloaded into memory) seems to correct this issue as well.

    No console errors are produced for either issue.

    Hope this is helpful, let me know if there's any other information I can provide that would be helpful!

    EDIT: If this is helpful to anyone else, I do NOT have Essentials loaded, we dumped that a while ago in favor of CommandBook (and the other sk98 plugins).

    EDIT #2: I recall seeing that indoor rain was either a Bukkit issue, or one of Minecraft itself, but felt it was still pertinent since the indoor rain disappeared with a distance-invoked chunk reload.
     
  16. Offline

    MadManMarkAu

  17. Offline

    childersc

    Thanks,

    If you need yet another mirror for it, I can gladly host it as well :)
     
  18. Offline

    tom

    PEX does not work with this.
     
  19. Offline

    fatmarley

    Hey @MadManMarkAu I'm using your multihomes with the extra m!! so all my commands are mlisthomes etc...
    Well I was trying to delete another players home (as op) and neither /mdeletehome P N or /deletehome P N were working.

    I was hoping you could just double check those commands, or enlighten me on what I have done wrong.

    @tom i use PEX, no issues at all.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 13, 2016
  20. Offline

    fragger505

    If by some reason you prefer to not have to use the "m" prefix, you can open up your Essentials.jar with a archive manager such as WinRAR or 7zip, and then comment out the commands for home, sethome, & delhome in the plugin.yml file.

    I'll provide a file if my explanation was bad.

    I assume /mdeletehome P N is referring to the command /mdeletehome <player>:<name>.
    If so, be sure you are using a colon to separate the username from the home name.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 13, 2016
    MadManMarkAu likes this.
  21. Offline

    erickingsr

    MadManMarkAu,

    Thank you for the update, much appreciated :)

    Best regards,
    Eric - CKM
     
  22. Offline

    Backfire

    Having a similar issue on my server, anyone got a solution?
     
  23. Offline

    Lildirt

    Is "PermissionsBukkit" supported with this? :)


    EDIT: Yes it is. Sorry. I didn't see it in the post.
     
  24. Offline

    ChromWolf

    Found out what Issue #1 was; apparently, we grabbed a copy of CommandBook that included the home functionality, and because it's commands were the same as MultiHome, it was overriding it. XD First-hand experience for why "mhome" was developed. We've re-downloaded CommandBook sans Home functionality to correct the issue.

    That said, we are still (as are others I believe) having the chunk loading issue. It was not present for CommandBook homes and, I hate to say it, we'd have just switched to CommandBook if it supported listing of homes. I know it's totally bad form to ask for updates, and I apologize, but... do we know what's causing this, and is a fix in the works?
     
  25. Offline

    Saidy99

    Can you get this to override Essentials commands? I don't like having to tell everyone to put an m before each command lol
     
  26. Offline

    ChromWolf

  27. Offline

    spunkiie

    still buggy with players getting stalled on black holes when teleporting home.

    btw: 0.9.3 doesn't have the bug, so we are still using it :(
     
  28. Offline

    ChromWolf

    I'd LOVE to switch to 0.9.3 so we can have working homes, but we've switched to PEX, and according to the changelog, PEX support wasn't implemented until 0.9.6... I suppose I could try to get it linking in with the dummy Permissions plugin included with PEX, but with all the other plugins I still need to update, I'd much rather see a working MultiHome....

    That said, I can't seem to find any list of earlier versions of MultiHome. I'd love to try 0.9.6 to see if the chunk issue is present there (it *is* present in 0.9.7, which is what we're running on our live server, though it seems exasperated in 0.10), but as I say, I can't seem to find it anywhere on @MadManMarkAu 's github.
     
  29. Offline

    spunkiie

    Is just funny how @MadManMarkAu simple ignores the users bug report. lol

    THAT FUCKIN' PLUGIN HAS A NASTY BUG SINCE VERSION 0.9.3 THAT SOMETIMES (VERY OFTEN) THE PLAYER WHEN TELEPORTING HOME WILL FALL INTO A BLACK HOLE. WAKE FUCKIN' UP MAN, IF YOU AREN'T GOING TO MAKE DECENT CODE/LISTEN TO USERS, IS BETTER TO SHUT THIS THREAD AND CLAIM THIS PLUGIN DEAD.
     
  30. THAT'S AWESOME. I JUST RELOG. BECAUSE. Y'KNOW. THE PLUGIN WORKS FINE OTHERWISE. ARE YOU FALLING INTO VALERIA'S DOOM? BECAUSE OTHER PEOPLE SAY YOU GET STALLED OUT ON THE VOID.

    Oh. Yeah. And http://forums.bukkit.org/threads/fi...a-lag-hole-request-a-chunk-resend-1060.19232/ . Pray, don't post in all caps, and go look for solutions to problems rather than complain about them. I'm sure MMMA will get to it when he can. In the mean time, you're not helping by flailing your arms like an entitled child. I don't see 'plugin dev' by your name to indicate you can even tell 'decent' code. Though if you are a code guru? Go find the error and just do a pull request. It behooves you to be at the least polite to plugin authors who do these things in their spare time for others benefit with no monetary gains for themselves.
     
  31. Offline

    spunkiie

    @HereInPlainSight

    stfu. you are so lame that you think ppl need to have a "plugin dev" tag to say something is broken/doesn't work well.
     

Share This Page