Bukkit

@SXRWahrheit

Thank you for including the verboseStrategyLogging output. From that, I can see that the only strategy you have defined is "spawnNewPlayer". In this example, the player is not a new player and since that is the only strategy you've defined, HSP is doing NOTHING (returning null).

This means either some other plugin is responsible for the behavior you describe, or it's possible it's just falling through to the normal Bukkit spawn point. You can use HSP's "/setmapspawn" command to change that if you like, and "/spawnlist -m" to see the Bukkit map spawns.

@Veinlockx

Use the modeRequiresBed strategy. If your setup is simple, just apply this to your default events at the top of your strategy chains and you're good to go. If your setup is more complex, this allows you to use this on just a specific world or just with specific groups of players, whatever you like.

@Unpluggeddk

If this still isn't working, please open a ticket and include: your Bukkit version, your HSP version, your Vault version and your economy plugin of choices version. Also please confirm in the ticket that you've seen your economy of choice work with other plugins immediately prior to this error and what plugin(s) those were.

(background: with this info I might be able to help you, but do be aware that HSP's economy code is very light because it punts all the work to vault. So I'm most inclined to think it's an issue with your configuration, but once I have all the facts and can reproduce the issue, I'd know for sure)

@Unpluggeddk

HSP does not have and likely never will have any sort of region definition commands. There are plenty of other plugins out there that do this very well. In fact, to your specific question, I do believe WorldGuard has the capability to refuse commands in certain regions, so I believe it will do exactly what you want.

Another option, if you have a plugin that can toggle permission nodes when players go in or out of a region (maybe an advanced permissions plugin has this ability?), you could always remove the "hsp.command.sethome" permission while in region.

@Edyi3

Sorry, the image you posted doesn't show up. Try using pastebin?

@Tecurotranki

I've checked in code and the permission check is there:

https://github.com/morganm/HomeSpawnPlus/blob/master/src/main/java/org/morganm/homespawnplus/command/BaseCommand.java#L134

This short-circuits the costs that commands charge and just returns success if the exempt permission is present. I know this works on my server and I've not changed this code in a long time, this works as far back as pre-1.0.

So the only remaining possibility is that the users you are testing don't actually have this permission when HSP checks for it. I've added a "/permcheck" command in future HSP to help debugging this (much like /groupcheck), but meanwhile any permission system worth it's salt should be able to run a perm check query. For example, for PEX this is:

/pex user bob check hsp.CostExempt.home

@Tecurotranki

There's a special permission you can give to override costs (documented on permissions page):

hsp.CostExempt.<command>

So if you want your mods/admins to be exempt from all costs, you can just give them the "hsp.CostExempt.*" permission.

@stevevbrewer

I'm not aware of anything HSP is doing that should be overriding Essentials behavior regarding first-time login announcements. HSP doesn't monkey with the announcements or the event in any way except to change the location. So unless Essentials is doing something funny such as monitoring to see if the location changed on PLAYER_LOGIN and not sending a message in that case, it shouldn't be affected.

Unfortunately it's not very easy to test as I'd need to setup Essentials, figure out it's new player detection (so as to be able to reset it) and then a second account to actually do the testing with.

@Mayhem777

No worries. I don't mind helping, but people whining about support that is provided completely for free is a hot button of mine. ;)

So it sounds like you figured out the problem? From what i saw in your original post it looks like you had "spawnNewPlayer" after "spawnLocalWorld", and spawnLocalWorld is likely to return a location so "spawnNewPlayer" never gets run as a strategy. That all should show up in the "verboseStrategyLogging" documented in the FAQ.

Another thing to check is to "/spawnlist -m" which will show Bukkit map spawns in addition to the HSP-recorded spawns. If you notice your players are spawning at the Bukkit map spawn, you can either adjust your HSP strategies and use "/setspawn" to set HSP spawn correctly, or you can use "/setmapspawn" command to change the Bukkit map spawn as well, if you like.

@pjrueda

If you downgrade a player to a lower limit, there is no provision for "deleting" excess homes over the new limit, they simply will be unable to add a new home since they are already over their limit.

As an admin, when taking such action, you can use /hlo (/homelistother) and /hdo (/homedeleteother) to do this manually if you like. And there's always the ability to manipulate the database (or YAML files, depending on which you use) directly as well.