Bukkit

@bukOhTwo

Just so I understand: you're saying your previous post permissions weren't working and you were getting a syntax error message, or you were getting a no permission allowed message?

And in any case, adding Vault fixed the problem? That is odd. What permission system?

Regarding sethome and bed, there's currently no way to do that although I suppose all the code exists so I could add it, sethome would just have to respect the "modeRequiresBed" flag. It was primarily designed for SP no-command use case where players right click on a bed to set home (thus impossible if no bed), and the "modeRequiresBed" strategy will not spawn a player at a home unless there is a bed within 5 blocks.

Which works the same with /sethome. While it would allow them to SET a home even if no bed in 5 blocks, but if you put modeRequiresBed in your strategies that use homes (such as onDeath or onHomeCommand), they won't be able to use that home if there is no bed or the bed is destroyed, etc.

@ThisUsernameIsMine

They might be missing from the page, I'll have to check and make sure all the commands/permissions are up-to-date. However, the pattern is the same for all commands: /home is "/hsp.command.home", /sethome is "/hsp.command.sethome". So, groupspawn should be "hsp.command.groupspawn".

Thanks for pointing out it's missing on the documentation, though, I'll try to get that up to date soon.

@bukOhTwo

Thanks for the report. As per the comment just below yours, please try the latest dev version. It only has one change from the current release and I believe it will fix the issue. It would be great if a few folks having problems would try this dev build and report back whether the issue is fixed or not. Thanks!

@andune

Would those who have reported issues with HSP commands please try the dev 1.7.2 release which can be found on the Changelog page. I suspect it will resolve the issue.

However, I would also very much appreciate those who have had the issue reporting in on OS and JVM combinations. I've been unable to reproduce the issue in any of my local test environments and I've tried very hard to do so - but I don't run Windows on any of my machines (I don't even have one to test on - Linux & Mac only). It would be helpful to know if all the folks who have issues on 1.7.1 are Windows users.

@gabe323

Thanks for the report. It's clear from people reporting in that there is a problem, but I'm unable to reproduce it locally so that I can resolve it. More information would help so that I can reproduce and resolve the issue.

If you are having an issue with HSP 1.7, first, please know that you can just install 1.6.3 and use HSP fine as before, the only thing you miss out on is new HSP 1.7 features. But if you are having an issue, I would appreciate you going to Ticket #135 and adding details about your installation so I can track it down.

As best I can tell, there is no conflict between Essentials and HSP. My working assumption at this point is that there is another plugin (or plugins) common to installations that are not working. If I can find a common plugin, I can install and reproduce the issue and resolve it.

@Techwiz100

Invert your VIP permissions, list the most important first. HSP processes the list in order, and it's likely that your "vip10" users also inhereit your "vip5" permissions, so HSP checks "vip5" and stops there. Reverse it so "vip10" is listed first and it should work as you expect. Further reading on this behavior is in the online docs here.

To confirm my hypothesis (short of just making the change), you can run "/pc homes.vip5 playername" where playername is one of your vip10 users. My money is on it returning TRUE that they have the "homes.vip5" permission.

@khobbits

Actually, the whole purpose of HSP dynamic command registration is EXACTLY to play nice with other plugins. And it appears to play fine with Essentials, and I see you're jumping through hoops to try to accomplish similar "play nice" in Essentials as well.

The two big advantages to HSP's new dynamic command system are:

• Admins can disable commands in config and it really works. The command is completely disabled, so other plugins can register the command without Bukkit assigning it an "alternate label" and the command is not sitting around hidden as "/ehome" or somesuch. This setting is not lost when the admin upgrades to a new version and forgets to hack up plugin.yml again.
• Admins can create new HSP commands in config. If an admin wants to define a "/randomspawn" command, he can do so. My first cut at this actually used extended attributes on plugin.yml, but it had the aforementioned downside that every time an admin upgrades, they have to remember to hack up plugin.yml. Crappy implementation from an admin perspective.

Unfortunately Bukkit does not provide a robust dynamic Command facility, so plugins that want to provide their admins with more control have to work harder to do it (I see Essentials is no exception). I think CommandBook does it well and only wish sk89q had actually released his plugin framework for everyone to use. In the meantime, HSP's system serves the purpose well until Bukkit (or Mojang official API) publishes a better way for all developers to do it in the API.

@Mayhem777

