Bukkit

@Shvesley

Ah. You need to confirm that a worldborder is set for the world you are trying to randomSpawn on. From what I read, your HSP configuration is fine. When a new player logs in, you want them spawned into a random location in world "wasteland".

What I said in my earlier response is that the stack trace you shared (thank you) indicates to me that you haven't set a world border for wasteland. This means if you run "/wb list", you will see that your world "wasteland" has no border set. Set a border, I believe the problem will go away.

If you can see that you DO have a border set for wasteland and you're still getting the same stack trace, please open a ticket here with all the details, such as your HSP, WorldBorder and Bukkit versions, the output of "/wb list" and your HSP config and I can attempt to reproduce the issue, the assumption at that point being that it's not the issue I currently think it is.

@ViscousSummer88

There are a few things to do:

• Read the FAQ to be sure you assign /spawn to HSP so Essentials isn't stealing it.
• Make sure the intended players have the right permission (hsp.command.spawn)
• Go to your intended spawn location and run "/setspawn" (or /hspsetspawn if Essentials is stealing it and you haven't fixed it from FAQ above)
• Set your onSpawnCommand event to use spawnLocalWorld strategy. This is actually the default setting, but good to double-check this is set properly. Use core.verboseStrategyLogging to see what HSP is doing if you're getting a different behavior than you expect (also covered in FAQ)

Good luck!

@Shvesley

I don't offer support for other plugins, sorry. I think WorldBorder has a reasonably well documented project page, so please review that and ask the author for help if the documentation isn't sufficient. Or if you don't understand it (and therefore aren't using it), you might consider uninstalling it.

If WorldBorder isn't installed at all, HSP will just default to -1000 through 1000 for random world spawning.

@tuxed

There were no breaking changes between 1.5.1-R0.1 and 1.5.1-R0.2. Nonetheless, I tested a build of 1.5.1-R0.2 so you can find that on Jenkins if you like.

@Shvesley

Thanks for using pastebin and including relevant config section. Based on the stack trace, my assumption is that you have WorldBorder installed but you've not setup a world border for the world in question. I don't believe I ever coded for this situation and I doubt it's what you want: if I coded HSP to accept an infinite WorldBorder, your players would be randomly spawning in an near-infinite world: from -30,000,000 to +30,000,000 X/Z.

If this really IS what you intend, then just set your WorldBorder to those limits. Be warned, since it is impossible you've pre-genned all 262,144,000,000,000,000 blocks (262 quadrillion) in the -32mil by +32mil MineCraft world, it means every new player login will be slow as your server freshly generates all 441 chunks around the player (10-chunk radius) as every one of them logs into a new, previously ungenerated location on the world.

If you HAVE set your WorldBorder limits on the world in question (meaning this is a bug of some sort and not the situation I described), then please open a ticket here with your stack trace and a listing of your WorldBorder limits and version and I will try to reproduce.

@ThisUsernameIsMine

Note that plugins are NOT supposed to change events using the MONITOR priority. Please don't ask the plugin author to do this.

HSP has gone to great lengths to allow you to modify the priority of the event for exactly this situation (Bukkit does not make it easy for plugin authors to allow admins to change this). Change your core.eventPriority from "highest" to "high". Then if the other plugin uses "highest", you'll be fine.

Since you are intentionally doing this, you can further tell HSP to stop telling you about it by setting the core.warnLocationChange setting to false.

@Consalvo

You say "Bukkit 1.5.1" and "HSP v1.7.4". These two are not compatible. Use the dev build from Jenkins, or wait until Bukkit admins approve v1.7.5 that I just uploaded a while ago, which is compatible with Bukkit 1.5.1.

@Eternity74

Please read the FAQ, it specifically covers command conflicts. HSP has a dynamic command system that Essentials does not play well with, since Essentials assumes all plugins have their commands enumerated in plugin.yml and HSP doesn't; admins are free to add/remove commands to HSP through configuration.

Specifically, this means if you have HSP and Essentials installed together, Essentials command system is installing itself over HSP /home. There is a very easy step to resolve this, please read the FAQ.