Bukkit

@deleted_6837836

The difference between config.yml and config_defaults.yml is that that the former is simplified, so that it is not overwhelming for new folks. You can freely copy any options out of config_defaults.yml into your config.yml and change them as you like, and config_defaults.yml has lots of examples and comments to help you out.

Your question regarding permissions is: you decide. I know this is a confusing point for some people, but HSP doesn't care what permissions you use. And you can make up your own permissions, neither your permission system nor HSP care.

Let's say you have group A, B and C. Groups A & B you want to have a homeLimit of 1. Group C you want different home limits, different spawns, etc all for just that group. You might choose to assign a permission to groups A & B "hsp.homelimit.1" (I just made that up, you could call it "foo.melon.mushroom" if you want) and assign it to A & B, and then setup per-permission homeLimits for that permission with HSP. For group C, you might choose to assign permission "group.C" and then assign a bunch of HSP stuff to group.C.

@Mayhem777

The strategy you're looking for is "spawnNamedSpawn". You would use it like so:

events:
  onDeath:
    - spawnNamedSpawn:myspawn

This would of course to the spawn you would set by using "/setspawn myspawn".

If you're looking to make it specific to a group/player, then you need to use the per-permission events. If that is your goal, there are examples on the website here and even some available right in the config_defaults.yml.

@morsumka

If you're getting that message, that means there is a strack trace in your server.log. Find that stack trace and look at it. If it looks like it involves HSP, then use pastebin to paste it and link it here or in a ticket and I will look at it.

@LucasFernandesL

It's all documented here on the website:

http://dev.bukkit.org/server-mods/homespawnplus/pages/permissions/#w-permission-systems

Either follow the instructions there to put HSP into op-only mode and then assign the permissions you want (as per the instructions), or go download and use a permission system, there are plenty of good/easy ones to choose from. I don't provide support for permission systems beyond the information listed in the link above.

@Elpres

Look at the full config default file, also always available as "config_defaults.yml" in your plugins/HomeSpawnPlus directory.

If you look at the homeLimits section, you'll see this commented out:

#  permission:
#    limit1:
#      permissions:
#        - my.custom.perm
#        - group.mygroup
#      perWorld: 3
#      global: 10

All you have to do is uncomment, modify the permissions to something that matches one you give to your moderators (make one up, use "group.moderators", "hsp.iLikeHomes", whatever) and then set the limits to what you want and you're good to go.

Also remember HSP follows the order you list and stops at the first match. So if you make one for "group.guests" (and usually permissions propagate upwards, so your mods would have this permission as well), make sure you list it after your moderators entry, otherwise your mods will match that first entry and stop there.

@Mayhem777

Thanks for the report, this is now fix in bugfix release v1.5.4.1. Please, in the future either use pastebin to report stack traces and/or open a ticket with the errors instead of pasting them into the comments here. Thanks!

@ThisUsernameIsMine

It seems like you've got this working the way you want now and at least according to your config, it all looks right.

However, you did ask about core.debug. YAML parameters are often referred to in dot-notation as I did, but it's just referring to normal legal YAML syntax. So "core.debug" means:

core:
  debug: true

@ThisUsernameIsMine

Sorry you're having so much trouble: this plugin makes it very easy to do many things, you're jumping right in with a fairly advanced config (also possible), but it certainly requires some tweaking and testing to get such a config dialed in.

Your verboseStrategy output shows exactly what's happening: strategy "spawnLocalWorld" is being run. You'll notice no permissions-specific strategies that you defined were checked. So either there is a problem with your config not obvious to me from the snippet you posted, or the player doesn't have the permission you intend.

Can you pastebin the entire config? I'll look over the full config you post and see if anything obvious pops out at me, if not I'll download it onto my test server and play around with your exact config to figure out what is happening. I suspect it's a permission issue and it looks like some additional verbose output here might be helpful.

Along those lines, another thing you can try, "core.debug=true", you'll see a line like so printed to your "plugins/HomeSpawnPlus/debug.log":

[5/1/12 8:01:42 AM] [HomeSpawnPlus] evaluateStrategies: INVOKED. type=onHomeCommand player=CraftPlayer{name=morganm}

immediately following that you'll see some lines that show permission-based strategies being evaluated (assuming they're setup right in the config). Something like this:

[5/1/12 8:01:42 AM] [HomeSpawnPlus] evaluateStrategies: evaluating permission-based strategies
[5/1/12 8:01:42 AM] [HomeSpawnPlus] checking permission my.custom.perm
[5/1/12 8:01:42 AM] [HomeSpawnPlus] player CraftPlayer{name=morganm} does have perm my.custom.perm, looking up strategies
[5/1/12 8:01:42 AM] [HomeSpawnPlus] evaluateStrategies: evaluating 1 permission strategies
[5/1/12 8:01:42 AM] [HomeSpawnPlus] evaluateStrategies: permission-based strategies result = [loc={world,119,68,25}, home={id=1,name=world_bed,playerName=morganm,world=world,x=119.3,y=68,z=26,yaw=117.15,pitch=43.95,bedHome=true,defaultHome=true}, spawn={null}]

In your case it should say 'checking permission "group.failnoob"' and iterate through all the permission-specific entries you defined, you're looking to see if the "does have perm" line pops up where you expect it.