Ulysses

Ulysses Stuff => General Chat & Help and Support => Topic started by: sabo on May 12, 2013, 12:39:10 PM

Title: Adding a 2nd parameter for can_target
Post by: sabo on May 12, 2013, 12:39:10 PM
As stated in this thread: http://forums.ulyssesmod.net/index.php/topic,5346.0.html

Quote
So, to solve the problem above, you would do: "ulx setgroupcantarget mod !%mod,^"  This means "mod can target NOT group mod, can target self"  (The comma basically just adds another separate parameter)

You can add a 2nd parameter for targeting groups.

What I want is: Superadmins can target Superadmin and all under superadmin. Superadmins can not Target the Owner (higher rank) and can not target themself.

So I did this: " ulx setgroupcantarget superadmin !%owner,!^ "

The "^" stands for the person who wrote the command
The "!" stands for not
"!^" means for me: NOT me

It does not work so can someone help me out in this please?
Title: Re: Adding a 2nd parameter for can_target
Post by: JamminR on May 12, 2013, 01:01:41 PM
Define "it doesn't work".
What error? What isn't working?
What access person is trying to do what to what access person?
Do you have owner inheriting superadmin (which then inherits restrictions)?
Title: Re: Adding a 2nd parameter for can_target
Post by: Megiddo on May 13, 2013, 11:53:40 AM
The comma is a union (http://en.wikipedia.org/wiki/Union_(set_theory)) operator, so you can't allow a group to target others in the group but not themselves. I know this restriction is annoying for cases like this, but to make it any more complicated we would have had to create a parser (http://en.wikipedia.org/wiki/Parser) with associated grammar and order of operations (in other words, way too much overhead for this feature).
Title: Re: Adding a 2nd parameter for can_target
Post by: sabo on May 13, 2013, 01:17:48 PM
The comma is a union (http://en.wikipedia.org/wiki/Union_(set_theory)) operator, so you can't allow a group to target others in the group but not themselves. I know this restriction is annoying for cases like this, but to make it any more complicated we would have had to create a parser (http://en.wikipedia.org/wiki/Parser) with associated grammar and order of operations (in other words, way too much overhead for this feature).

Okay I guess there is no way to change that.

Thanks for the answer atleast I am aware of the situation now :)

Have a nice day ;)