Bukkit

@FredyR4zer

homeLimits:
  default:
    perWorld: 1
    global: -1

  permission:
    vip:
     permissions: [group.vip]
     perWorld: 3

For any player with permission group.vip (add this to your VIP group), they will have 3 homes per world, and the default global unlimited. Everyone else gets 1 home per world. Change to suite your tastes.

If you setup more than just one per-permission group, beware of permission inheritance.

@FredyR4zer

Yes. Try it.

@Paxination

You're close; you have a typo on your limit1 perWorld entry (you didn't capitalize the W), so I'll assume you're finding you're stuck at the default perWorld limit of 2.

@Jo11yWombat

The most current HSP 2.0 version (can be found on Jenkins) includes the feature as described. Right now this works such that you could have the command block set as "/spawn @p spawn1" and it would result in HSP treating it as if the player has run "/spawn spawn1". The implication and downside to this approach is it means the player must have access to run the command, which also means there's nothing to prevent the player from just running "/spawn spawn1" at any time.

You could obfuscate this somewhat by using custom commands, but long-term I will find a way to treat console commands like this in a special way and allow them to run as op perms rather than the permissions of the player.

Be warned that HSP 2.0 is only alpha at this point, but it works well in all of my own local testing and I'd appreciate some extra testers at this point to run it through it's paces, so feel free to give it a try. There are no DB changes, so if things don't work out, rolling back is as simple as putting the old JAR in place. Also HSP 2.0 supports all current CraftBukkit versions so you don't need a special one for your version of CraftBukkit.

EDIT As of build #521, the command block permissions should work properly. Even if the player doesn't have permission to use the /spawn command, the command block will still work, as you would expect.

@PAL18

If you're seeing that message, there will be a stack trace in the console (or server.log) to match. Please pastebin the stack trace, paste the URL into a ticket and include all relevant details (HSP version, CB version and any other plugins you are running). The stack trace will usually point me right to the offending line of code, and the additional details will help me create an exact test environment to reproduce the error and test to make sure it is fixed when I write code to fix it.

@Jo11yWombat

Well, first the HSP way to do this would be to set a spawn, like "/setspawn class_selection". Then players could teleport there using "/spawn class_selection". However, you want to do this via a command block and so that would require some way to pass a console command to accomplish that effect. Unfortunately, HSP does not currently have this feature.

Based on HSP 2.0's codebase, I think it's reasonable I could detect the console as input, which is what a command block command runs as, and then the first arg could be the player. This way all HSP command would automatically take the first argument of any command from the console to be the player, so you could do something like /spawn @p class_selection and HSP will take it to mean the player (@p) is running "/spawn class_selection".

I'll look into adding this into HSP 2.0, which is where all new features are going. So you'd get this new feature in 2.0 and will be able to help me test and make sure it's ready for release.

@shadvalentine

I like TeleportSuite from @krinsdeath.

Most teleport plugins only hook /back for their own teleports, but a smart one would hook TeleportEvent and keep track of all teleports, regardless of which plugin it came from. I suggested this to @krinsdeath for TeleporteSuite a long time ago and I'm pretty sure he added it, and I know my server has been happy with that plugin.

That said, one area I know there would be a conflict is if you are using a crossWorldTeleport strategy. If you use /back in combination with such a strategy, the crossWorldTeleport strategy would "take over" your /back and do whatever it was you instructed HSP to do. I've not heard of this being a problem for anybody, but you weren't specific about your problem so I'm just calling that out in case that's what is going on.

@Paxination

Yes. You can set homeLimits per-world, so you would set the limit (separately) for each world to 2.

Further, at your discretion, you could limit players to only being able to go to homes on their local world, so while in world PVP, they couldn't go to their homes in survival. Or they could. Up to you.

@shadvalentine

Gunnerrrrr has it right. You are looking for a teleport plugin, there are plenty of good ones out there. I don't see HSP has any value to add to what these other plugins already do very well.

And while I'm on the subject, thanks to Gunnerrrrr for helping people out with comments and tickets for HSP. The help with issues is greatly appreciated Gunnerrrrr!

@Lars_1993

I'm not aware of having added any functionality for worlds to share each other's homeLimits, but it seems like a useful concept. Please open an enhancement ticket for this idea. I can't promise I will be able to get to it anytime soon, but at least the next opportunity I have time to work on HSP, there's a chance I'll work on enhancements from my ticket list and cut some code for it. :)