Bukkit

@Cedimedi

Please read the permissions page about enabling ops permission settings. That said, the out-of-the-box settings for HSP will use superperms and all the superperms nodes are configured for full access to ops.

So it's more likely that you're running some other plugin that is eating your /setspawn command, such as CommandBook. Please review the HSP FAQ for instructions on how to deal with that situation.

@minecraftbreda

Yes, v1.4.3 shows 'CB 1.2.3-R0.1' as a supported version, which means it's R6 event compatible. I notice that 'CB 1.2.3-R0.2' is now an option to select in the upload menu, but there were no breaking changes between those versions (there would be whole long comment threads here if there were). I'm running it on this dev build:

This server is running CraftBukkit version git-Bukkit-1.2.3-R0.2-3-g7acc04c-b2063jnks (MC: 1.2.3) (Implementing API version 1.2.3-R0.3-SNAPSHOT)

@minecraftbreda

Click the 'files' tab and look under the 'game version' column.

@tremor77

Example is in the full config reference. Here's another example:

cooldown:
  permission:
    entry1:
      permissions:
      - group.Newbie
      - group.Guest
      home: 300
      spawn: 600
    entry2:
      permissions:
      - made.up.permission
      - hsp.cooldown.60sec
      home: 60
      spawn: 60
    entry3:
      permissions:
      - special.group.of.people
      home-named: 60

In this example, anyone with the permission "group.Guest" or "group.Newbie" will have a home cooldown of 5 mins (300 sec) and spawn cooldown of 10 minutes. Anyone with the permission "made.up.permission" or "hsp.cooldown.60sec" will have a 60 second cooldown. Note that both of those permissions were made up, you can make them whatever you want. All HSP does it check the permissions list you give it against the player's permissions.

Also note in the last example (entry3), the players with that permission have the "home-named" cooldown set, which means they have one cooldown per home. So if they type "/home a", that starts the 60-sec cooldown for home a. They can immediately type "/home b" to go to their home b, which is on a separate 60-second cooldown.

Read the 'Advanced cooldowns and warmups' link for more detailed on advanced use cases if you want them, or just stick to the basics, whatever works for what you want to do.

@muggerfugger

Set "core.verboseStrategyLogging: true" in your config. You'll see something like this when a strategy chain fires:

2012-03-19 [INFO] [HomeSpawnPlus] evaluating default global strategies
2012-03-19 [INFO] [HomeSpawnPlus] Evaluated SPAWN_THIS_WORLD_ONLY, location = world,143,73,34
2012-03-19 [INFO] [HomeSpawnPlus] Evaluation chain complete, location = world,143,73,34

The last line tells you the location where HSP is sending the person. If you check the location you were teleported to and it doesn't match what HSP said, then it wasn't HSP that sent them. (ie. you probably have some other plugin doing something)

Note the log message is abbreviated so as to not be spammy in the log, HSP records and uses the *exact* double precision location and sends them there. Assuming you're using sqlite, feel free to open the sqllite database and run the query "select * from hsp_spawn" and you'll see the exact locations HSP has on record.

@Wookieguy

I confirmed the error you're getting is accurate for what you're doing. You have changed the "onHomeCommand" strategy, for which there is no default Bukkit option (like there is for death/spawn). So when HSP finishes evaluating strategies and still has no location, it will print an error if you have "core.verboseLogging" set to true. Set that to false to not have the error printed to your log.

As to why it's still not working, my best guess is that it has to do with the fact that whatever permission system you're using isn't aligning with what HSP is looking for. Using Vault is your best bet and also remember that groups are case sensitive. I really don't have anything else to offer as I don't do troubleshooting for permission/group issues.

What I might do in a future release is add an admin capability that allows you to run a query to see what HSP sees as the users "primary group". With that in place, it will become easy to match up what HSP sees with what you are trying to do. Or if HSP doesn't see anything at all, you know you have some permission/group troubleshooting to do.

@tremor77

Detailed notes on HSP's warmup/cooldown capabilities is available here.

I've never used booscooldowns so I can't help you with that. HSP does also have a per-permission charging capability, but maybe you want to keep it all in boos; up to you.

If you do decide to use HSP's cooldown/warmups, you can turn on "core.debug" to true and you will end up with some detailed info in your "plugins/HomeSpawnPlus/debug.log" that you can use to troubleshoot any issues. Again, can't help you with boos, but maybe they have a similar facility.

@Doidles

If you're using and like Essentials, just use their spawn commands.

If you like something that HSP has regarding spawns but don't want to switch homes, then just use HSP and don't use any home-related strategies or give out any home permissions to your players. Just realize you obviously won't be able to leverage homes as part of the event chains (ie. send to home if they have one, otherwise to some spawn), but you wouldn't be able to with any other plugin either since all your homes are recorded in Essentials.

I did have an Essentials home importer (that's what I migrated away from when I wrote HSP originally a long time ago), but I haven't updated it in forever and I doubt it works with the latest version.

@harryjamesuk

spawn at a specific world on death:

events:
  onDeath:
    - spawnSpecificWorld:theworld

in "theworld", go to wherever you want to set your spawn and type "/setspawn". Also type "/spawnlist" afterward to make sure it was set and you don't have some other plugin that's eating your /setspawn.