Bukkit

@PaulThePirate

You say "OP issue" - do you have a permissions system? If not, then you want to tell HSP to use ops-only permissions: http://dev.bukkit.org/server-mods/homespawnplus/pages/permissions/#w-ops-only

Follow those instructions and then put into defaultPermissions any perms you want all players to have. HSP follows a pattern with command permissions, they are all "hsp.command.XXX". So setfirstspawn will be "hsp.command.setfirstspawn".

If you are OP, you should have access to all commands. If you have a permission system, then try giving yourself one of those permissions and and see if that fixes it.

@PaulThePirate

This is a similar issue to what a few people have reported with HSP 1.7 series. Please see Ticket #135. I've tried many times to reproduce the issue but it always works fine for me. If you have any details to add, such as Bukkit and full plugin versions that you are running that might help me troubleshoot the issue further, please post it to that ticket.

Also, please go to the Changelog and try the latest dev snapshot and let me know if that improves anything. If that doesn't work, then download HSP 1.6.3 which seems to work reliably even for people that have this issue (the only downside is you won't have some of the newer 1.7 features).

@stuckatwork

Done! (as of 1.7) Check out Example7. The first example shows several new 1.7 modes being used to tweak random spawning, such as min/max Y, not spawning over water, etc.

Also 1.7 brought with it the 'ModeRememberLocation' and 'SpawnLocalPlayerSpawn' (also shown in that example), so HSP can actually remember where it randomly spawns someone and always spawn them back in that same spot (or not, your choice as always).

Glad you like the plugin. Enjoy.

@ccman972

What did you change recently? Did you upgrade Bukkit? Did you upgrade HSP? Did you change permission systems? All 3 at once? Something else?

It's very difficult to help you without knowing what you changed when it broke. Nonetheless, I will offer two solutions you can try, you can let me know how they work:

Try updating to the latest dev build. If your problem is related to an issue a few other 1.7 users were seeing, this might fix it, please let me know if it does.

Another option is to install HSP 1.6.3. You of course miss out on the new 1.7 features, but if the dev build above doesn't work, this gets you up and running.

All of that assuming your issue is related to the dynamic command system introduced in 1.7, which it may not be. If it really is a permission issue, you should be able to follow my advice in the previous post about assigning individual permissions.

Let me know if you've tried any of my suggestions in this post or my previous and they work. If not, please open a ticket and post as much detail as possible, including: exact Bukkit version (/version), HSP version, other plugins and their versions, and the exact error message you see (screenshot is best) and any other details (such as what you used to have when it worked and what you changed when it stopped working). The more information you provide, the more likely I will be able to help you find and fix any problem.

@ccman972

What permission system? Please paste the HSP startup string that looks like this:

11:46:28 [INFO] [HomeSpawnPlus] using WEPIF:PermissionsEx for permissions

Some permission systems don't respect the superperms "rollup permissions". You can try modifying the permission system HSP uses to just be superperms by adding:

permissions:
  - superperms

to your hsp config.yml to force it to use superperms only. This gives it the maximum chance to work with rollup perms, but still some perm plugins might not work well.

Your other option (short of switching perm systems) is to just manually assign the permissions. The plugin.yml (also in the JAR file) shows the permissions that would be assigned, you can just manually assign those same permissions.

@SUB_dawg

Is this a new install or have you been running HSP for a while?

The error indicates a problem with your ebeans server. I don't support the ebeans server, HSP just uses the facility Bukkit provides. Most of the time it just works, but occasionally I see weird errors from folks like yours below. You could try asking in the Bukkit forums, perhaps there is an ebeans.properties setting you can tweak to increase the number of connections. HSP shouldn't ever be using any more than one at a time, perhaps you've installed another plugin lately that's also using ebeans and is forgetting to close out connections?

Since this error is ebeans specific, you could also switch to the HSP YAML backend. (core.storage setting). If it's a new install, this is an easy switch. If an existing install, check the admin commands for commands to backup your database (using ebeans) and then after you switch, run a restore.

@HeavenMc

1. You could do that by using per-permission limits and your perm system to assign permissions per world. Example:

Group "Member" perms: hsp.world1.member (on world1), hsp,world2.member (on world2)

homeLimits:
  permission:
    entry1:
      permissions:
        - hsp.world1.member
      perWorld: 1
    entry2:
      permissions:
        - hsp.world2.member
      perWorld: 2

Now on world1, they will have hsp.world1.member which will give them 1 home in that world and in world 2 they will have hsp.world2.member which will give them 2 homes.

2. There is no way to set this config per-world, it is global. The closest you can get is to disable warmups entirely for a given world (or select groups on that world if you want) using permissions. To do that, you would enable the config globally and on worlds you want to disable warmups, give everyone on that world the hsp.WarmupExempt.* permission,

@dkmc

You would use per-permission homeLimits settings, and assign those permissions to the players/groups you want. An example:

homeLimits:
  # default limits (set to whatever you like)
  default:
    perWorld: 1
    global: -1

  permission:
    limit1:
      permissions:
        - hsp.homelimit.5
      perWorld: 5

You can have multiple entries and you can use whatever permissions you want (I just made up 'hsp.homeLimit.5' for this example). Also not above that the 'limit1' entry inherits the default global limit of -1 (unlimited). You could restrict it per-permission if you wanted also.

If you're going to define multiple levels of limits, it would be a good idea to give this section of the 'How HSP works' a read, so you can avoid issues with permission inheritance.

There are a handful of users who reported issues with HSP 1.7 dynamic commands. Could one of you that has the issue please download the latest dev build and confirm or deny that it fixes the problems you were experiencing? Or if you see any severe errors on startup that would be great to know too.

You can find the link on the Changelog with change details, or I've included it here in this comment for your convenience.

@ThisUsernameIsMine

The command (/permcheck or /pc) was documented in the FAQ, but not properly documented on the admin command page, which is fixed.

Glad the custom command chain is working for you. I was excited to add that feature to HSP, opens up lots of possibilities for admins. Enjoy!

@dogbig

I added code such that old invites should cleanup automatically and not NPE (and tested, worked for me). If you're still seeing the NPE, can you share your database (perhaps PM it to me) and the users affected? If I can reproduce it I'll fix any issue I find.

As to try/catch, the NPE's are indicative of a programming error. So rather than try/catch and silently eat the bug, I let any unexpected bugs propagate to Bukkit so you get a stack trace that you can share and I can fix. :)