Ulysses
Ulysses Stuff => General Chat & Help and Support => Topic started by: Wayne Brady on November 08, 2009, 06:14:53 PM
-
I need to make an owner group (for me) and a Co-owner group for my co-owners. I can make the groups easily, but how would I go about making them have everything a super admin can do, but higher?
-
Re: Immunity - see http://forums.ulyssesmod.net/index.php/topic,4314.0.html
Re: access - In Gmod standard access, there are 3 levels, superadmin, admin and user, there is no higher group than superadmin.
In ULX, with it's customizability, you can make many groups. Use addgroup to create a group called owner and have it inherit superadmin, then, groupallow with the revoke switch to remove access to some superadmin commands you'd rather have owner have, then groupallow those same commands to owner.
See ulx help and ulx usermanagementhelp for those commands explained (the ulx help is out of date for the immunity explanation, so ignore that - refer to the link above I gave you for that)
-
So, can you tell me the exact commands to make it do everything a Superadmin can, but with higher immunity?
-
Read the how to, then ask what you don't understand.
It's explained well.
-
My problem with this is the fact that won't it take forever just to retype every groupallow thing for the superadmin again so it makes it so they can't ban owners and stuff, and also to make owners and co-owners be able to have higher immunity? I don't want to have to type ulx groupallow superadmin "ulx ****" "!%owner" over and over again..
-
In all honesty, we and Garry meant for superadmin to be the highest ranking access anyone would ever need.
In Gmod terms, superadmin default = root = superuser.
That's why Gmod allows it the most commands.
That's why we allow it the most commands.
In most cases, it would be best to create a lower group with less commands, which would also mean much typing but not as much as editing every allow for the superuser.
Until XGUI gets more completed, yes, you'd need to do alot of typing.
Remember though, this is SVN. It's under development... which means Megiddo may see this discussion and allow (or already has and it's just not clear yet something similiar to
ulx groupallow superadmin * !owner
Back up your groups and users files (which, when running SVN, you should anyway)
Try that.
Or, even try ulx groupallow superadmin "ulx" !owner
That in it's own right has issues though, won't be able to use asay to talk to the wall ops, etc.
Or if those two tries don't work, make one or two command access immunity changes like shown in the how to,
then go examine what edits were done to the data/ULib/groups.txt file, and copy those with a good text editor for the other commands you don't want performed on an owner.
Experiment.
Best way to learn.
Keep backups so you can recover from what you learned not to do. :)
-
There's no 'mass permission edit' in place right now... I don't really see any good way to do that.
-
There's no 'mass permission edit' in place right now... I don't really see any good way to do that.
We should find a way for those like us who like console commands, but are lazy and don't want to have to type, even using autocomplete, for every command for every group. =)
-
We should find a way for those like us who like console commands, but are lazy and don't want to have to type, even using autocomplete, for every command for every group. =)
I'm open to suggestions. :)
-
Just an idea for starters...
ulx groupallow superadmin * "!%owner"
where "*" =
1. Would add no additional access and instead would
2. would cycle through the superadmin's current allow table and make the same change as if I'd typed each "ulx <...>" command individually.
I feel there's a pitfall I'm missing there...but, again, just an idea trying to keep wheels turning. (mine and anyone elses)
-
Just an idea for starters...
ulx groupallow superadmin * "!%owner"
where "*" =
1. Would add no additional access and instead would
2. would cycle through the superadmin's current allow table and make the same change as if I'd typed each "ulx <...>" command individually.
I feel there's a pitfall I'm missing there...but, again, just an idea trying to keep wheels turning. (mine and anyone elses)
How about having an access tag named __target that is just general ability to target on all commands? But then you'd be unable to psay someone you can't target.
-
How about having an access tag named __target that is just general ability to target on all commands? But then you'd be unable to psay someone you can't target.
That was my concern throwing out things to Wayne previously.
That in it's own right has issues though, won't be able to use asay to talk to the wall ops, etc.
I'm guessing you mean, for instance, ulx groupallow <group> "ulx __target" <!<group>>?
-
I'm guessing you mean, for instance, ulx groupallow <group> "ulx __target" <!<group>>?
Basically, yes.
-
Say if group1 inherits from group2, would group1 have higher immunity? Because, that's how I have it set up now.
-
There is no 'higher' (or even 'lower') immunity in the inheritance chain unless you've used groupallow <group2> <ulx command> "!%group1" on every command of every group below that group