I never said other people weren't, only that with the information available to me (you're using Essentials and HSP), I'm not able to reproduce the issue. If I can't reproduce it, it's very difficult to fix it.

OriginalMadman reports he is using CommandBook. @Mayhem777, the error message you said was printed out seemed more like a CommandBook error, do you use CommandBook as well?

I'm a CommandBook user myself so for those of you having issues, as per my previous post, please share as much detail as you can (use pastebin): such as a full plugin list with versions (use the excellent PlugMan plugin and type "/plugman vlist"). Please share your HSP config and if you're running CommandBook, your CommandBook config as well.

Also, please share the exact behavior happening. OriginalMadMan says "the commands don't work at all" - do you get a permission error? Any error message? Or just silence?

There seem to be many people using HSP 1.7+ successfully (my own server included), so there is something unique in your environments causing the issue. I will be happy to fix it if I can reproduce the issue and track it down. Need more info, please!

@diannetea

To try to reproduce the issue, I installed Essentials on a test server tonight. I confirmed Essentials standalone behavior: /home and /sethome worked. I then installed HSP 1.7.1 (fresh install, no config changes, no usurping) and HSP /home and /sethome worked fine. Here is what I tested with:

>version
23:09:15 [INFO] This server is running CraftBukkit version git-Bukkit-1.3.1-R1.0-b2320jnks (MC: 1.3.1) (Implementing API version 1.3.1-R1.0)
>version Essentials
23:09:18 [INFO] Essentials version 2.9.3
23:09:18 [INFO] Provides an essential, core set of commands for Bukkit.
23:09:18 [INFO] Website: http://tiny.cc/EssentialsCommands
23:09:18 [INFO] Authors: Zenexer, ementalo, Aelux, Brettflan, KimKandor, snowleo, ceulemans, Xeology, KHobbits, md_5 and Iaccidentally
>version HomeSpawnPlus
23:09:22 [INFO] HomeSpawnPlus version 1.7.1
23:09:22 [INFO] Author: morganm

So according to my testing, Essentials and HSP play nice together and there are no issues. @diannetea if you want further help with this please open a ticket and include relevant info such as: 1) full plugin list with versions 2) HSP config.yml 3) screenshot of the misbehavior (so I can see exactly what is happening). 4) bukkit.yml

Here is an example ticket that included all relevant information and I was able to reproduce and resolve the issue as a result. Ticket #131

Beyond you providing more info, I can do nothing further as I cannot reproduce your issue in local testing.

@khobbits

Ah that was directed at me. So it seems Essentials does some interrogation of other plugins "plugin.yml" files and acts differently based on what it finds. It seems I will have to do some work to Command Usurping then specific to Essentials in light of this.

As to why HSP 1.7 plugin.yml doesn't contain commands, it's because they are dynamically registered now, much like CommandBook (notice their plugin.yml is devoid of commands these days, too). This lets admins turn on/off HSP commands through their config.yml so they don't have to remember to open and edit plugin.yml every time they update HSP. (A personal annoyance of mine from back in the days when I used to run Essentials, sounds like you have a better system now)

@diannetea

The way HSP 1.7+ handles command registration has changed, specifically to allow for custom commands and also to now allow you to completely turn off HSP commands if you want (some people do). So, there's a LOT more flexibility in the 1.7 command system.

However, I did notice in my testing that the way commands are registered now seems to have some impact on the Command Usurping system I built, which in truth is somewhat of a hack that I built in order to make HSP users' lives easier since there are so many "uber command" packs that often have /home, /spawn, etc commands (such as Essentials and CommandBook).

Always the "best" way to alleviate command conflicts is to either edit the plugin.yml or config files of conflicting plugins, or to monkey with Bukkit aliases (for example, you could alias "/home" to "/hsphome" and it will always work, regardless of how you switch around your plugins).

But in the interest of making it easy for HSP users, I have Command Usurping, and it sounds like you were depending on that feature and it's no longer working the same. I specifically fixed it (and confirmed with testing) for CommandBook in HSP 1.7.1, but I've not run Essentials for a long time and have done no testing with it.

Interesting that it works in 1.6.3 and not in 1.7, since the Usurp mechanism for HSP didn't change at all, the only thing that changed is the way that HSP registers it's own commands.

In any case, plenty of options for you to fix the conflict between Essentials and HSP, feel free to choose any of them. When I get a chance, I will do some specific testing with Essentials and HSP Command Usurping and see if I can figure out what's going on and fix any issues.