Bukkit

@ThornRage

The workaround is here. Put that into your config.yml and there is no need to wait, the problem will be resolved. The same info is also listed in the Known Issues section for v1.6.2 download.

Well the comment jump isn't working, so just including fix inline here. Add this to your config.yml:

core:
  reloadChunkOnTeleport: false

@Gunnerrrrr

If your goal is to make your faction and HSP home the same, why not disable faction homes?

If that's not possible, then check out CommandHelper: using it you could make it so someone typing "/f home" would get remapped to just "/home" (and therefore picked up by HSP rather than factions). In fact, it think this would even work with Bukkit aliases, no other plugins required.

http://wiki.bukkit.org/Bukkit.yml#aliases

@Mayhem777

Same comment as to Jobsti: please create an enhancement ticket with the request so I don't lose track of it. Thanks.

@GunnyWaffle

No worries. Glad it's all working well for you now. Enjoy!

@Jobsti2

Please open an enhancement ticket. The comment stream sometimes moves fast and I forget about features asked for here. Make it a ticket and I'll see it and take care of it in a future version.

@GamingG

Thanks for the verboseStrateyLog output. If everything is as you describe, it looks like you may have hit a bug with the bed-finding algorithm. Note that the bed has to be within 5 blocks of the location you /sethome or bed-clicked. If that is the case, then it will require some further debugging.

If, based upon what we've discussed, you do feel everything is setup right and this is a bug, please open a bug ticket (so I don't lose track of this). If you want to help debug the issue, feel free to turn on core.debug and pastebin the log into the ticket. Otherwise this will have to wait until I have a chance to reproduce and debug the issue locally. (I do test all functionality I write and this did work when I tested it, it's possible it was inadvertently broken or was broken by a 1.3.1-related Bukkit update)

@GamingG

"Also, it looks like it's completely possible to bypass the mode anyway by teleporting in from another world using "/home w:worldname". As a possible workaround, is there a way to block access to homes in a particular world from other worlds while still allowing the command to be used in the same way to get to other worlds' homes?"

There is not. Enabling such behavior would either require an "excludeList" world for cross-world teleport or some fairly complex mode work that would allow you to define what worlds can/can't crossworld teleport to specific other worlds.

Since that's not immediately forthcoming from HSP, I might suggest an alternative would be to disable crossWorld teleport in HSP and instead give players a portal hub they can set /home in or a you setup a /spawn in or whatever (realize you can setup an event strategy for players /spawn command to only go to this one portal hub and not mess with the default spawn/new player behavior at all), and let them go there in the local world, then world-hop and /home in the new world. This lets players easily access their /home in other worlds without violating that you don't want them popping into their hardcore_world home from another world.

@GamingG

Your config looks right to my eyes. Can you turn on verboseStrategyLogging and test using "/home" and pastebin the output of the verboseStrategy log for that command? You should see it processing your "world_hardcore" onHomeCommand chain.

If that doesn't give us a hint as to the problem, next I will ask you to turn on "core.debug" and paste me the relevant info from the plugins/HomeSpawnPlus/debug.log file.

@andune

OK I have confirmed the source of the bug. It is related to BananaChunk-like functionality added as far back as HSP 1.3 (Jan of this year). Apparently all the chunk cache work they've been doing in Bukkit 1.3 has created a situation where reloading the chunk on teleport causes this issue (so this issue is new as of Bukkit 1.3.1). I'll update the Bukkit leaky with code details so those guys can look into it more, but for now the easy workaround to fix the issue is to add this to your HSP config:

core:
  reloadChunkOnTeleport: false

I'll add a note in the known issues with the info. Thanks again for troubleshooting and reporting the issue.

@ThornRage

An update: over the last hour one of my mods was kind enough to help me with isolated testing and I've confirmed the issue you posted IS a problem with HSP (Bukkit 1.3 vanilla = no issue, Bukkit 1.3 + ONLY HSP = issue). While I've further examined the code and the cause is not apparent to me right now, we are working to narrow down the issue and once I find it I will publish a fix. Thanks for reporting the problem.

@GamingG

Please share your config.yml (pastebin). Note the ordering of your "mode" statements is important since some modes reset others.

@ThornRage

You don't provide any specific info or stack traces in the ticket, only an erratic behavior that isn't reproducible. That said, I have heard reports of similar behavior on my own server and in the ticket you suggest that you've confirmed it's not an issue on vanilla. Since it's erratic I don't know how conclusive your "vanilla vs not" test is.

However, going under the assumption that your test was accurate and valid and that it means that HSP might be party to the minecart/boat/etc shenanigans (you also mention CommandBook, which I also run on my server), I did a quick audit of the code. The most likely code to be party to such issues is the onPlayerInteract() event and that code has not changed in many versions. This doesn't mean that Bukkit didn't change in some way that could be causing issues, so I further carefully checked the existing code and don't see any way it could be causing said issues.

Which leads me back to; how much work have you done to verify that it is HSP causing the issue? If you can, please confirm you have the issue on your server, and then do nothing except disable HSP and confirm the issue is gone as a result. If you can do this, I will invest more time than I already have in trying to find an issue, but as of right now I don't see how it's possible HSP is involved unless you can provide some more conclusive evidence.