Jump to content
  • 0

How to tell an object's true owner?


Lindal Kidd
 Share

You are about to reply to a thread that has been inactive for 4562 days.

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

Question

5 answers to this question

Recommended Posts

  • 0

right-click>edit could be the problem, especially if the viewer is older. There are some very old "caching" kinds of bugs with the edit floater, old values were not flushed when the fields were populated with a new object's details. I have not seen that problem happen with the 2.x inspector, the edit window could still have that bug but it is not needed for the grief kind of situation.

I am sure that 1.x viewers could be patched not to do that if somebody wanted. LL added a fix once for the editor group display, so there should be a pattern to see there that can be copied to the owner etc. fields.

 

  • Like 1
Link to comment
Share on other sites

  • 0

If you are able to fetch the UUID of said object, using the following can help:

default
{
    state_entry()
    {
        list info = llGetObjectDetails(uuidHere,[OBJECT_OWNER]);
        llOwnerSay((string)llList2String(info,0));
    }
}

 

However alot of clients support the ability to click on the name of the object (which is most of the time a link to the profile of the owner)

 

Another way of doing it, is if it is a chat spammer, is to set up a listener on Channel 0, using listen()'s built in key id, will return the objects UUID automaticly, see below.

 

key uuid;

default
{
    state_entry()
    {
        llListen(0,"","","");
        
    }
    listen(integer chan, string objectName, key objectKey, string msg)
    {
        uuid = objectKey;
        list info = llGetObjectDetails(uuid,[OBJECT_OWNER]);
        llOwnerSay((string)llKey2Name(llList2String(info,0)) + "  Said: " + (string)msg);
    }
}

 

^^Copy and paste that into an object, anything sent over channel 0 will display the message and who sent it.

Link to comment
Share on other sites

You are about to reply to a thread that has been inactive for 4562 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
 Share

×
×
  • Create New...