
Limit doesn't update
natkemon opened this issue ยท 10 comments
Hello.
Currently having an issue with limit configuration. This is the limit section of the config: http://pastebin.com/pCWUZL5X
Problem is that the defaultLimit doesn't update to 0 but continues to stay at 5 public and 10 private warps.
What have i done wrong?
This is definitely not the latest devBuild (I changed the formatting of warp assets
some time ago and this looks like the old one). Please try this one.
Getting an error upon typing a command like /warp list
http://pastebin.com/wJAaj2Du
My bad - that is already fixed in code but since currently the repository of Vault is offline, automatic builds do not work.
Please try the build before the one I linked above: https://thee140.ci.cloudbees.com/job/mywarp3_bukkit/122/
The above build works. Tested and some parts work. THe problematic parts is warps for obsidian and skybro are staying on a limit of 2 rather than 3 and 4 respecitvely.
Yes, the limits obsidian
and skybro
are overwritten by gold
.
Limit permissions are resolved in lexicographical order. If a user happens to have permission for two limits, the lexicographical first applies. This means that you cannot name the limits like you want to, but must name them in a way that takes the lexicographical ordering into account, e.g. like so:
configuredLimits:
j_sand:
totalLimit: 1
publicLimit: 1
privateLimit: 0
affectedWorlds:
- skybros
- Spawn
g_gold:
totalLimit: 2
publicLimit: 2
privateLimit: 0
affectedWorlds:
- skybros
- Spawn
d_obsidian:
totalLimit: 3
publicLimit: 3
privateLimit: 0
affectedWorlds:
- skybros
- Spawn
a_skybro:
totalLimit: 4
publicLimit: 4
privateLimit: 0
affectedWorlds:
- skybros
- Spawn
With that being said, do i need to change the permission nodes so that it looks like this: mywarp.limit.a_skybro
PEX: http://pastebin.com/qEGYFbye
warp config: http://pastebin.com/r8Gh0MYD
Doesn't seem to be working. Do you mind checking out what i did wrong? All ranks stay at 4 warp limit now
I cannot reproduce this. Could you test again with the latest devBuild and post the output of /warp assets
for a player that should have the default limit?
Beides you should remove affectedWorlds
from the default limit as it is always ignored (the default limit is always global). If you only have two worlds (Skybros
and Spawn
) I would recommend to also remove affectedWorlds
from all other limits as limits without it are always global.
Currently using the latest devBuild. Running version 1.9.4
My user Ghostman132 assets are as displayed: http://prntscr.com/c0584y
Using PEX: This is my permissions file : http://pastebin.com/YWZesMrp
Currently have more than 2 worlds (skybros and spawn). So i should leave it as it is i assume.