Bukkit

@Mayhem777

That is a warning, not an error. It is there because many people run Essentials and then find they can't run HSP commands. There is a comment a page or two back (linked here) that documents how to deal with it. If your home and spawn commands are working as expected (with HSP), then I wouldn't worry about it.

Regarding the conflicts, you just turn it off in the config:

core:
  warnConflicts: false

Make sure you add it to the existing core section.

If you want more help, please post your entire config.yml with your next update (open a ticket and attach it there, or use pastebin). It's much easier than trying to guess what might be going on in your specific environment.

@Mayhem777

Ah, now we have an error we can work with! As you can see in the output you pasted, the crux of the issue is:

org.bukkit.configuration.InvalidConfigurationException: unacceptable character '?' (0xFFFD) special characters are not allowed 2012-11-18 08:53:27 [SEVERE] Caused by: unacceptable character '?' (0xFFFD) special characters are not allowed in "<string>", position 202484

You have a bad character in your config.yml that is causing Bukkit to choke when loading the file and so of course HSP is unable to load without it's configuration from Bukkit.

You can either look for and fix the offending character (or possibly multiple characters if there was file corruption), or if you can't find it, you can just move your config.yml out of the way and restart Bukkit. HSP will see no config.yml and will copy the default one in place - but it should startup fine. Then you can just cut & paste your config sections into the new config, preferably one section at a time and test to make sure it loads so if you copy the bad character you'll know what section it is in.

@Q2Lummox

Ah. If I understand your request properly, it's that you don't want the Minecraft behavior of "fast-forwarding" through the night to take effect when players sleep in a bed, because you have another plugin that lets them heal by sleeping in a bed.

While an interesting request, this is not core to HomeSpawnPlus's functionality, so I won't be adding this feature. You might find other plugins out there that change the way sleeping works that might be interested (or already have) this feature. If not, I'd suggest asking the author of the other plugin since this is much closer tied to that plugins feature set.

@Mayhem777

Wish I could help, but I don't know what "the same error" is. If you're referring to the startup messages related to ebeans, those are normal and you can ignore them.

If there's some other error, we can work with that, but right now I don't have enough information to help you other than to say that HSP 1.7.3 is working fine on many 1.4.2 and 1.4.5 servers, so this problem is unique to your environment.

You can open a ticket here with your problem statement and attach any errors you see in the logfile, as well as versions of plugins and Bukkit you are running and your HSP config.yml file.

A good troubleshooting tactic is to run Bukkit on a test server and run a minimal set of plugins, perhaps just your permissions plugin and HSP. If that works (it will), you can begin to compare differences between your working test server and your broken production server until you find the issue.

@Chaett

Sounds like it's working well then, glad to hear it. I think that's the first reported use case of spawnRegionRandom I've seen. I wrote that one just because I could and thought someone might find a use for it someday - glad someone did. :)

@Mayhem777

Sorry I don't understand what "plugin is red" means and as far as I've tested and heard from others, HSP 1.7.3 is working fine with all recent versions of Bukkit currently available. So this sounds like something unique to your environment and you'll have to do some more research or digging to figure it out, I can't tell what's going on from the info you posted.

Regarding the ebean messages, it is true the ebean server is loaded regardless of what you've configured it as in config.yml. This is a shortcoming of Bukkit, as Bukkit determines whether the ebean server should be loaded based on the plugin.yml "database" attribute. This means it's hard-coded in the JAR and Bukkit provides no way to change that dynamically.

I wrote a pull request a few months ago for Bukkit to resolve the issue (a very simple and clean one to maximize chances of being pulled in), but to date it has not been pulled. Sorry, nothing I can do about it. If you want the ebean server to be off and the messages to go away, you'll have to manually modify plugin.yml to set "database: false" in your HomeSpawnPlus.jar every time you download an update.

@Chaett

Please follow the FAQ for turning on verboseStrategyLogging. This will tell you exactly what HSP is doing. If it's not doing what you expect, you likely have the configuration wrong.

From what I can see of what you've pasted, your config is probably wrong. It should be something like this:

events:
  onDeath:
    - spawnLocalWorld
  world:
    pvp:
      onDeath:
        - spawnNearestSpawn

Your indentation appears to be wrong and with what you have, I expect the only strategy being run is "spawnLocalWorld". verboseStrategyLogging will help you figure out what is going on and tuning it until you get it right. You can live-reload strategies after changing them in the config by running /hsp rc so testing can be very quick to get your strategies tuned to your liking.

@Q2Lummox

I'm afraid I don't understand the ultimate goal. I think just about every possible combination of bed sleeping is covered by the existing flags, they are documented here:

http://dev.bukkit.org/server-mods/homespawnplus/pages/bed-homes/

If you can't get it to work how you want from the flags covered in that documentation, then you will have to re-phrase your question, as I'm not sure what you're trying to accomplish.

Also note that HSP respects shift/sneak-clicking, which bypasses HSP functionality and passes the event straight to Bukkit, so your players could use this to sleep in beds without setting their homes. If you want this behavior to be the default, you can set the config flags appropriately to do so.