is it safe to rename the operator group?

[Mornedil]

Basically, here's how I want my ulx rank heiarchy to be set-up (gmod rank inside parentheses):

newbie (user)
builder (user)
trusted (user)
moderator (admin)
Admin (admin)
superadmin (superadmin)


So I have 2 problems.

1. I want to rename the operator group "trusted". I already have their team name set to "trusted", but "operator" still shows up everywhere except the scoreboard. I'm just wondering if it's safe to rename the group name, or if "operator" is hard-coded anywhere within ulx (like how it's a bad idea to rename admin/superadmin).

2. I need the moderator group to have gmod admin permissions, but actually be below the ULX group admin. I know I can set the team name of admin to moderator, and create admin2 above that, but same problem as in #1 applies - "moderator" would only show up in the scoreboard while they would be referred to as "admin" everywhere else.

[Zmaster]

Operator should be perfectly fine to change the name of, every time I've installed ULX on a new server I've changed its name to moderator and have never experienced a problem with it

[Mornedil]

Thank you, I'll go ahead and change it's name.

I'll add one more question (beside question 2 which I am still wondering about how to do).


whenever I set "can target" to for example "#user,#builder", it gets automatically changed to "user,#builder" when I hit apply.
Is this supposed to happen or is it a glitch?
I've noticed that if I type in "##user,#builder" it gets changed to "#user, builder", so the first hashtag seems to be removed.

[Aaron113]

I hate to keep tooting my own horn, but your second question can be done using this...

http://forums.ulyssesmod.net/index.php/topic,8486.0.html

[JamminR]

Aaron, as you agreed in your own horn post, both sides of the discussion rely on the person understanding how can target and inheritance work.
Though I can't really ask you to stop, I wish you would.
Your code is not safe practice, especially considering many do not understand.

[Mornedil]

hmm I have to agree that while that code is a good idea, it might not be very smart to override the core functions of ULX like that.

It would be very helpful though to individually be able to set an ULX group to either "user", "admin" or "superadmin".

It's a feature ULX should have imo, because it's frustrating that certain groups are kind of locked to a certain name. and having checkboxes like that (or the ability to connect ulx groups to gmod ranks via console commands) would certainly solve a lot of the confusion and workarounds when setting up groups.

[Aaron113]

It would be very helpful though to individually be able to set an ULX group to either "user", "admin" or "superadmin".

It's a feature ULX should have imo, because it's frustrating that certain groups are kind of locked to a certain name. and having checkboxes like that (or the ability to connect ulx groups to gmod ranks via console commands) would certainly solve a lot of the confusion and workarounds when setting up groups.

That's exactly what my little addon does.  If you don't want admins to be considered admins, then they don't have to be.  All I'm overwriting is a check for group superadmin (and admin).  Literally "if group == superadmin". 

The only thing I really agree on is that new users are confused as it is, why add in more confusion?  Or this could make things easier... who knows for sure.  It's just there as an option.

[allofmywutsteam]

Everyone seems to mention the code Aaron wrote up, but I'm not sure how easily OP can implement it if he doesn't have the ULX/code experience.

In any case, OP, I wouldn't recommend changing the default "admin" group to something other than admin simply because there are so many addons that use the default "admin" group with no problem. And then inheritance moves up from there.

I do recommend creating a group that inherits from a group below "admin" and then give that specific group all the ulx access you want. I'm not entirely sure why you want someone to be considered "admin" and not give them "admin" rights though. Maybe I'm not understanding the request

[allofmywutsteam]

Basically I see it like this:

newbie > admin > moderator > superadmin
builder > admin > moderator > superadmin
trusted > admin > moderator > superadmin

Reason being because you want moderator to have Admin access. but the issue is you don't want the moderator to be above the admin group, so you wouldn't be able to inherit Admin rank, so giving them specific perms would be ideal. That way you have the structure you want and mods have the same access as admins. only difference is, they won't have that gold name color effect on the SB. But that can be adjusted i'm pretty sure

ulx addgroup "newbie" "user"; ulx setgroupcantarget "newbie" "!%moderator"
ulx addgroup "builder" "user"; ulx setgroupcantarget "newbie" "!%moderator"
ulx addgroup "trusted" "user"; ulx setgroupcantarget "newbie" "!%moderator"
ulx addgroup "moderator" "user"; ulx setgroupcantarget "newbie" "!%admin"
ulx groupallow "moderator" "ulx teleport";ulx groupallow "moderator" "ulx bring" ... etc etc (keep allowing whatever specific commands you want mods to have that admins have)

[Aaron113]

I think he wants a group below admin to have admin access to be able to do things like clean up maps and such (which is usually highly dependent on IsAdmin()).  The only viable option (outside of what I already suggested), is to go in and edit what ever addon he may be using.  This is where what I suggested comes in handy.  There is the chance doing this gives them other rights you may not want to them to have (like admin sweps or sents), which is the only downfall.

Also, my script doesn't really require any code experience.  Just download it from the link I supplied and it is already in addon format for you.

EDIT:  That's all I really have to suggest unless you want to rename your groups and teams to work the way you want.  (Ex:  the group admin would be called Moderator)

[Mornedil]

@allofmywutsteam, that seems like a pretty inconvenient and confusing workaround to the problem. @Aaron, I think your code is the best solution, the reason I hesitated was because official ulx devs were kind of against it in your thread. But the default grouping in ulx doesn't allow for much versatility, as in, it makes no sense to have anything between admin and superadmin without using some nonsense name like "admin+" or "senior admin".
And yeah, you understand me correctly when you're assuming I mean giving access to features in other addons which require IsAdmin() to return true.