Bukkit

@chrisjon

Alright, you previously defined issue #1 as:

1. Default users is always teleported back to spawn when they rejoin the server.

So I'm going to assume by your post that you've fixed issue #2 and that this issue #1 is still happening. In which case, according to the log you posted, you'll see that HSP finished the evaluation chain with "location = null", this means that HSP took NO action. If that player is being teleported to spawn instead of where they last logged out, it's not HSP's doing.

I looked over your other plugins and I don't see one that stands out to me that's doing the spawn teleport, but you might try turning them off one at a time until you find it.

@harryjamesuk

Please read some of the online documentation, there is a wealth of it that covers your questions. Try these:

http://dev.bukkit.org/server-mods/homespawnplus/pages/strategy-doc/ http://dev.bukkit.org/server-mods/homespawnplus/pages/examples/

There are events and strategies that cover your exact scenario.

@Wookieguy

Enable "core.verboseStrategyLogging: true" and HSP will log detailed messages to your server.log as it is processing strategies. So then run your /spawn command and see what it is doing. Feel free to pastebin the output and your config here if you need help figuring it out or think you may have tripped on a bug.

Also note that the group names are case sensitive.

@Wookieguy

One way you could do it is like so:

events:
  onSpawnCommand:
    - spawnGroupSpecificWorld:arcanian_world
    - spawnGroupSpecificWorld:vanguard_world

on arcanian_world, you would /setgroupspawn Arcanian. on vanguard_world, you would /setgroupspawn Vanguard.

The result is that when someone with permission "Arcanian" types /spawn, the first strategy will result in looking for a groupspawn "Arcanian" in arcanian_world, which will be found and the Arcanian will be sent there.

When a Vanguard types /spawn, a groupspawn "Vanguard" will be searched for on arcanian_world, and since you haven't set one there, HSP will move on to the next strategy which will check for groupspawn "Vanguard" on vanguard_world, where the Vanguard will then be teleported to.

Another way to accomplish the same thing is to use per-permission events, where you could have a spawn chain specific to each Vanguard or Arcanian in case you wanted to something crazy. ie. perhaps when an Arcanian dies on "vanguard_world", you want them to "spawnNearestSpawn" (ie. graveyard concept), but when they're on their home world, they go to their home instead. All that is possible too.

@Wookieguy

I believe what you are looking for is the "spawnGroupSpecificWorld:myworld" strategy. The reason is that groupSpawns are specific to a world, and "spawnGroup" just operates on the local world, so on another world it won't find anything.

So for example, let's say you have 3 worlds: "world", "creative" and "new-lands". Let's say you have done "/setgroupspawn redspawn" in world, and have given some players the "redspawn" permission. With example config:

events:
  onSpawnCommand:
    - spawnGroup
    - spawnLocalWorld

players with redspawn permission on world will go to redspawn, while other players would go to whatever the default spawn is set to for that world. However, on world "creative" or "new-lands", everyone will go to the localspawn since there is no redspawn you've defined on those worlds.

Changing the first strategy to spawnGroupSpecificWorld:world will make it so redspawn players will always go to redspawn on world no matter which world they are on and non-redspawn players will fall through to spawnLocalWorld as before.

Note that if you have a perm system that can have different permissions on different worlds, HSP respects that and checks the permission of the TARGET world (world in this example).

@chrisjon

Regarding #1, try turning on "core.verboseStrategyLogging". HSP will log the strategies it runs (such as when player logs in) and you can see where it is trying to send them. For example, if HSP's result is to send the player to "0,80,0" and your players are ending up on "400,80,-200", then you know some other plugin you have is also set to "Highest" event priority and is overriding HSP.

2. This is because your "onHomeCommand" event chain has one strategy: "homeMultiWorld". This means HSP will check for a home on the local world ("explore") and then in the default world ("world_main"). Since you say they have a home on "world", it's not being checked. Since you are using 1 home per user, I'd suggest using the "homeAnyWorld" strategy instead, which would find the home on "world" in your example.

@webname

There is not, though I know someone asked for it before. I don't see an open ticket for it so maybe it was in a comment thread long since lost. Please open an enhancement ticket for this feature. Can't promise I'll get to it anytime soon, but at least it'll be in the list for me to consider next time I have some free time to work on HSP features.

@tremor77

This is not a HomeSpawnPlus message:

> cd src/HomeSpawnPlus
> grep -ri obstruct src
>

@Digitalink2008

1. I don't see discontinuing it anytime soon. I use it on my server and my server has been around for a year. I won't make any promises, but almost a year so far and no intentions at this point to stop. Worst case, it's part of the reason everything I make it open source, if I ever disappear, someone else can easily take over.

2. HSP does not interact with a jail plugin at all. In theory it wouldn't be much different than my WG interface, but I tend to be pretty lazy when it comes to adding new features because my time is at a premium. So I'd say you're probably best off to just use the WG feature and put one around your jail with a spawn point in the jail. You're also welcome to open an enhancement request for a jail plugin and maybe I'll eventually get to it, or even more welcome to cut some Java yourself and write the code and push it back to me.

@DQone

The only plugins supported for import are SpawnControl and an old version of Essentials. There isn't a lot of demand for additional imports and I tend to spend the little free dev time I have building new features that are in higher demand. That said, the import process is pretty straightforward and there are some good examples if you understand Java, so you can look at the HSP source and write your own and contribute it back if you are so motivated.

Optionally, HSP does have a backup/import format. You can install HSP, create a few homes and then run "/hsp backup". This will create the file "plugins/HomeSpawnPlus/backup.yml". You can then look at the details of this file for the format. If you know how to write a script (perl, ruby, powershell, etc) you could convert your "MultiHome" format into HSP's backup format and then just run a restore to load up all your old homes.