Bukkit

@HeavenMc

Of course. You're looking for the onSpawnCommand event and the spawnSpecificWorld strategy in combination with a world-specific strategy. Or you could use spawnNamedSpawn if you have multiple spawns on a world and want to choose a specific (non-default) one.

Something like:

events:
  world:
    skyblock:
      onSpawnCommand:
        - spawnSpecificWorld:Main-World

All of this is documented on the strategy doc and the How HSP works pages if you want to read the details or explore other options.

@ccman972

Ah, now we have something to go on! Your results show that HSP is being invoked correctly, so this isn't a command mapping problem.

I see that when the player types /spawn, HSP goes through the evaluation chain you specified, which starts with spawnLocalWorld. On that world (Main), you have done a /setspawn at the location -1, 65, -1. This is where HSP is attempting to send the player.

Is the player going somewhere else or staying put? Is -1, 65, -1 a safe place to teleport? Is there anything else in the log (errors, perhaps?) at the time /spawn is typed?

@ccman972

With the exception of the one time I commented about your lacking problem reports (whereupon you uploaded your entire plugins directory), your problem statements have given me nothing to go on and you've shown no interest in helping yourself by posting results of having run through the FAQ or posting error messages, screenshots or confirming permissions. You simply post saying "X doesn't work" with no additional troubleshooting information of your own. It's a waste of my time.

Despite this, I have gone out of my way to load up your configs that you finally uploaded, spent my personal time poking around in your environment looking for issues and through extensive testing, even managed to find a bug and fix it (which you never reported). I posted back that the bug was fixed in a dev build and for you to give it a try, and you've not done that.

At this point I've put in hours of time responding to your messages, downloading and testing your custom configs and even publishing special dev builds for you, and the results I get back are "/spawn isn't working" and a few days later "are you still working on my problem?".

No, I am not and no I will not. You need to put in some time to troubleshoot your own problem or move on from HSP. I don't want you as a user if all you're going to do is suck up my time with repeated useless problem statements that don't have enough information to be solved.

If you're ready to put in some effort to fix this issue, then lets start from zero. Go read the FAQ, follow the instructions there. Download and use the dev build I put up for you. Come back here and post a ticket detailing exactly the steps you have followed in trying to troubleshoot the issue. If you show me you've gone through the FAQ and if you share enough information for me to help, I will; if not I will respond with "keep trying".

Things for you to do: verboseStrategyLogging, /permcheck permission verification, using bukkit.yml aliases to map to "/hspspawn" (on the dev build), capturing a screenshot of any error, posting any stack traces that show up in your logs and sharing any debug.log information if none of that works.

@ThisUsernameIsMine

CME (ConcurrentModificationException) is multithreaded programming bug; for Bukkit this happens most often when a plugin does something on an asynchronous thread and tries to use the Bukkit API (which is 99.9% not thread safe). The problem is concurrent bugs like this often don't show up during testing; the code "works" fine 99 times out of 100 or 9999 times out of 10000, but it's that one time it doesn't that you get a CME and your server blows up. Plugins that use Async scheduler tasks or that start their own Threads are suspect.

HSP only does this in two places, one is in the HSP Convert process. This is to avoid locking up the main thread when doing a large conversion and it's a one-time use thing and clearly isn't the source of your problem. The second is in the Metrics plugin from Hidendra, this is asynchronously pushing updates to mcstats.org. This is well studied code and used in many plugins and in no way does any thread unsafe accesses to Bukkit.

So, you need to find which plugins you have doing asynchronous scheduled items (or their own Threads) and pick the most likely offenders and turn them off one at a time until your problem goes away. If you do this and manage to conclude that HSP is actually the culprit, I will entertain the idea with an exhaustive code audit, but since my search for async only shows those two cases, I'm already 99.99% sure HSP is not the cause of your issues.

FWIW, I reboot my server every 24 hours anyway (on a schedule during low times). Reboots are fast and for any server running more than a few plugins (recognizing many plugins are written by folks that are new to Java, and even those that aren't are rarely tested to the quality standards of Enterprise Java code), it's probably a good practice to do this just to keep things running smooth.

Good luck.

@Apple_columb

That's just the Bukkit EBEAN server shutting down - I have no control over those messages. They are benign and can be ignored.

@Hangar

Thanks for the update, good to know. I'll work on packaging a release up soon and update the web docs to describe the bukkit.yml alias method so new folks can use this method to eliminate plugin command conflicts as well.

@ccman972

Unfortunately, your problem description doesn't have any additional details for me to work with. Fortunately, you DID send me all your configs, so I fired up a local test environment with your configs and tried to reproduce the behavior. I don't see any 'sending to spawn' messages (HSP only recently added these and you don't have them turned on in the config options) and I don't see any permission issues.

What I did see was this stack trace when I tried to /sethome: http://pastebin.com/ZeS6uqQj And the accompanying Bukkit 'error' red text in the game console when exceptions like these happen. Did you see this at all? If so, it would be much easier to fix issues like this if you find and pastebin stack traces when they happen.

The stack trace was a result of your economy (Essentials, I think) printing "$50" or whatever the cost was. The $ trips up the Java regex unless replacer for localized messages. So I added code to be sure it's properly escaped and now I can /sethome, /home and /spawn in my local test environment, using your configs. You can download a dev build with this fix from the Changelog page.

Let me know if it fixes your issue. And if not, please open a ticket and include as much detail as possible. Stack traces, screenshots, even another full dump of your current configs. With the existing plugin dump you gave me a week or so back and the above dev build, HSP is working fine for me now.

@ccman972

I thought your issue was fixed? If you still have the home/spawn command conflict issue, then yes, there has been progress. Use the current dev release (on Changelog page) and use Bukkit aliases. For example:

# bukkit.yml
aliases:
  home: hsphome
  spawn: hspspawn

I'll restructure the documentation to include these details for new people, but this is basically the gist of what you have to do. This is a set-and-forget, you can upgrade HSP or other plugins and your home and spawn will always map where you intend.

@Linyrae

Please open an enhancement ticket and describe the functionality and use cases you have in mind. I'm not promising to implement anything, HSP has quite a few external dependencies for me to track against as is. However if the use cases make sense I may consider it.