Config file
Ironic8b498 opened this issue ยท 6 comments
I did a quick search on mywarp.limit.disobey.[WORLDNAME].total and couldn't find anything on how to set up config to change limits per groups and worlds.
For some reason, GitHub's search does not seem to search the wiki so it is pretty much useless. Creation limits are explained here, including configuration examples for Bukkit and all disobey permissions.
Please let me know if anything is unclear after reading the article or if you have additional questions so I can improve it.
Ok got the config to load without errors, had a little issue with typo's but I got it under control now. I changed enabled under Limits to true. Seems to use default limits. Just can't seem to get the limits to work per world. I have mywarp.limit. set to each of the ranks. I still can't get the limits to work.
http://pastebin.com/G9kSbQ0u mywarp config
http://pastebin.com/0FKeDHvq perms
tp make your wiki easier to understand I think you should add how to add a rank that is a number, I have three groups 0, 1, 2 and not all server owners may know they need to add ' to allow the script to run. Also I'm just a little fuzzy on the mywarp.limit.disobey which means to over ride set limits default or group limits?
The disobey permissions disobey every limit, regardless if configured or default. For users with such a permission, the corresponding limit is never checked, e.g. for the mywarp.limit.disobey.test-world.total permission, the total warp limit on the world test-world is never checked.
To overwrite a configured limit with another one, you must make use of the lexicographical resolution. Judging from your permissions configuration, 0, 1, 2, vip and xrayer will all have the recruit limit due to permission inheritance. To solve it, you could rename your limits like this:
| Old name | New Name |
|---|---|
| recruit | z_recruit |
| xxx | r_0 |
| griefer | p_griefer |
| xrayer | p_xrayer You could also simply use the p_griefer limit. |
| yyy | o_1 |
| zzz | k_2 |
| vip | g_vip |
| guard | d_guard |
| admin | a_admin |
To be clear: Limits have absolutely nothing to do with permission groups - a limit is just a permission, nothing more. You can use the same limit for multiple permission groups. It does not make much sense to define the same limit twice with a different name (as you seem to do with griefer and xrayer, as well as with xxx and yyy).
Thanks got it now, on older version of plugin I had the zzz at top that's why it worked then. I used the new names you suggested and got rid of griefer and xrayer and used z_recruit since I was using the same settings for those three.