Skip to content
This repository has been archived by the owner on Feb 3, 2024. It is now read-only.

Pex 1.21.3 - Many problems: Op's can't use commands, players perm issues, massive lag #1628

Closed
GamerUnityGit opened this issue Aug 27, 2014 · 5 comments

Comments

@GamerUnityGit
Copy link

I've been using Pex for years now on all servers I've helped set up. I understand (as far as I know) permission nodes very well. My trouble is my latest server has so many issues with Pex that I don't know whats going on. I found out I was using Pex 1.20.x (can't remember which version) soI upgraded to the latest 1.7.2 version. The problem that spurred me to upgrade was the "Regex-matched value of undefined from cache" error. Upgrading didn't fix that. So I rewrote the permissions file completely. That helped for the most part, except now players are being denied permission for nodes I explicitly allow. Even if I give the player personal nodes, it doesn't matter.

I had originally put in about 2400 nodes for my default group, most negated, but I did that so I had all nodes in one spot in case I needed to allow nodes or grant special players custom nodes. I was being lazy. But I've since then changed that and now my entire file with about 50-60 players added has about 1200 lines. I run an anime based server, so we have a lot of different ranks for different mage classes for the players and 11 ranks for staff (council based staff, "10 seats" for different staff roles, and one player moderator group).

Inheritance isn't properly working, regardless of what I try. My default group is called Citizen, and then I have a hidden rank called DefaultPerms, that inherits Citizen, which all 20-30 mage ranks pull from for just a couple extra permissions not granted to Citizens, to keep permission file length down. I don't use rank: '####' because I don't use /promote or /demote. That could goof up our server with how we do ranks.

I also don't understand why Pex is causing a 10 second lag whenever a player logs in. And yes, I know its pex. One of my admins and I spent several hours pulling each and every plugin one at a time and he logged in while I watched console. Right when I saw him try to connect, I'd run /pl (command that wouldn't cause lag or needed any sort of event) and it was always 10 seconds after he logged in. I read that players had lag when running a file based backend, so thats why I came here. I wanted to try the SQL backend before exploring other options with pex.

This is what I had done:

multiserver:
use-netevents: true
permissions:
debug: false
allowOps: false
user-add-groups-last: false
log-players: true
createUserRecords: true
backend: file
backends:
file:
type: file
file: permissions.yml
sql:
uri: mysql://localhost/mydatabase
user: myloginid
password: mypassword
updater: false
alwaysUpdate: false

But when I start the server, it deletes the file and writes the default file back.

One other issue, and as far as I know my last, my admins, which I op and also grant all perms with - '*', cannot do anything other than what the default group can do. if I explicitly allow any player any custom node, such as /pex user add essential.gamemode to one of my admins who are op'd but can't use /gm, it doesn't allow them to use it.

Here is my permissions file, and the reason quite a few ranks are empty is because they are unused at the moment. Also, if I can't get even my default group to work, there's no point in working on something else that won't work. I've spent over a week working on this, googling that, checking this, rewriting the file several times, changing perm plugins to no avail... I'm tired of this and I want to know what I'm doing wrong and if its my fault or if I stumbled across a bug.

http://pastebin.com/CtvyCjuQ

@GamerUnityGit
Copy link
Author

Reverted Pex back to a 1.6.4 version to get rid of the lag. But now I'm worried about the regec-matched value of undefined from cache. I had this before which is why I moved to Pex 1.21.3. I'm changing to fix a problem but gaining another huge problem. And my server isn't updated past 1.7.2. Thats why I'd like help figuring out whats wrong with 1.21.3 for me. Any help would be appreciated.

@zml2008
Copy link
Member

zml2008 commented Sep 2, 2014

All issues should be fixed in 1.22.3+ (and the soon-arriving 1.22.4). Version 1.21.3 is unsupported.

@zml2008 zml2008 closed this as completed Sep 2, 2014
@GamerUnityGit
Copy link
Author

Thats bullcrap. I stated I'm not updating past 1.7.2 and you just ignore me? Awesome. You produce something and instead of offering help you just act like Microsoft. Update this and it'll fix it. Update update update. Never using this plugin again with this kind of "support".

For the record, I never asked for a rewritten 1.7.2 Pex plugin. I asked for freaking help understanding what was wrong. If you don't tell me whats wrong how will I know if it was me or the plugin? And you can't claim "All issues should be fixed" because any decent coder knows there's no such thing as a perfect program. I waited a week for this crap? And to think I praised Pex over every other plugin, even earlier today. Extremely disappointed.

@jomo
Copy link

jomo commented Sep 2, 2014

I'm sure you'll get your money back.

@zml2008
Copy link
Member

zml2008 commented Sep 2, 2014

If you want to know what changed, there are conveniently [commit logs](http://github.com/PEXPlugins/PermissionsEx/commits/master which can tell you exactly what has changed. There are also more concise changelogs available on every release page.

If you want to maintain a release that fixes your issues for 1.7.2, feel free. This project is released under the terms of the GPLv2. Otherwise, update.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants