uHome
uHome - The Ultimate Multi-Home Plugin
Is teleporting to your homes making you suffocate? Having trouble getting in and out of minecarts? Update to v1.5.3 and set loadChunks: true in your uHome config.yml!
Introduction
uHome is a fork of the wonderful MyHome plugin by tkelly and spathizilla, modified to provide multiple homes to players that are simple to use and easy for server operators to control. Developed for use on my server, Ultimate Minecraft, some features have been removed that were previously available in MyHome, namely publicizing of homes and economy support, which were removed as they were not needed on the server. Currently, economy support is implemented in v1.5a and above, and will be available in release versions shortly.
Version Support
uHome 1.5.3 is known to be compatible with all releases of CraftBukkit 1.4.7.
Feature Summary
- Creation of multiple private homes (warps) for each player.
- Bukkit SuperPerms support, including permissions variables.
- Works out of the box without config changes and no permissions plugin necessary
- Home creation limit, with support for different levels through permissions nodes.
- Command cool-downs and warm-ups, also variable according to permissions nodes.
- MySQL and SQLite support.
- Simple default home support - players can use /sethome and /home, without parameters, to warp to a default named home.
- Importing of homes from MyHome.
- Inviting of players to homes.
- Locale Support - customise uHome to talk your language, or fit your server's theme.
- Multi-world support, you decide if players can move between worlds with their homes.
- Auto completion of home names when warping.
- All commands work with online and offline players, case insensitively.
- Use Minecraft's vanilla command blocks with uHome to make teleporters in your world!
Installation & Setup
Simply download and place the uHome.jar into your plugins folder in your Bukkit directory. A configuration file is generated when running the plugin for the first time, which contains many options to adjust the behaviour of the plugin to your needs. Hopefully, the defaults provided should prove a good basis for most users. Easy permissions setup is possible by giving your players 'uhome.own' and your admins 'uhome.admin'. A 'uhome.all' node is provided that will also give the group/player no limits in addition to the player and admin command rights. If you're not a user of permissions, uHome allows all players to do basic actions by default, while giving ops full access.
For information on setting up permissions based (per group) limits, see the section entitled "Other Permissions" below.
For more configuration information, check out the Configuration page.
Need Help?
If you have any queries, you can use the comments section below and I should reply fairly quickly, as I check this page almost daily. If you'd like live support, you can ask me in IRC, either in #bukkit or #uhome under the username 'ks'. If you come across bugs, or have a feature request, create a ticket using the "Tickets" tab at the top of the page.
Live Support: irc.esper.net #uhome (May not be online, sorry!)
Commands & Permissions
Basic Commands: /home - (uhome.own.warp) - Takes you to your "home" home. /home set - (uhome.own.set) - Sets your "home" home to your current position. /home delete - (uhome.own.delete) - Deletes your home "home". /home help - Display help Multihome Commands: /home <name> - (uhome.own.warp) - Takes you to your home with the name <name>. /home list - (uhome.own.list) - Displays the homes you own. /home set <name> - (uhome.own.set) - Sets a home called <name> to your current position. /home delete <name> - (uhome.own.delete) - Deletes your home named <name>. /home limit - (uhome.own.set) - Displays the number of homes you can set. /home warp <name> - (uhome.own.warp) - Takes you to your home with the name <name>, avoiding conflicts with other commands. Invite Commands: /home invite <player> <name> - (uhome.own.invite) - Allows <player> to warp to your home called <name>. /home uninvite <player> <name> - (uhome.own.uninvite) - Removes <player> from <name>'s invited players list. /home invites [page] - (uhome.own.listinvites) - Displays the homes that you have been invited to. /home requests [page] - (uhome.own.listinvites) - Displays the players that you have invited to your homes. /home lock <name> - (uhome.own.unlock) - Locks a home, so that only those invited can warp to it. (Default behaviour.) /home unlock <name> - (uhome.own.unlock) - Unlocks a home, so that anybody who knows the name of the home may warp to it. Admin Commands: /home <player> - (uhome.admin.warp) - Warps to a player's default home (provided you have no homes with similar names). /home list <player> - (uhome.admin.list) - Lists a player's homes. /home delete <player> <name> - (uhome.admin.delete) - Delete's a player's home. /home reload - (uhome.admin.reload) - Reload uHome's configuration - Do not use this for swapping to MySQL /home <player> <name> - (uhome.admin.warp) - Takes you to the home of <player> called <name>. /home set <player> <name> - (uhome.admin.set) - Sets another player's home to your location. /home limit <player> - (uhome.admin.list) - Displays the maximum number of homes <player> can set. /home invites <player> - (uhome.admin.listinvites) - Displays the invites <player> has received. /home requests <player> - (uhome.admin.listinvites) - Displays the invites <player> has sent. /home info <player> <name> - (uhome.admin.info) - Displays information on the given home, including it's co-ordinates. /home debug - **(Console Only)** - Toggles debug logging to investigate permissions errors. Can create a lot of messages. /home <player> <owner> <name> (uhome.admin.send and uhome.admin.warp) - Sends the given player to another player's home. Can be used from the console, and from command blocks!
Other Permissions
Variable Permissions: (uhome.limit.[a-e]) - Gives the player the home limit reflected by the config. E.g. if limitB=10, and the player has the permission "uhome.limit.b", the player can make up to 10 homes. (uhome.cooldown.[a-e]) - Gives the player the cooldown time reflected by the config, as above. (uhome.warmup.[a-e]) - Gives the player the warmup time reflected by the config, as above. Bypassing Timers/Limits Permisions: (uhome.bypass) - Bypass all limits (cooldowns, warmups, bed usage and home limit) (uhome.bypass.cooldown) - Permission to bypass /home cooldowns (uhome.bypass.warmup) - Permission to bypass /home warmup (uhome.bypass.warmup.damage) - Permission to ignore damage when warming-up (uhome.bypass.warmup.movement) - Permission to ignore movement when warming-up (uhome.bypass.bed) - Permission to use /sethome when bed usage is forced. (uhome.crossworld) - Allows a player to move between worlds with homes. Admin Permissions: (uhome.all) - Has access to all commands in uHome (uhome.admin.reload) - Is able to reload uHome config.
Limits Explained
Limits and variable permissions are powerful and actually very simple to use. However, they may seem confusing at first, so for information on how to use them visit the Configuration page.
Importing From Other Plugins
uHome v1.5a and above support importing homes from both CommandBook and MyHome. For information on how to do this, please read the page Importing From Other Plugins. Would you like to see import support from other home plugins? Create a ticket!
Current Usage Stats
Stats provided from v1.5 and above only!
Credits
A huge thankyou to the original authors - tkelly and spathizilla, for their work on the base plugin. :)
Thanks to CubeNation for adding economy implementation via Vault.
Thanks to linkinkov & Schmarotzer for the Russian translation.
Another thanks to those users who consistently send good feedback, bug reports and feature requests. You know who you are!
Source code available on GitHub, feel free to fork, butcher and re-release to your liking. https:github.com/ks07/uHome
Want to see it in action? Visit Ultimate Minecraft
@ks07
Its good as it is.
Its best to have options for it.
Question for future releases:
Would anybody like a "lite" version? I.e. private homes only (no invites), no warmups or cooldows, no economy integration when it comes, etc?
Or would people prefer just to keep these as config options?
(No promises this will ever happen!)
@ks07
invites are only for vip players)
@Gizmocubesworld
Good to hear it!
If you don't want to use invites at all, you can disable them in the config.
@ks07
hm, ok, i'll keep on trying make that work)
http://clip2net.com/s/1ype5
so it works if i give uhome.own. but i dont want people invite payers to their homes. hm, i know what to do!
omg. added uhome.own to default and -uhome.own.invite and it works.
@Gizmocubesworld
Hey gizmo - that's odd, those nodes are correct. That message about contacting the server administrators is from PEX, so PEX doesn't think that you have the required node.
In the next release, I will add a permissions debug config option. This will let you see what permissions your server is telling uHome you have, so that you can see what is or is not working.
@deleted_7554077
@KJanar - Thanks for being helpful! :)
@Gizmocubesworld
@Gizmocubesworld Well uHome and PEX aren't the best buddies. But they work for me. I am running CB 1.1 R3 1846 PEX 1.18 and latest uHome 1.3.4
So imma teach u what i know.
Don't use any star node permissions with uHome it doesnt like them.
Use uhome.own or uhome.admin but not uhome.own.*
Also its uhome.all but uhome.* still works.
When you have the deny permissions enabled and are using uhome.* you have to put a negative deny permissions infront of it like this:
- -uhome.deny
- uhome.*
Thats because the * gives full access even the uhome.deny permission so it denies all acces, but having a negative deny permission infront of the uhome.* disabled that.
For more answers and question PM me.
i cannot set/warp/delete home without uhome.* permission. uhome.own.set/warp/delete does not work. i'm using pex. please help. thanks. Bukkit 1.1 R3
http://clip2net.com/s/1yi87 http://clip2net.com/s/1yi9V
hm, sethome works, but home set/delete do not work.
Coming up in the next major release:
Almost back to normal...
hoping to do one large update for 1.4, unless 1.1 breaks anything which needs fixing first. Watch this space!
@ForgeUser7554077
This plugin is working 100% with Pex and if anyone else is having problems with pex, the permission ' * ' and uhome.deny ask me on youtube.com/user/NiftyGamerz
NB! ks07 I made a new ticket 20 and I posted a new comment that contains the reason why the plugin ain't working with '*' permission. Hope you see this and fix it somehow :D
Thanks
Ou also tested just the uhome.* permission under owner and it works.
So it must be that the uhome.deny gets more power
@ForgeUser7554077
OK good news, the plugin still works but there is some bugs in the permissions.
The uhome.* permission isn't working in CraftBukkit 1.1 server, but you can use uhome.admin.* and uhome.own.*
Limits still work uhome.limit.a
@ks07
Bad luck for us. It's not working with CraftBukkit 1.1
None of the commands do nothing. I enter them but its not activating the plugin, no error messages no nothing, its just not doing anything
Just a note - there probably will not be any more updates to uHome this January due to exams and other commitments. Updates will resume in February, so please keep your feedback coming while you wait!
@Josh2905
Hey,
You must be using v1.3.1 / v1.3.3 - in which case the permission node you need is uhome.crossworld
Thanks.
How can I give my users the permission to warp to their home in different worlds? It works, if you have a * permission, but i cant find a permission or a config option for multiworld-homes.
@CTapblu
Hmm, that's interesting - If you don't mind me asking, is your password numbers only? Because as far as I'm aware, the inverted commas shouldn't be necessary.
(And in that case, I have an inkling as to what is causing this.)
EDIT: Turns out that yes, the error is most likely caused by having a numeric password. Normally, quote marks aren't necessary, unless the setting is numeric. I'll probably add quotes by default next update, as that way it should be fine for both types. Yaml is a strange beast...
Thanks for pointing the issue out!
i make it works... in cfg file, password line for user must be like: password: 'password'
default it looks like: password: password
Pls, fix it :) Or just place inverted commas to default cfg... Why i didn't see that before... P.S. It will be nice to publish detailed FAQ for noobs like me xD
@ks07
Thx, i can read logs :) But i can't find a problem...I have correct username and password (root access on localhost for testing).... Other plugins, like PEX, connect to database and use it normal... may be another proble in reading config? ore something else... help me pls