Bukkit

@ThisUsernameIsMine

You're confusing home and spawn. Spawn/Groupspawn are admin-controlled places, settable only through /setspawn and /setgroupspawn.

Homes are user-controlled places, settable via /sethome or bed clicks. According to your config file you posted previously, your /home strategy is defined as:

# strategies to use when player types "/home"
  onHomeCommand:
    - homeMultiWorld

This means when you type /home, HSP looks first for any home you've defined on your local world (in this case, creative) and not finding one, it then looks for any home you've defined on your default world. Since you're saying you're being sent to world survival, I'll assume this means you've defined your defaultWorld as survival, thus this is where HSP sends you.

HSP is doing exactly what you told it to do. Again, I recommend turning on "verboseStrategyLogging" and watching the logs when you do things. Doing so, you would have seen HSP processing the "homeMultiWorld" strategy and not finding a local home but instead finding a home on your default world.

@MCCharlieCraft

I'll assume you've replaced "{USERNAME}" "{IP}", etc with appropriate values to a known, working MySQL DB? You also need the mysql jar in your server lib directory. Do you have other plugins already working with MySQL?

@ThisUsernameIsMine

This is correct, groupspawn is largely an inherited feature from this plugins original SpawnControl roots and I've done very little to change it's behavior since then. As originally designed in SpawnControl, it was specific to a certain world and that behavior still holds true. I believe part of the reason for this is permission systems allow defining per-world groups/permissions, so there's no easy/defined way to globally query for a persons group, as it might be different on different worlds.

I did add a 'spawnGroupSpecificWorld' strategy at some point (see strategy doc), so you could use this in combination with world-specific strategies to redirect one world's events to spawnGroup in another world. This will spawn them at the groupSpawn for the group they are in for that world. Note that vanilla superperms API does not support cross-world queries for group/permissions, so you need to have something like bPerms/PEX and Vault/WEPIF in place in order to take advantage of this.

@Fearlessagent

Yes, use your permission system. Most all permission systems allow per-world settings, so just disable the "hsp.command.sethome" permission on the worlds you don't want it on. Or rather, in your case, only enable it on the one world you DO want it on.

Regarding the homeLimit settings, you haven't defined a global limit and in the absence of any defined limit, a limit of "1" is assumed. Thus your config is essentially saying this:

# ability to raise or lower the limit of homes you allow
# players to have. Can be defined on a per-world or
# per-permission basis. (-1 = unlimited)
homeLimits:
  singleGlobalHome: false
  default:
    global: 1
  world:
    myworld:
        perWorld: 2

And the global limit of 1 is being enforced. If you want no global limit, then change it to -1.

@ThisUsernameIsMine

Did you restart after /setspawn? Looking at the code, the world-spawn setting code only happens on world loading. This actually was inherited from the original SpawnControl because that's how it did it, I will change that in the future to happen immediately on /setspawn. You can use the new /setmapspawn which will ONLY set the map spawn (and happens immediately), which appears to be the exact same function as "ExactSpawn". Can't tell for sure since the author doesn't share source publicly, but you're welcome to look at HSP's code for this:

https://github.com/morganm/HomeSpawnPlus/blob/master/src/main/java/org/morganm/homespawnplus/commands/SetMapSpawn.java#L23

Regarding your spawngroup login problem, I already answered my best guess at what's going on: you have the "group.failgroup" permission, because you're inheriting it through group inheritance. Use your permission system to check. Or, as I also volunteered, turn on verboseStrategyLogging and pastebin the log it spits out when you login here. It will tell us exactly what HSP is doing and if it's processing the "group.failgroup" permission for you, it will say so.

Regarding last login location, no Bukkit does this for you. Yes Bukkit still has the weird spawn issue by default, but Bukkit recently added an "exact-spawn" parameter to bukkit.yml, so you can just use that instead.

@williewillus

The bed-click behavior was changed in 1.5.1, release notes document the new options:

http://dev.bukkit.org/server-mods/homespawnplus/files/26-v1-5-1/

I do believe as part of these changes the first click was canceled in response to another user request to disable the "You can't sleep at night" messages it was printing. It's really one or the other, seems different people want different options, so I will add in a config option to allow you to choose. For now, you might disable the "core.bedhome2clicks" option and then right-clicking on a bed (once) will both set your HSP home and sleep at night.

@ThisUsernameIsMine

Reading ExactSpawn's homepage, all it does it change your maps spawn. HSP's "/setspawn" will do the same thing if you have "core.override_world" set to true and as of 1.5 there was also added a "/setmapspawn" command that does the same thing. In addition, you can type "/spawnlist -m" to view the spawns for each map you have.

Sounds like you just didn't have your map spawn set and went and found another plugin that did exactly that. Feel free to keep using it or feel free to use HSP's "/setmapspawn" feature, they do the exact same thing.

@C0nd3mn3d

possible to create an event? Sure. The unlikely part is that it would require a strategy that knew how to talk to some other plugin and that doesn't really fit for HSP. It has built-in home capabilities, so why would you want to pass it to another plugin? If you really want /sethome to go to another plugin, just disable it within HSP's plugin.yml and your other plugin will take over the command (assuming it has it registered).

Of course, you won't be able to use homes as part of your strategies then since you're using another plugin to manage your homes that HSP can't see. But maybe that's what you want.