MUX: Attribute Visibility
-
Is there a good way to restrict attribute visibility to a list of objects (players, rooms, things) contained in an attribute list somewhere?
I know it can be restricted via underscore, or with attribute ownership as attribute owners can read the attribute on an object even if they don't own the object. Visible is too open.A good example would be if you wanted to have a clan that could issue an arbitrary command and see the names of everyone in that clan... but you only wanted members already added to that clan to run the arbitrary command.
-
@Hexagon said in MUX: Attribute Visibility:
Is there a good way to restrict attribute visibility to a list of objects (players, rooms, things) contained in an attribute list somewhere?
I know it can be restricted via underscore, or with attribute ownership as attribute owners can read the attribute on an object even if they don't own the object. Visible is too open.A good example would be if you wanted to have a clan that could issue an arbitrary command and see the names of everyone in that clan... but you only wanted members already added to that clan to run the arbitrary command.
MUX does not have an arbitrary method to specify if you can see specific attributes over someone else.
What you'lll have to do is build a @function to fetch the attribute(s) based on evaluated permission sets.
Sorry I don't have a better answer for you.
Though maybe... hum. Not overly familar with MUX Zones, but it is a potential for murking the ownership a bit to grant you what you want, but it will likely still be object-wide and not per attribute.
I don't think Penn attribute trees would even grant something like this.
-
@Ashen-Shugar said in MUX: Attribute Visibility:
@Hexagon said in MUX: Attribute Visibility:
Is there a good way to restrict attribute visibility to a list of objects (players, rooms, things) contained in an attribute list somewhere?
I know it can be restricted via underscore, or with attribute ownership as attribute owners can read the attribute on an object even if they don't own the object. Visible is too open.A good example would be if you wanted to have a clan that could issue an arbitrary command and see the names of everyone in that clan... but you only wanted members already added to that clan to run the arbitrary command.
MUX does not have an arbitrary method to specify if you can see specific attributes over someone else.
What you'lll have to do is build a @function to fetch the attribute(s) based on evaluated permission sets.
Sorry I don't have a better answer for you.
Though maybe... hum. Not overly familar with MUX Zones, but it is a potential for murking the ownership a bit to grant you what you want, but it will likely still be object-wide and not per attribute.
I don't think Penn attribute trees would even grant something like this.
On Penn I'd run it through a switch that checks an attribute on the player (clan) against the attribute one is trying to see. Could use a couple objects depending how complex you want it, but could get the effect of certain attributes only visible by certain clans or groups pretty easily.
Not that it helps OP.
-
Thanks @Ashen-Shugar @Lotherio. That's about what I figured, but it was worth asking.
