Set Homes
PLEASE READ!!!
This plugin will no longer be updated. We have released a new an improved version called, Set Homes Two. All future updates will be applied there, however this plugin will not be removed from the projects page so feel free to use it in it's current state as it is stable.
SetHomes
A simple homes plugin with the ability to create, delete, and teleport to many different homes. Have the ability to control a blacklist of worlds in which players will be restricted from setting homes. Using the config you can control setting such as a maximum number of homes, teleport cooldown, teleport delay, and their respective messages that get displayed to the user.
Installation
Simply place the downloaded jar into your server plugins folder.
NOTE! For "MAX HOMES" to work you must meet one of the soft dependencies below, and setup groups for the respective permissions plugin. You will then also need to setup max-homes in the config.yml. An example max-homes setup can be found below the default config
Soft Dependencies
Only choose one option below
- LuckPerms permission plugin
- Vault plugin, as well as, a permissions plugin supported by Vault
Commands
- /sethome [HomeName] [HomeDescription] - This command will allow the issuer to set a home with a given name and description of their choosing at your standing location. If no name and description are given then you will set a default home at your standing location.
- /home [HomeName] - This command will teleport the user to the given "HomeName". If no home name is given then the user is teleported to their default home that was set by /sethome
- /home-of [PlayerName] [HomeName] - This command will allow players with the "homes.home-of" permission to teleport to any players set home. If no home name is provided it will assume the default home as the desired destination.
- /delhome [HomeName] - This command will delete the home at the given home name. If no home name is given then it will attempt to remove the default home.
- /delhome-of [PlayerName] [HomeName] - This command will allow players with the "homes.delhome-of" permission to delete any players set home. If no home name is given it will assume the default home as the home desired for deletion.
- /uhome <HomeName> <HomeDescription> - This command will allow players with the "homes.uhome" permission to update any of there already set homes. If no description is given, and there was one previously set before it will reuse the old one.
- /uhome-of <PlayerName> <HomeName> - This command will allow players with the "homes.uhome-of" permission to update a home for any player. If no home name is supplied then it will update the supplied players default home.
- /homes [PlayerName] - This command will list all of the players currently set homes if there are any. Players with the "home.gethomes" permission can use the extra PlayerName parameter to list the homes of a specific player.
- /blacklist [Add/Remove] [WorldName] - This command is used to both add and remove worlds to/from the blacklist. If passed no other arguments it will list all worlds currently blacklisted.
- /setmax <GroupName> <Amount> - This command will allow players with the "homes.setmax" permission to set a maximum number of allowed homes for a specific permission group. For example if you wanted to only allow the default permission group 4 homes you execute the command, "/setmax default 4".
- /strike - Have fun admins.
Permissions
- homes.* - A player given this permission will be allowed all commands under the Set Homes plugin
- homes.home - A player with this permission is allowed to teleport to named homes
- homes.sethome - A player with this permission is allowed to set named homes
- homes.strike - Give the power to others!
- homes.blacklist_list - A player given this permission will be able to list worlds in the blacklist
- homes.blacklist_add - A player given this permission will be able to add worlds to the blacklist
- homes.blacklist_remove - A player given this permission will be able to remove worlds from the blacklist
- homes.config_bypass - A player given this permission can set homes in blacklisted worlds, and doesn't have to wait for cooldown or teleport delays. They will also be able to exceed the max home limit.
- homes.gethomes - Give the ability to list any players active homes
- homes.home-of - Give the ability to teleport to one of any players active homes
- homes.delhome-of - Give the ability to delete one of any players active homes
- homes.uhome - Give the ability to update homes
- homes.uhome-of - Give the ability to update other players homes
- homes.setmax - Give the ability to set a maximum number of homes for a permission group
Default Config
# -------------------------- # SetHomes Config # -------------------------- # Messages: # You can use chat colors in messages with this symbol §. # I.E: §b will change any text after it to an aqua blue color. # Color codes may be found here https://www.digminecraft.com/lists/color_list_pc.php # Time: # Any time value is based in seconds. # Things to Note: # Set any integer option to 0 for it to be ignored. # The max-homes does not include the default un-named home. # Use %s as the seconds variable in the cooldown message. max-homes: default: 0 max-homes-msg: §4You have reached the maximum amount of saved homes! tp-delay: 3 tp-cooldown: 0 tp-cancelOnMove: false tp-cancelOnMove-msg: §4Movement detected! Teleporting has been cancelled! tp-cooldown-msg: §4You must wait another %s second(s) before teleporting!
Example Max-Homes setup
max-homes: default: 1 free: 3 subscriber: 5 admin: 0
F.A.Q
- Q: How can I give players permission to set named homes?
A: You will need to install a permissions plugin, either LuckPerms, or Vault & a Vault supported permissions plugin then apply the permission "homes.sethome" to the (player or group) you would like to allow the usage of multiple homes for.
Change Log
- Set Homes Two released: https://dev.bukkit.org/projects/set-homes-two
- Added support for Minecraft/Craftbukkit V1.16.3.
- Added support for LuckPerms permission plugin
- Made LuckPerms default permission plugin, and set Vault as a rollback before disabling all together
- Changed colors, and layout of list homes message to be more readable
- Fixed error, where SetHomes could not load without Vault
- Removed auto-updater functionality because it was not working properly
- Added server log messages for permissions plugin hooking, and no perms plugin found
Hi,
I need a little help, I have essential X, Luckperms, Vault and Set Home. I just upgrade my server from 1.15 to 1.16, so I can use the command /homes (and then It's list all my home I had) but when I use /home (name of any home I have) It's don't work because It's use essential X home command now. I looked everywhere I could look but same problem, the please somebody can help me to solve this thank you very much.
In reply to Forge_User_11497170:
Hello,
Within the config.yml of essentials there is a section for disabling commands. You can add the home command to that list, so the version from "SetHomes" will take over. The section within the config looks something like this
Hope this helps,
Xquiset
In reply to Xquiset:
Hello
No it didn't work, i don't know how but when i put the command on the disabled command it still work
I think maybe it's good but nothing version for 1.8!
One of the players on my server informed me that he got this error when he tried to access one of his "homes" (home 1), he is the only one with this problem. As an administrator I can use a command to go to the location of your "home" but it also gives me the same error.
An internat error occurred while attempting to perform this command
25.10 21:28:43 [Server] ERROR null
25.10 21:28:43 [Server] INFO org.bukkit.command.CommandException: Unhandled exception executing command 'home-of' in plugin SetHomes v1.2.9
25.10 21:28:43 [Server] INFO at org.bukkit.command.PluginCommand.execute(PluginCommand.java:47) ~[patched_1.16.3.jar:git-Paper-219]
25.10 21:28:43 [Server] INFO at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:159) ~[patched_1.16.3.jar:git-Paper-219]
25.10 21:28:43 [Server] INFO at org.bukkit.craftbukkit.v1_16_R2.CraftServer.dispatchCommand(CraftServer.java:802) ~[patched_1.16.3.jar:git-Paper-219]
25.10 21:28:43 [Server] INFO at net.minecraft.server.v1_16_R2.PlayerConnection.handleCommand(PlayerConnection.java:1908) ~[patched_1.16.3.jar:git-Paper-219]
25.10 21:28:43 [Server] INFO at net.minecraft.server.v1_16_R2.PlayerConnection.a(PlayerConnection.java:1719) ~[patched_1.16.3.jar:git-Paper-219]
25.10 21:28:43 [Server] INFO at net.minecraft.server.v1_16_R2.PacketPlayInChat.a(PacketPlayInChat.java:47) ~[patched_1.16.3.jar:git-Paper-219]
25.10 21:28:43 [Server] INFO at net.minecraft.server.v1_16_R2.PacketPlayInChat.a(PacketPlayInChat.java:5) ~[patched_1.16.3.jar:git-Paper-219]
25.10 21:28:43 [Server] INFO at net.minecraft.server.v1_16_R2.PlayerConnectionUtils.lambda$ensureMainThread$1(PlayerConnectionUtils.java:23) ~[patched_1.16.3.jar:git-Paper-219]
25.10 21:28:43 [Server] INFO at net.minecraft.server.v1_16_R2.TickTask.run(SourceFile:18) ~[patched_1.16.3.jar:git-Paper-219]
25.10 21:28:43 [Server] INFO at net.minecraft.server.v1_16_R2.IAsyncTaskHandler.executeTask(IAsyncTaskHandler.java:136) ~[patched_1.16.3.jar:git-Paper-219]
25.10 21:28:43 [Server] INFO at net.minecraft.server.v1_16_R2.IAsyncTaskHandlerReentrant.executeTask(SourceFile:23) ~[patched_1.16.3.jar:git-Paper-219]
25.10 21:28:43 [Server] INFO at net.minecraft.server.v1_16_R2.IAsyncTaskHandler.executeNext(IAsyncTaskHandler.java:109) ~[patched_1.16.3.jar:git-Paper-219]
25.10 21:28:43 [Server] INFO at net.minecraft.server.v1_16_R2.MinecraftServer.ba(MinecraftServer.java:1135) ~[patched_1.16.3.jar:git-Paper-219]
25.10 21:28:43 [Server] INFO at net.minecraft.server.v1_16_R2.MinecraftServer.executeNext(MinecraftServer.java:1128) ~[patched_1.16.3.jar:git-Paper-219]
25.10 21:28:43 [Server] INFO at net.minecraft.server.v1_16_R2.IAsyncTaskHandler.awaitTasks(IAsyncTaskHandler.java:119) ~[patched_1.16.3.jar:git-Paper-219]
25.10 21:28:43 [Server] INFO at net.minecraft.server.v1_16_R2.MinecraftServer.sleepForTick(MinecraftServer.java:1089) ~[patched_1.16.3.jar:git-Paper-219]
25.10 21:28:43 [Server] INFO at net.minecraft.server.v1_16_R2.MinecraftServer.w(MinecraftServer.java:1003) ~[patched_1.16.3.jar:git-Paper-219]
25.10 21:28:43 [Server] INFO at net.minecraft.server.v1_16_R2.MinecraftServer.lambda$a$0(MinecraftServer.java:177) ~[patched_1.16.3.jar:git-Paper-219]
25.10 21:28:43 [Server] INFO at java.lang.Thread.run(Thread.java:748) [?:1.8.0_252]
25.10 21:28:43 [Server] INFO Caused by: java.lang.NullPointerException
25.10 21:28:43 [Server] INFO at java.util.Objects.requireNonNull(Objects.java:203) ~[?:1.8.0_252]
25.10 21:28:43 [Server] INFO at com.samleighton.xquiset.sethomes.SetHomes.getHomeLocaleFromConfig(SetHomes.java:370) ~[?:?]
25.10 21:28:43 [Server] INFO at com.samleighton.xquiset.sethomes.SetHomes.getPlayersNamedHomes(SetHomes.java:231) ~[?:?]
25.10 21:28:43 [Server] INFO at com.samleighton.xquiset.sethomes.commands.GoHome.teleportHomeOf(GoHome.java:286) ~[?:?]
25.10 21:28:43 [Server] INFO at com.samleighton.xquiset.sethomes.commands.GoHome.onCommand(GoHome.java:109) ~[?:?]
25.10 21:28:43 [Server] INFO at org.bukkit.command.PluginCommand.execute(PluginCommand.java:45) ~[patched_1.16.3.jar:git-Paper-219]
That error only occurs with one player, the others are fine.
In reply to Overglitch_:
Hello,
Sorry for the much delayed reply. I believe there is a value for this players particular home that is somehow missing. You will need to find out the Minecraft UUID of this player and look in your homes.yml, located in the SetHomes plugin folder, and see if all the values for this players home appear to be set correctly.
Best Regards,
Xquiset
Quick question. If I decide not to install any of the soft dependencies, how many homes will people be able to set?
I really just want everyone to have one home and that's it. No need to name it anything, a simple /sethome and /home for everyone to have would be enough.
Do I need to install the soft dependencies and set maxhome to 1? Or is that the default setting for the standalone plugin?
In reply to Mrfluffertootle:
Hello,
You should still be able to use the unnamed homes by just issuing /sethome and /home. If you do not give anybody permission to the "homes.sethome" permission then no player will be able to set the named homes, unless they are op-ed. You will not need any of the soft dependencies for this functionality.
Best Regards,
Xquiset
Very good Plugin. If u are hesitating. Just download it. The only problem is that ppl respawn at their home and not their bed. That can be annoying if they have a limited amount of homes but want to respawn on their bed location. So they would need to set more homes but they can't because it's limited.
ㅇㅀ
I can't get 1.2.8 to work at all so had to go back to 1.2.7, it wouldn't even start when the server started at all.
In reply to mental_metalhead:
Hi,
Could you explain a little more what it is that's not working? Is the plugin not loading, is the server not loading because of the plugin? Can you post there server logs?
Best Regards,
Xquiset
In reply to Xquiset:
I install the Jar file on my server in plugins for the 1.2.8 and it never starts on sever boot at all not even an error so I rolled back to 1.2.7 and it started working again but I get an error that 1.2.7 tried to update and it failed. Logs wouldn't show you anything because Sethomes 1.2.8 never even shows up.
In reply to mental_metalhead:
Hello again,
Thank you for the information on what happened. I am currently looking into this issue. I will update you here as soon as I figure out what might be happening.
Best Regards,
Xquiset
Hey there :) I have some trouble since updating the plugin to the newest Version, running a 1.16.2 Bukkit-Server:
It says "SuperPerms no group permissions." - What is that? I use MyPermissions, and the group all players are in got the following permissions:
homes.sethome
homes.home
homes.gethomes
homes.uhome
homes.sethome
Can you help me? The error occures when i try to save a new home. I can use existing homes, but when i try to save a new it says ingame "An internal error occured while attempting to perform this command".
Thanks in advance!
In reply to Forge_User_86387630:
Tried a bit, this error occures even when i remove the permissions-plugin.
In reply to Forge_User_86387630:
So, even with the default Bukkit permissions i got this error. But: When i delete the SetHome folder and let the plugin create a new one, it works fine. Any idea?
In reply to Forge_User_86387630:
And another one: Version 1.2.5 is working without any errors. So i stick with it :)
In reply to Forge_User_86387630:
Hi,
This error is caused by not having a Vault compatible permissions plugin. Vault is used so that I can grab "groups" from various different permission plugins out there. You will need to install a permissions plugin that is listed on Vaults plugin page. Sorry for any confusion.
Best Regards,
Xquiset
I'm having an issue where another player and I aren't able to set multiple homes with names anymore. It used to work before I had reset my server but now all me and him get are "An internal issue has occurred" or something around that. Not sure what it could be. I 've updated to the latest version and also tried Vault but Vault made everything worse.