Bukkit

@javieraizpuru

spawnLastLocation remembers their location as they leave a given world to another world and is not really intended for use in onJoin, because it's not needed there.

Bukkit already remembers the "last logout location", so if you want them to spawn there, just comment out the onJoin event or use the default strategy. If your goal is to have them spawn at a first-time spawn (the only time they don't have a previous logout location) and their "last logout" location all the other times, just leave the default config:

events:
  onJoin:
    - spawnNewPlayer
    - default

and use /setfirstspawn to set the "new player" spawn for use here.

@Aiur850

Very interesting, considering I maintain both projects. :) Thanks for the info, I'll look into it. It could be a common library version mismatch causing the issue.

@andune

For comparison, I downloaded Spigot (same version that you listed) and got the following results:

07:51:30 [INFO] This server is running CraftBukkit version git-Spigot-jenkins-Spigot-377 (MC: 1.4.6) (Implementing API version 1.4.6-R0.4-SNAPSHOT)
07:51:46 [INFO] [HomeSpawnPlus] Enabling HomeSpawnPlus v1.7.3.2
07:51:46 [INFO] [HomeSpawnPlus]  Loaded 130 locale strings (0 overrides)
07:51:47 [INFO] [HomeSpawnPlus]  using WEPIF:bPermissions for permissions
07:51:47 [INFO] [HomeSpawnPlus]  Vault not found, HSP economy features are disabled
07:51:48 [INFO] [HomeSpawnPlus]  version 1.7.3.2, build 684 is enabled

>version
07:51:54 [INFO] This server is running CraftBukkit version git-Spigot-jenkins-Spigot-377 (MC: 1.4.6) (Implementing API version 1.4.6-R0.4-SNAPSHOT)
>version HomeSpawnPlus
07:52:13 [INFO] HomeSpawnPlus version 1.7.3.2
07:52:13 [INFO] Author: morganm
>home
07:52:14 [INFO] /home
>hsphome
07:52:23 [INFO] /hsphome
>homelist
07:52:31 [INFO] /homelist - show homes on all worlds
07:52:31 [INFO] /homelist world - show homes on 'world'

@seventoes

Do you have a 'commands:' section in your HSP config? If you can pastebin your config, I can look it over for any possible issues or use it to try to recreate the problem.

EDIT: Actually on closer examination, I see you are running Spigot. I have never tested against Spigot and I'm not sure if they've followed the CraftBukkit package-rename commit. In order for HSP to work, you'll have to pick the version of HSP that matches the version of CraftBukkit that Spigot imitates.

The Spigot message says v1.4.6 so if Spigot follows the package renaming, you would think HSP v1.7.3.2 would be correct. If Spigot chose not to implement the package renaming, you might need to use HSP v1.7.3 instead.

Some good news here is the in-development v2.0 of HSP eliminates this problem; it will be backwards compatible for all versions of CraftBukkit so one JAR will run on any version of CraftBukkit released up to that point (which should also include Spigot).

@jeffro1001

I've never heard of that and if all you did was install dynmap (no other changes) and got the behavior, then uninstalled dynmap and the behavior went away, that is very bizarre indeed.

However, in any case, regardless of the 'why' it happened, the answer will be the same: read the FAQ section on Essentials commands. Essentials, for all it's efforts to play nice and defer to other plugins, doesn't play well with HSP's dynamic command system and there are some very easy steps you can take to permanently resolve the issue on your server.

WorldGuard integration possibilities are covered in the examples, specifically Example 7 has lots of info on this.

The answer, as with all answers for HSP, is it depends on what you want to do. Lets assume what you're trying to do is set it so when a player dies in a WorldGuard region, they spawn at the WorldGuard region spawn (if set). But if they die elsewhere, they spawn at their home; if no home is set, you want them to spawn at the local spawn. Here's a simple example for what that looks like:

events:
  onDeath:
    - spawnWGregion
    - homeLocalWorld
    - spawnLocalWorld

Also, as with all things in HSP, there's value in doing and observing. You can reload HSP config live, so there's no cost to changing a config and '/hsp rc' and then give a test to see what it does. Turn on verboseStrategyLogging (read FAQ) for even more detail and watch your server.log. You should validate your HSP strategies are doing whatever it is you intend for them to do, so test it out.

@Clinot

In thinking through your use case, I think what you want is already provided by Bukkit for free:

events:
  onJoin:
    - default

In this scenario, when a player joins, HSP will just pass control over to Bukkit which will promptly do exactly what you're suggesting: log the player in wherever they last logged out.

The spawnlastlocation was really intended for use in other events, such as crossWorld or custom commands where the Bukkit logout location isn't what you want.

@buttatron2000

That is a WorldGuard feature, please read the WorldGuard documentation (I don't recall the syntax). Basically, using WorldGuard, you can set a spawn point for a given region. Then you can use HSP's spawnWGregion strategy to use those WorldGuard spawns as part of your strategy chains.

@Xcelsior1991

Two things: Please read this section in the How HSP works documentation regarding permission inheritance. I see your permissions are ordered lowest to highest and if your permission system uses inheritance, this will cause you problems.

Second, there are some known issues with Permissions in 1.4.6 unrelated to HSP and they seem to be most commonly related to "*" permissions. I'd recommend giving your admins your 'hsp.group.Admin' permission explicitly rather than depending on "*" to do it for you. That might resolve your problem. Also check out HSP's built-in /permcheck (/pc) command.