HomeSpawnPlus
HomeSpawnPlus (HSP) / SpawnControl: the most advanced Home/Spawn plugin for Bukkit. HSP has flexible events and strategies that you can customize for your unique needs. If you just want dead-simple home/spawn management, HSP can do that too, but you might find some other plugin easier to setup or understand. If you want full control and maximum flexibility to do whatever YOU want and not be limited by just basic /home and /spawn functionality, then HSP might be for you.
HSP's events and strategies, custom commands and integrations with plugins like WorldGuard and Multiverse allow you to completely control every aspect of spawns and homes, so that unique edge or setup you want, chances are good that HSP can do it for you.
Please read the FAQ before posting questions or tickets (especially Essentials users). Also there are Examples.
Versions
- Official releases are on the Files tab of this page
- 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. Jenkins
HomeSpawnPlus has these Features:
- Multi-world homes (one-home per world, multiple homes per world or even just one global home, your choice)
- Specific control as to what happens on events such as player login, player death, typing /spawn or /home commands using strategies. Should the user always stay on the same world? Spawn at the nearest of multiple spawns (ie. graveyard concept)? Maybe they always go to a specific group spawn on that world (for PvP factions, perhaps)? Your choice.
- Ability to set a one-time new player spawn point
- Cooldowns and warmups Can be set to cancel on movement or damage. Advanced details here.
- Economy support (via Vault) to optionally charge players for commands
- Home limits, definable per-group or per-permission. More documentation.
- Configurable per-world or per-permission for just about every option (events, cooldowns, warmups, costs, homeLimits)
- Define your own custom commands Documentation here
- WorldGuard region-spawn support (allow people to spawn at WG region spawn when inside that WG region)
- Ability to visit homes other people have set, on any world (controlled by Permissions)
- Language localization Also you can customize any message in HSP. Details here.
- Home invites - documentation here
- Set homes by clicking on a bed: read bed-related options documentation.
- Dynmap integration built in, very configurable to meet your own needs
- Persistence choice: Sqlite (default), MySQL or YAML
- Standard YML config.yml: with live reloading in-game (/hsp rc)
- Import home data from other plugins (Essentials 2.9, CommandBook 2.1 and SpawnControl v0.8)
Installation:
- Download HomeSpawnPlus.jar and put it in your Bukkit plugins folder
- Startup Bukkit, HomeSpawnPlus will automatically put the default config.yml into plugins/HomeSpawnPlus/config.yml
- Configure config.yml to your liking, then either '/hsp rc' to live reload the config, or restart your server.
Additional info
This plugin was designed to work with Vault, WEPIF, PEX, Permissions 2.x/3.x, or any Superperms-compatible plugin. Please read more about permissions here.
Under the hood: How HSP works
Examples
Spawn strategy documentation
Advanced Cooldown and Warmup information
User Command Reference
Admin Command Reference
Permissions
Changelog
Source Code
Metrics plugin
This plugin utilises Hidendra's plugin metrics system, which means that the following information is collected and sent to mcstats.org:
A unique identifier The server's version of Java Whether the server is in offline or online mode The plugin's version The server's version The OS version/name and architecture The core count for the CPU The number of players online The Metrics version
Opting out of this service can be done by editing plugins/Plugin Metrics/config.yml and changing opt-out to true.
Have an issue? Got a new idea?
If you find a bug or have an enhancement request, please create a ticket so I don't lose track of the request or issue in a comment stream. If you have a basic question, feel free to post in the comments here or visit the forums on forums.bukkit.org.
Thanks to @Timberjaw for the awesome work on SpawnControl that gave me a great base to start from!
@gummby8
In short: in the future it will be simplified using a new Bukkit method which will result in just checking for player.dat behind the scenes (I think), for now, you have to delete both the player.dat and the row in the hsp_home table.
Easiest way for the latter if you're using default SQLite is to:
What constitutes a "new player" I am trying to test the new players spawn, and I don't know how to set myself as a "new player"
posted ticket about value display when charged.
Huhu @andune
There is no point in the locale for "you are at your limit of yx homes for world "worldname"
@scungilli
Please use pastebin to share your config. comments here mangle the formatting so it's impossible to tell what's going on, plus it takes up a lot of room in the comments that could just be a single, clean link.
Since I can't really see what's going on in the formatting mess, I'll wait for the pastebin link to try to sort out any issues. Note that I use PEX myself and have no issues. Two things to be aware of:
Hi, im also experiencing issues with HSP and pex working together. i have taken all of your suggestions but none of them seem to solve this issue:
Commands for multiple homes set, but users are unable to access these commands.
here is my config file for HSP:
---core:
verboseLogging: false
warmup:
default: perWorld: 1 # I've attempted setting this number to the max value as well. global: -1
permission: limit1: permissions: - group.Moderators perWorld: 5 limit2: permissions: - group.VIPs perWorld: 3 limit3: permissions: - group.Members perWorld: 2 permissions: -group.Guest perWorld: 0
home: 0 sethome: 0 spawn: 0 groupspawn: 0
-- also, all of the permissions are entered correctly in each of the groups. I have tried variations of this config file but I just can't get it to change the outcome. any help would be great.@baemboo
You're probably missing the "hsp.command.spawn" permission. Or it's possible some other plugin is stealing your "/spawn" command. Read about and try the usurpCommand config option.
Or, another easy way to test is just rename HomeSpawnPlus.jar to "aHomeSpawnPlus.jar", that will guarantee it loads before the "other" plugin and gets the home/spawn commands assigned to it instead.
hmm i dont really get it, it doesnt matter how i set up the config when someone types /spawn it replies /spawn [player]
@BSEUNHIR
Yes it's fixed in the dev codebase and ticket #47 describes the workaround for 1.3. Unfortunately I haven't had time to package up another release, hopefully I can get to that soon.
It's a lot of work and time to maintain these plugins, I do my best to keep up with all of my plugins in the spare time I have outside of RL demands, but remember this is all done for free on my spare time. In fact, if you'd like to contribute to help, all of my plugins are open source and I take gitpull requests, so fixes are just a gitpull away from willing hands to help. ;)
@andune
I resolved my problem.
It's this:
http://dev.bukkit.org/server-mods/homespawnplus/tickets/47-op-check-taking-precidence-over-superperms/
Used the quick fix described there.
I hope you get to resolve your permissionproblems soon. (WEPIF and superperms) :)
@BSEUNHIR
I also get this. Always says it is using PEX permissions, even though I have latest worldedit and wepif.
@andune
I have worldedit on my server, together with PermissionsBukkit. I tried giving myself hsp.command.setspawn through both of them (but WEPIF should get the permissions from Permissionsbukkit already, right?) and it kept telling me that I didn't have permission.
But I just noticed something: It tells me that I'm using Worldedit 5.0 and WEPIF was changed in build 606. Thus, WEPIF is skipped. However, build 606 was back in 4.8. Is there something one my side I can do to have it go through WEPIF anyways?
@BSEUNHIR
Works fine. I have it running on #1718 on my server now, no issues.
It's possible you either have a permissions misconfiguration (I don't help with those, maybe see if some nice soul at #bukkit will assist) or you have some other plugin installed that's stealing the commands you're trying to use but you haven't given permission for (such as CommandBook).
One thing you can try is installing Vault; it's a nice "glue" layer between plugin and whatever permission systems you have, and as an added bonus if you want to use economy features, it enables those as well. Outside of that, I cannot help you based on the information given other than the things to look at that I've listed here.
Does this work on craftbukkit for 1.1? I can't get it to work, whatever I try to do it tells me I had no permission. :(
NVM :D. I just typed something wrong. Everything is going perfectly :D
It seems PermissionsEx has issues with Parent Nodes.
Audune: I must put in individual permission nodes instead of hsp.full or hsp.basic to get permissions working IN PEX. It says SuperPerms only, what does that mean...?
@Nuinethir
1. There is an open ticket (request) for this, Ticket #18.
2. I'm pretty sure spawn records pitch & yaw as well, unless a bug has creeped into a recent version; as I recall testing this specifically and seeing it work. I'll re-test in 1.3 and make sure nothing has broken; you can also do /setspawn and then run a SQL query from the "hsp_spawn" table to see the parameters that make it into the DB. Regarding groupspawn, again I believe it works the same way, but I can't say that I recall testing this one as thoroughly so it's certainly possible it never recorded yaw/pitch. In any case, please confirm the behavior your seeing against the latest version (1.3) and once confirmed, feel free to open a bug ticket so I remember to look at it when I'm fixing other bugs in preparation for the next release.
@andune Ahhh I see :D. Just one question: When you say the "kits" are only for SuperPerms, what do you mean? Just putting those kits in PEX doesn't work :/
@andune: Two requests for you:
1. When a player dies or does /home, the plugin should check to see if their bed exists. If it is broken, it instead sends them back to spawn.
2. I noticed that setting the home via the bed records not only the direction but the pitch and yaw. Spawn and groupspawn should work like this. As it stands now, /spawn will always have my players facing west. Since the exit from my spawn faces south, and the groupspawn (first-time players) faces the rules board facing north, it is somewhat disorienting.
Thanks!