Ulysses

Ulysses Stuff => General Chat & Help and Support => Topic started by: thegtz on July 28, 2012, 10:38:25 PM

Title: How to disable the (*) which targets everyone?
Post by: thegtz on July 28, 2012, 10:38:25 PM
I would like to disable * for commands so that the person using the command has to type the person's name in instead of just using * to target everyone. Is this possible?
Title: Re: How to disable the (*) which targets everyone?
Post by: Megiddo on July 29, 2012, 05:35:58 AM
Yes, comment out or delete line 110 in ulib/lua/ulib/shared/player.lua.
Title: Re: How to disable the (*) which targets everyone?
Post by: MrPresident on July 29, 2012, 06:27:32 AM
maybe it would be useful to add an access flag: Something like ulx allowaccessgroups. Players with this flag would be allowed to target using *, %, and ^ where players without would have to type names.
Title: Re: How to disable the (*) which targets everyone?
Post by: JamminR on July 29, 2012, 09:20:51 AM
Meg/Stick, Anyway to use "can_target" and "!*" and not have ULX block running commands on everyone?
(That's hard to explain but I hope you get what I'm saying)
I mean, if one were to add that now, I presume ULX would block targeting all players, not just the "*" command.
Is there any string one could add to prevent using "*" as a command?

Title: Re: How to disable the (*) which targets everyone?
Post by: thegtz on July 29, 2012, 11:01:18 PM
Meg/Stick, Anyway to use "can_target" and "!*" and not have ULX block running commands on everyone?
(That's hard to explain but I hope you get what I'm saying)
I mean, if one were to add that now, I presume ULX would block targeting all players, not just the "*" command.
Is there any string one could add to prevent using "*" as a command?

Is there any string one could add to prevent using "*" as a command?

Thats pretty much what I want to be able to do or maybe even remove it from certain commands.
Title: Re: How to disable the (*) which targets everyone?
Post by: Megiddo on July 30, 2012, 04:02:35 PM
MrP's suggestion would work, but it would globally affect a player.

Not possible in the way it's done right now JamminR, as keywords are always expanded when evaluated. I can't think of any logical way to break this rule in the permission strings at the moment...

It's all or none with that edit at the moment, thegtz.