Bukkit

@Mayhem777

Note 1.7.1 is released. Assuming you mean 1.7.1, then you'll need to share more details, because I've tested it and know others are running and it is working. Did you have HSP 1.6.3 working prior to installing 1.7.1? Have you changed anything else in your environment, such as other plugins or permission systems?

You mention OP, are you using a permission system? If not, have you read how to use HSP with ops-only?

Are some commands working but not others? What is your plugin list? Do you have any verboseStrategy or debug logs to share? So far in your two posts the most detail you've offered is "it doesn't work". All I can do with that is tell you "it does work" and that it is most likely a problem with your config, which I won't be able to help with until you share some details that will help me reproduce, diagnose and otherwise troubleshoot the problem.

@diannetea

It is most likely you have some other "/home" system causing that. Do you run Essentials or CommandBook? Try typing "/hsphome" instead, see if that has the intended effect. If so, look into Command Usurping or use whatever facilities the other plugin has for turning off conflicting commands.

@ThisUsernameIsMine

This is because you are no longer using Vault or WEPIF. Vault is smart enough to hook a permission system (such as bPerms) to use it's native groups, which HSP leverages for the "groupspawn" functionality. Superperms (aka Bukkitperms or Dinnerperms) have no concept of group, so there is no way to "get group" from superperms. Originally this meant HSP did not support groupspawn for superperms, since no capability exists.

However, a convention emerged which was to apply permissions like "group.guest" via superperms to your groups. HSP respects this convention, so you can use those permissions to identify your groups and HSP will find them.

Another path forward might be to figure out what was wrong between Vault and bPerms in the first place that you went away from it. I know codename_B and Sleaker, both are good guys so I'm sure if there's a bug that you can reproduce, they'd be able to fix any issue quickly.

ps. Note the FAQ identifies a command you can use: "/groupquery player" to identify the group HSP sees a player in. If you run this now, you'll see it returns nothing for your players, which is why they aren't matching any of your groupspawn strategies.

@ThisUsernameIsMine

If you're using bPerms and want to bypass Vault/WorldEdit perms, then just add this to your HSP config.yml:

permissions:
  - superperms

This tells HSP to just use superperms permissions and not Vault/WEPIF. Let me know if that works for you.

BTW I've tested HSP with both the latest versions of Vault and WorldEdit and it works fine for me. But I don't use bPerms so maybe there's a conflict between one of them and bPerms, I don't know.

v1.7.1 has been released which fixes all known issues that have been reported with v1.7 so far. Those of you who were having problems, please download v1.7.1 and let me know if you have any issues, or I even appreciate positive confirmation that any issues you had are fixed. Thanks.

@ThisUsernameIsMine

Ah! You're saying it's a permission issue? That's different than your original problem report led me to believe. This could make sense. The new dynamic command system sets the permission on the command which Bukkit would use superperms to enforce. But this would be different than how 1.6.3 did it. I see you're using bPerms and you say the fix is to call out each HSP node explicitly. What were you doing before?

UPDATE: I've uploaded a new dev build which no longer sets the Permission on the PluginCommand object. Please download and let me know if this fixes your problem (link in Changelog).

@ThisUsernameIsMine

Thanks for the detail, that helps a ton. It looks like maybe the "default" command chains are not being invoked. To test, can you add this to config:

events:
  onNamedHomeCommand:
    - spawnNamedSpawn

Please let me know if this fixes your namedHome issue. Meanwhile I'll do some local testing around this hypothesis.

I've put in some time to get the Strategy doc updated with lots of new info regarding new v1.7 features.

I've taken to tagging new features with the version they were introduced, so if you're interested in just reviewing new events & modes available to you in 1.7, you can use your browser to just search the page for v1.7 to skim through new features.

I also have examples of new multiverse/worldguard integrations as well as the new custom commands feature.

There are some early reports of some commands no longer working after people upgrade to v1.7, but no one has yet given me details such as what plugins they are running, their config.yml or verboseStrategyLog details. If you have upgraded to 1.7 and are having issues, I would appreciate this detail. If you've upgraded to 1.7 and are not having issues, that would be a good data point as well.

If you are someone having issues, you could try downloading 1.7.1 dev release, which is a stable (but not-yet-released) version of 1.7 with some bug fixes. See the Changelog for details and download link.