Bukkit

@thernztrom

Have you slept in a new bed since the update? The problem is that Bukkit now looks for a bed at the *exact* point your Bukkit "home" is set to, and HSP lets you record your home a few blocks away. The fix is that when you set your home, HSP now sets your Bukkit home to the exact bed location, which makes Bukkit be quiet about the message. So when you sleep in a bed after the upgrade, the message should go away.

@tremor77

Yes, as per the strategy documentation: "spawnLocalRandom: choose a spawn at random in the player's local world to spawn the player". This means HSP will choose a random spawn location out of the ones you've setup with "/setspawn" (I'll update the docs to be a bit more explicit about this behavior). You say it always sends them to the same location, so if you type "/spawnlist", I'd bet you only have one spawn setup for that world.

It sounds like what you want is the newly added "spawnWorldRandom" strategy. This will spawn the player at a completely random location in whatever world they are in. Please note if you have WorldBorder intsalled, this will spawn within the WorldBorder limits, otherwise it defaults to a 1000..-1000 square area. You can also use the spawnRegionRandom in conjunction with WorldGuard regions to narrow down the random spawn area if you like.

Regarding taking over MV portals, that seems fraught with peril as far as development and Bukkit go. I will think on it some more, but for now, I'm going to say that's not easily possible.

@Thunder7102

overwrite multiverse spawn? I've worked with the MV devs and there should be no problem with MV overriding HSP due to the way the priorities are set between the two plugins. Follow the FAQ to turn on verboseStrategyLogging to find out what's happening.

CommandBook import is supported and documented on the admin commands page.

@bearbear12345

There are two ways to accomplish this. First, you might be using a permission system and want to align the spawns to specific groups (run /groupquery Notcher; we'll assume it returns "groupA"). If this were the case, you can "/setgroupspawn groupA" and also for your other groups, then in your config:

events:
  onDeath:
    - spawnGroup

(you'll probably want some other strategies after it, in case a player isn't in a group that has a group spawn set, but that's up to you)

However, let's assume you don't want to align to group names, maybe because you have a spawn called "spawnA" and you want 2 different groups to use the same spawn, plus you might want to assign the permission to individuals and not just groups. In this case, you would do something like so:

events:
  permission:
    entry1:
      permissions:
        - hsp.group.1
      onDeath:
        - spawnNamedSpawn:spawnA

In this example, anyone with the permission "hsp.group.1" will be sent to "spawnA".

@KillahKiwi

Sure, I've added it as part of the development towards the next release, strategy "nearestHomeOrSpawn". You can download a dev build from link in the Changelog dev notes.

@Wizzy86

I have no idea what regios is or does, but yes, HSP works with WorldGuard regions. You just have to include the appropriate strategy to use it however you want. For example, if you wanted a player to spawn in a WorldGuard spawn (set by "/wg flag region spawn" or somesuch) if in a region and otherwise to spawn at their home and if no home, to spawn at the world spawn, it could look like so:

events:
  onDeath:
    - spawnWGregion
    - homeMultiWorld
    - spawnLocalWorld

Review the strategies guide for all your event strategy options. Recently added was the ability to spawn at a completely random point inside a WG region using the "spawnRegionRandom" strategy.

@GamingG

I added reset cooldowns upon death in 1.6, read the changelog and look at the new "config_defaults.yml" for details. Enjoy.

@Mayhem777

Read the FAQ. The first step is to use verboseStrategyLogging. Turn that on, look at the output. If that doesn't help you figure out what's going on, then pastebin the output and your config.yml and put links here.

With the lack of any details to go on that you've published so far, my only guess could be to try setting "core.safeTeleport: false". This has been on by default since 1.5.5, however there were some changes to the safe teleport algorithm in 1.6 that include fire avoidance and some efficiency improvements. It's possible that's created a bug that's triggered by your particular spawn setup.