Bukkit

@DarkRyuZ7

@Gunnerrrrrr has it right, look at his example. The only additional point I would add is that it's generally better to list "highest first" to avoid permission inheritance problems. You can read more about it here.

@DarkRyuZ7

Use the homeLimits section of the config. Something like this:

homeLimits:
  default:
    perWorld: 1
    global: -1
  permission:
    entry1:
      permissions:
        - donator
      perWorld: 2

In this example, the default says each person on the server will be allowed 1 home per world. Then anyone with the permission 'donator' would be allowed 2 per world.

You can make the permission whatever you want and use your permission system to assign it to whatever group you are putting these players in. Or whatever makes sense for your intended setup and permission system.

@TheFlannelBeard

For #2, just go to each world and run "/setspawn" wherever you want that worlds spawn to be. Then in your strategy config, use:

events;
  onSpawnCommand:
    - spawnLocalWorld

Now when they type /spawn, they will be teleported to the spawn for their local world. If they are in a world without any spawn, nothing will happen. If you want them to go to the local spawn if there is one and then to default spawn if not, just add spawnDefaultWorld after spawnLocalWorld to your strategies.

Regarding "/deathspawn name", this capability already exists, in two forms. One is you can give your players the ability to spawn at named spawns, so they can just type "/spawn church10" or "/spawn deathspawn4", whatever you name them. If you actually want a "/deathspawn" command that would work just like your graveyard spawn (and you could even add a warmup or cooldown), then just make your own deathspawn custom command.

@TheFlannelBeard

Sounds like #1 and #2 are fine and your only question is #3?

If so, the answer is: sort of. HSP has a spawnNearest strategy, which will pick the nearest spawn to the player. So if the only spawns you have in the world are church1 through church 10, then yes, that will work. If you also have other spawns, such as a newbie spawn and some other spawns, then they could spawn at those as well if they die nearest to them. So if it's a world that only has your church spawns, you're good.

If what you want is to spawn to the nearest spawn, but you want to define the spawns (ie. church1 through 10, but not spawn1, spawn2 and newbie_spawn), then a strategy could easily be created to do that, but one doesn't currently exist.

@saxamafonet

It is not possible with anything in HSP today, although in theory it could be added with a mode. This functionality is probably better controlled in WorldGuard which has facilities for including and excluding commands, although I'm not sure if it lets you set an exclusion based on membership, but it's certainly a feature they could add.

Regarding Feed the beast and MCPC, I have never tested this. Specifically I saw one other report of MCPC not working, but the stack trace provided indicated a possible missing EBEAN implementation. If you have a stack trace you can pastebin when your server shuts itself off, that might be helpful in tracking down the issue.

@Enkious

What you listed looks fine. Feel free to experiment on a test server, or if you don't have one, HSP supports live-reloading of most config options, event chains especially, so you can tweak it, run /hsp rc to reload, test it; tweak some more, reload, test, etc. A good way to test would be something like so:

events:
  permission:
    test:
      permissions: [my.test.perm]
      onSpawnCommand:
       - spawnRandomNamed: name1, name2,...

In this example, anyone with the permission "my.test.perm" (which you could assign just to yourself for testing) will get the listed event chain when running the /spawn command. You can test it out to make sure it works how you like, then move the chain up under your onNewPlayer event, which obviously is much harder to test since you're only a new player on your first ever login. :)

Regarding the onJoin/spawnNewPlayer question, it won't ever get invoked. A player is only new on their first ever login, if you have an onNewPlayer event defined, that is what will get called. Similarly, I wouldn't expect your onDeath to work, since the player probably has a player file by the time they die (and therefore isn't "new" anymore).

Perhaps your intent is to have them go to the same random spawn they originally spawned at if they die? If so, yes that is possible with HSP, I can write an example for you if this is what you are trying to accomplish.

EDIT: oh and your last question, the command is /setspawn name1, although I think ThisUserNameIsMine may already have answered with a link to the actual command.

@shon33

I don't know what mcpc-plus is, sorry. The error you posted suggests it might not support Ebeans, which HSP uses (it comes bundled with Bukkit). You can try changing your HSP core.storage to YAML instead, which will avoid the ebeans dependency. Be warned that this might be slow on very large installations, but performance should be ok up to a few thousand homes or so.

@ThisUsernameIsMine

Quote:

but CrazyLogin (or bukkit) still has priority over HSP

It's been a while, so I may not remember the details perfect, but I thought your issue was that you wanted CrazyLogin to have a higher priority, which is why you asked the author to change to MONITOR priority? By changing your HSP core.eventPriority to "high", CrazyLogin will have a higher priority.

If your problem is as you describe, in that you want HSP to have priority over CrazyLogin, then you may be out of luck. HSP allows you to change the priority, it's default is HIGHEST. If CrazyLogin is also HIGHEST and is getting the events instead, then unless the CrazyLogin author allows you to change the priority in the config like HSP does, you don't have many good options. You can try renaming the plugins so Bukkit loads them in a different order, it might affect which one gets final say.

Bukkit really doesn't provide a good way for server admins to manage plugin event conflicts. I went out of my way to add support for HSP to be controlled by a config option and I've not seen many other plugins that do this. You could ask the CrazyLogin author to add it.