Jump to content
You are about to reply to a thread that has been inactive for 100 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

Posted

I have read through a few threads on here about the merits of the following methods, and the conversations are somewhat convoluted but don't answer my question here. So I don't *think* it is a duplicate but I might have missed something.

Methods

llDetectedGroup()
llSameGroup()
llGetObjectDetails(ID,[OBJECT_GROUP]) )

My understanding is that the first two compare the group of the agent to the group that the object and current script themselves are set to. Which is possibly fine when the object is rezzed in world, as the person who places it can set the group. But for me this doesn't work (see below)

 

Context and purpose

In my case I have a HUD that will be distributed to and worn by members of a group. At some later stage any of those users might be removed from the group, which needs to cause the product to stop functioning for that user. The HUD operates from a single click by the wearer.

  • We cannot be know what group, if any, the wearer has active when they attach the HUD (so the HUD object attachment might, I assume, have no group set)
  • The wearer also might not have our group active when clicking on the HUD.

 

Question

Can we detect if the wearer (same as: the agent clicking the object) is a member of a given group (for which we have the UUID and can be hardcoded) regardless of whether they have that group active?

 

Posted
48 minutes ago, Remi Alpha said:

Can we detect if the wearer (same as: the agent clicking the object) is a member of a given group (for which we have the UUID and can be hardcoded) regardless of whether they have that group active?

No, but add llIsFriend to the list of functions with unworkable caveats.

As for blacklisting, experience KVP as I mentioned in your other thread, could be workable for that use-case. (HUD checks for the existence of a 'blackkist:owners_UUID' key, stops working if found.) More work for administration (need to manually interact with some blacklisting script) but at least it should work.

If your users have RLV enabled (which can be a big ask for people who aren't familiar with it) llOwnerSay("@set_group:group_name=force"); can be used to set the wearer's active group, which could then be verified.

  • Thanks 1
You are about to reply to a thread that has been inactive for 100 days.

Please take a moment to consider if this thread is worth bumping.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...