Bukkit

@justinwl

/spawndelete is the HSP command for deleting a spawn (as documented on the commands page).

This can be used to delete HSP spawn points, if any exist. There is also a Minecraft/Bukkit spawn point for each map, and as far as I know, there is no way to delete it. If your HSP strategies fail to send the person somewhere, the event (in this case, the respawn event) will just fall to Bukkit to process, which of course will just send them to the Minecraft map spawn.

So we come back to: if someone dies on your minigames world, what is it you want to happen? Let's say you deleted both the HSP spawn and found some way to hack Minecraft/Bukkit and delete the world spawn, so now NO spawn exists on that world. What is it you expect to happen? The player dies and ends up in a timeless void? Are they supposed to go to their home? Or perhaps a home or a spawn on another world?

Figure out what it is that you WANT to have happen and then build an HSP event chain that does that. That's what HSP is for.

@justinwl

There are many examples to help you out.

The first thing is to decide what you WANT to happen instead of what IS happening. You didn't describe what you want to happen, so I can't really help. Whatever it is you want to have happen, chances are good HSP can do it, look at the examples and have a look over the events and strategies for all the possibilities.

@MrCleanIsDirty

If you're running the latest snapshot from Jenkins, that error makes no sense as that line should never be null. And if it is null, it is a very odd bug. But if you're running a different version, then it could be a different line and I might have a more immediate answer.

In any case, please open a ticket and include your exact Bukkit version and HSP version (both printed out at server startup) and this stack trace here so I have the context. Also a list of plugins you are using is very helpful and if you do anything specific to make the stack trace happen.

I can then make sure I'm looking at the right source code and try to replicate the problem to help troubleshoot the issue.

@Sordrin

Ah, that's good then. We've ruled out the most common issue of some other plugin eating your /home commands, so we know it's HSP getting your command and just need to fix your strategies. The best do-it-yourself method for this is to turn on core.verboseStrategyLogging and HSP will tell you exactly what it is doing when you type /home.

My best guess from your description is this:

You have homeMultiWorld as your only strategy. homeMultiWorld is a shortcut strategy for homeLocalWorld followed by homeDefaultWorld. I'll setup a scenario that I assume is similar to yours and might explain what is going on.

HSP has a core.defaultWorld parameter, let's assume for this example you've set this to a world you have named default. Lets assume a second world called secondWorld where you have run /sethome and so you have a home on secondWorld. Now let's assume you're standing on thirdWorld (your "local" world when you run /home). You have no home set on default or thirdWorld, only the one you set on secondWorld.

When you run /home standing on thirdWorld, HSP runs the homeMultiWorld strategy which checks first for a home on the world you're standing on, thirdWorld. Nope, no home there. HSP moves on and checks the default world, which in this example is default. Nope, no home there. HSP moves on to the next strategy. There is no next strategy, so you hit the end and get the 'No home found' message.

Assuming this describes your situation, great, now we know the problem. How to fix? Decide what you want to happen and then put in the strategies to match. The easiest might be just to add homeAnyWorld after homeMultiWorld, so a player will first be sent to a home on the local and default world (if any), or as in this example where they have none, homeAnyWorld would find the home that was set on secondWorld.

This might not be what you want if you have five worlds and want /home to work a specific consistent way, or perhaps work one way on one world and a different way on another. HSP leaves it to you to decide how you want it to work, but if you just want /home to "always" work as long as a player has a home defined somewhere, then adding homeAnyWorld as a last-ditch strategy is a good plan.

@Sordrin

Are you running other plugins that also have their own /home command, Essentials perhaps? If so, please read the FAQ, it will help you troubleshoot and fix this issue.

@Sargewood

The latest dev release on Jenkins works fine against 1.7.5 (just tested), in fact it works as far back as build #49, built Jan 11.

When the current dev build on Jenkins is released here on DBO, it will relieve the issue of HSP breaking with every MC/Bukkit version change since the CraftBukkit dependency has been eliminated.

@NoHoPeLess

Yes, first step is to use /hsp backup to backup your database.

Then change your core.storage to ebeans, setup your bukkit.yml to point to mysql and then restart your server. HSP will initialize the database, it will be empty.

Then run /hsp restore OVERWRITE. This will restore your database from the backup file you took just a few minutes ago, of course restoring to your newly created MySQL database tables.