What would this kind of system do to my server?

[Shadotak]

I see some people worrying about user data taking up space on the server.

I've set up a system where the User class isn't used at all. I created a new class called NUser to be the default group and I use AutoPromote to set people to that group when they join (set it to 0 hours). This way, I can create a "Minge" class that has no access to commands. It can't move, can't noclip, can't spawn anything, and has no weapons.
My real question is: What will happen to my server when I have hundreds of people in a ulx group? Will it affect it at all?
Additionally, is there another way to do this? My problem is that I can't create a normal class that doesn't inherit rights from users. I want the Minge class to have absolutely no access to anything, which isn't possible if Users have access to simple commands like !god.

[Gower]

Use ulx groupdeny to deny a group commands.

You can disallow "user" all commands and then inherit the permissions to the new group.

[Stickly Man!]

XGUI has been known to be a little sluggish when you start getting lots of users in groups- that's something that's been on our todo list for a while.

My recommendation would be to leave the user group as your standard group everyone is assigned to, and give permissions from there. Then, create a Minge group that inherits from user, but use ulx groupdeny to deny access to each command you don't want them to have access to. From there, your other higher-level groups can still inherit from user, keeping Minge separated as its own thing. I don't think I ever added groupdeny to the groups tab permissions editor yet, so you'll have to use the console command.

[Shadotak]

Use ulx groupdeny to deny a group commands.

You can disallow "user" all commands and then inherit the permissions to the new group.

XGUI has been known to be a little sluggish when you start getting lots of users in groups- that's something that's been on our todo list for a while.

My recommendation would be to leave the user group as your standard group everyone is assigned to, and give permissions from there. Then, create a Minge group that inherits from user, but use ulx groupdeny to deny access to each command you don't want them to have access to. From there, your other higher-level groups can still inherit from user, keeping Minge separated as its own thing. I don't think I ever added groupdeny to the groups tab permissions editor yet, so you'll have to use the console command.

These help a bunch. I wasn't aware there was a way to get around inheritence. Thanks for this!

EDIT: quick question, how do I use it?
http://puu.sh/73N7v.jpg
It tells me "Groupe 'minge' doesn't have access to 'noclip'"
I tried it with ulx noclip as well, same thing.

[Stickly Man!]

You should just be able to do this in your console:

Code: [Select]

ulx groupdeny minge "ulx god"
..but it should work from XGUI either way.

One other thing, the screenshot you posted- there was a bug where no text was showing up in that blue bar at the bottom of your XGUI window, which I fixed a loooong time ago. You should update your version of ULX and ULib by using the SVN Versions listed here or by going to our GitHub page.