Bukkit

@Thyrin

I've not tested it with CommandBook 2.2. Since you're reporting it as not working, my guess is that the format changed. I'll have to download 2.2 and play with it to figure out the new format and then code support for it.

@xVitaminD

If you're trying to use that setting, then that means you're trying to use "ops-only" mode. The details for how to do this are well-documented on the permission page:

http://dev.bukkit.org/server-mods/homespawnplus/pages/permissions/#w-ops-only

@vman411gamer

Look in the config_defaults.xml file under "homeLimits". There is a commented out example for how to assign home limits per-permission. Just copy that section into your config.yml and assign the values as you like.

The permission to assign is whatever you want. You might call it "hsp.homeLimit.2" and then assign that to the groups you want. Or you could call it "xyz.foo.bar", HSP doesn't care, you can make up whatever you want and just tell it what permission to look for.

<<reply 711279="">>

Interesting. I'm not doing anything special to ignore case as part of the import, so it just means the player file Essentials is storing is not maintaining case, so I'll have to do a lookup for an actual MC player name to get the real case. I'll look into it at some point, glad you have a workaround for now.

@xVitaminD

The "default" installation is just that, the default settings, meaning it may or may not be what you want (and more than likely is not). In this case, HSP's default setup is command-less (allows for just bed behavior).

If you want to allow access to commands, then you must grant permission using your permission system of choice. This could be no permission system at all in which case you need to read up on 'superperms'. Alternately, if you prefer the simpler (but increasingly less supported) "op-only" setup, HSP supports that, including allowing you to assign default perms to non-ops.

All of this is described on the Permissions page, it describes everything you need to know, including links to command pages/permission as well as detailed description of how to setup an ops-only system if that's what you want.

@deleted_6837836

The crux of your problem statement in your first post was you wanted to control "which group spawns in what". I gave you the answer to that question, which is that /setgroupspawn in combination with the groupspawn-related strategies control this behavior.

You further clarify this use case in your most recent post by saying "I do not know how to attribute a player into that group" - to which I can only respond by saying this is controlled by your permission system and I don't offer help for setting up perm systems. The FAQ describes the HSP /groupquery command which can show you which group HSP finds a given user in, which might help troubleshoot any group-related issues you might be having.

If that doesn't answer your question, you could provide more details about the scenario/use case you are trying to solve, then maybe I can offer more helpful advice.

@Kidd0Elite

No, I can't help you with that. HSP doesn't edit groups or permissions, it only responds to what you've set. If you can find another plugin (or make one) that does what you're asking (auto-assigns groups on login), then you can use HSP to respond to those groups or permissions to do home/spawn related things.

Same is true for editing groups. Consult your permission plugin documentation. (I don't offer help with permissions plugins, HSP is coded to use them in an agnostic way; you'll have to find support for those plugins from the authors or the Bukkit community)

@deleted_6837836

GroupSpawnCommand is on the strategy page, and it ties to "/groupspawn". Primarily this feature is a legacy from the original SpawnControl, which had "/spawn" and "/groupspawn" commands, and they weren't related at all. With HSP strategies, you can make "/spawn" do whatever makes sense for you, so "/groupspawn" is largely unnecessary. But who knows, you might want to have both (ie. /spawn takes you to world spawn, /groupspawn takes you to your group spawn). You get to decide.

You set a group spawn by typing /setgroupspawn GroupA, you can query what group HSP finds a player is in by typing "/groupquery player". If player is in GroupA and you enable access to /groupspawn, then when they type /groupspawn, they would be sent to the spawn you set for GroupA. You can also use a few groupspawn-related strategies elsewhere, such as onDeath, onJoin, etc.