I have read through all the previous topics about this but nothing has helped me resolve the issue.

I have configued one limit and added that permission to one rank. I use inheritance for my ranks so the one above the one with the permission should inherit that permission. There is no overlapping from what I can tell.

GroupManagerFiles.zip
MyWarpFiles.zip

Oops, I should have noticed that. It didn't fix it though it seems (I de-opped myself and gave myself VIP but could still place past the limit). I have the default warp limit set to 10 in total (which is the case for VIPs, while anything higher should get 20 total warps using the permission).

Worth mentioning is I have way more warps than the set limit to begin with (24 warps when the limit is 10). Adding a warp still works in this scenario. Do the limits only work if you are below the limit to begin with, or does the plugin check if the amount of warps is larger or equal to the set limit?

No, the limits should also work if you have more warps than allowed by disallowing the creation of new ones

What is the output of /mw assets in the situation you described above?

I think you have a typo in the permission:

  g:essentials_VIP+:
    permissions:
    - mywarp.limits.mod

Should be:

  g:essentials_VIP+:
    permissions:
    - mywarp.limit.mod

(Remove the s.)

Let me know if this fixes the problem.

Bump. Any luck figuring this out?

Sorry for not answering. I will have to test this with GroupManager by myself, as the config looks fine.

I promise I will do this by 20/05/18 - unfortunately I have hardly any time for non work related stuff atm.

So, I just tested your files in GroupManager on my own test server. Unfortunately, I cannot reproduce your problem, everything works as expected.

You said above that you promoted yourself to vip. But reading from your files, players need to have VIP+ in order to have the mod limit. Could you please test, if it still does not work if you (1) use mywarp.limit.mod (no plural as said above) and (2) you are in the VIP+ group?

I appreciate your time. I have the default limit set to 10, so it should work regardless of my rank as long as I have permission to set warps (which VIPs do) and no bypass permission. I tried when I was VIP+ but it is still not working. I use several worlds on my server and I tried in the default world and in another one.

Could you send the MyWarp config you used for your test server? I feel like that could be the only place I have done something wrong, but I use a lot of plugins so who knows!

I changed my GroupManager config to inherit the group.yml and users.yml files from the main world. The warp limits now seem to work in that main world, but nowhere else. Tried specifying each world under "affectedWorlds" in the MyWarp config but to no avail. Will keep experimenting!

After more testing it seems like as soon as I make myself VIP+ the limit stops working in the main world, and doesn't work anywhere else just like when I am VIP. If I remove the permission mywarp.limit.mod the limit works for me when I am VIP+ in the main world, since it is then using the default limit. So the configured limit is not working anywhere, and the default limit only works in the main world.

Thank you for this update. This is an extremely strange behaviour.

What strikes me most is that the default limit only works in the main world. Technically, the default limit is a fallback: It is always used as a fallback if other limits or disobey permissions are not present. If it does not work, something must block it.

Could you test if it works on a different world than main when you explicitly negate the following permissions on this world for yourself (non-op)?

mywarp.limit.disobey.[WORLDNAME].total
mywarp.limit.disobey.[WORLDNAME].public
mywarp.limit.disobey.[WORLDNAME].private
mywarp.limit.disobey.[WORLDNAME].*
mywarp.limit.disobey.*

The world name is case sensitive.

Also, if you are not making this test on a public server, could you maybe give it a short try using another permission plugin?

The permissions did not work using GroupManager. Tried switching to LuckPerms, but contrary to the name of the plugin I did not have any luck. Used the migration command to move everything over from GroupManager, with no errors. The VIP rank has all the commands as it did with GroupManager so I assume it worked, but the issue with MyWarp persists and I have negated the permissions with the new plugin and it is still not working. Clearly not a permissions fault then!

I just tested it again but without luck: I cannot reproduce your issue using this file.

• I used the latest devBuild. Are you using it, too?
• I used the last version of CraftBukkit for 1.12.2 (CraftBukkit version git-Bukkit-2b93d83 (MC: 1.12.2) (Implementing API version 1.12.2-R0.1-SNAPSHOT). Are you using it, too?
• I used GroupManager 2.0.1-b332. Are you using it, too?
• Are you absolutely sure that you are no longer OP when testing?

If the answer to all of these questions is 'yes', I am really out of ideas.

Sorry, I don't mean to waste your time and I should have done way more testing than I have done thus far. I really appreciate your help in trying to resolve this.

When you did your testing, did you try going over the limit in several worlds? Because that seems to be the problem for me.

I tried removing all warps and reset the config again, and I found that warps are limited on a "per world" basis and not globally. I set two warps in one world and two in another, with the global limit (default total limit) at just two, and as soon as I tried to place the third warp in both worlds I got the "too many warps" message. I did my testing with the permissions negated as you advised me to do above, but that did not make a difference. I am definitely not OP when doing the testing as I always check my commands with /help and they are always correct for VIP, plus the fact the game tells me I am no longer OP.

In this round of testing I used the latest Spigot build for 1.13.1 and your latest release of MyWarp for 1.13.1, as of this post. I use "EssentialsXGroupManager 2.0.1-b332", but I couldn't find where I got it from. I inherit the users.yml and groups.yml files from the main world to every other world to make things easier. I will add screenshots to make the steps I took in-game extra clear. The first three are from one world, the last two from the other world.

Here is my up to date GroupManager config.yml, globalgroups.yml, users.yml and MyWarp config.yml.

GroupManager.zip
MyWarp.zip

Delete any files I have given to you earlier and use these if you decide to test again. These are the ones I used for my testing above, without the negated permissions for GroupManager as they didn't seem to have an affect.

If you do another test and your result is positive, then I must be using a plugin that somehow conflicts with MyWarp, or the worlds I am testing in are too old (they are all from before 1.8), so 3+ years ago. I haven't tried that yet though. I use MultiVerse to keep all worlds loaded at the same time, see relevant files below.

MultiVerse.zip

Tested with two fresh 1.13.1 worlds and the limit is still applied on a "per world" basis.

When you did your testing, did you try going over the limit in several worlds? Because that seems to be the problem for me.

This finally did the trick, I was able to reproduce the problem. A fix may take two or three weeks as I will probably just rewrite the handling of limits, because the current version is rather ugly and a hell to maintain...

Thanks for doing all of this tests!

Great! And no worries, troubleshooting is something I enjoy, especially if it is beneficial for me and the developer in the long run. Good luck with the fix!

Could you test if the last devBuild (#1627) solves the issue?

It works, thank you so much!