[non stop spam]

Depending on which viewer you're using and how you've set it up, you can click on the object's name in its chat header or in Nearby Chat, or Conversations, or Chat History, or mouse over its name and click the little "i" button that shows up. This will open a little dialog telling you who owns it and where it is.

If it shows you as the owner, and the map shows it right on top of you wherever you go, then it'll be something you're wearing.

[non stop spam]

I think misrepresenting yourself as Linden Lab staff is about the gravest crime the Lab recognises. Abuse report and support ticket.

[Grid wide experiences]

For most people using experiences I think the main benefit will be the ability to access their key-value pairs everywhere.

[Question re llGetLinkPrimitiveParams]

I think we need to see the script being used, the linkset it's in (and specifically which textures are in which prim of the linkset... and which prim in the linkset the script is in) and the permissions of the textures involved (as they relate to the owner) to be able to get a handle on the issue.

[Favorite External Script Editors]

Ew, coding on a six inch touch screen? Is that a thing? I must be getting too old for this lark.

(Necro, but so what?)

[How do maps on a prim scroll?]

I haven't looked into it in any great detail, but the LL reference at http://wiki.secondlife.com/wiki/Linden_Lab_Official:Map_API seems to offer at least the ability to generate a MOAP map that could be udated using successive calls with changing coordinates.

[How do maps on a prim scroll?]

You can get the map texture UUIDs from Tyche Shepherd's grid survey, as well as other places, I think. You could make a square mesh plane with four square faces for the textures which you'd move around behind a border and swap the textures around to keep the desired location central.

[delete object after wearing]

Permissions are reset when an object changes ownership, which happens when the object gets attached.

You must request permission to detach from the new owner once it's been attached.

[delete object after wearing]

You can't delete an object from the inventory with a script.

[Do you think a sim looks the appropriate size (256 X 256 meters)?]

Metres and yards are pretty much interchangeable. Unless you're going to Mars.

[My Boat]

One thing to look out for when rezzing on water is that your viewer often takes the rezz point to be the land where your cursor would be pointing if there wasn't any water in the way. If you're having trouble in what you know to be a valid rez zone, try looking straight down when you try to rez something.

[Can't select an item that I just placed]

Using Firestorm? If so use area search and right-click and choose edit from the menu.

[Can't select an item that I just placed]

Have you tried camming at it from underneath?

[Display message only once in a timer for loop]

1 hour ago, Rolig Loon said:

Absolutely!  ?

 

Opps! Sorry, I missed that bit.

[Display message only once in a timer for loop]

If you have access to an experience, don't forget key-value pairs as a way of storing data.

[Display message only once in a timer for loop]

I confuse myself in LSL almost every time I look at a script.

[Json2Text]

Having just started messing around with the LSL Json functions, I thought I would be a good idea to write a function that'd chat out a JSON string neatly formatted:

Json2Text (string json)
{
    string TAB = "    ";
    string output;
    string line;
    string tabs;
    integer quotes;
    integer new_line;
    integer index;
    integer length = llStringLength (json);
    do
    {
        string character = llGetSubString (json, index, index);
        if (character == "\\")
        {
            ++index;
            string next_character = llGetSubString (json, index, index);
            line += "\\" + next_character;
        }
        else if (character == "\"")
        {
            line += "\"";
            quotes = !quotes;
        }
        else if (character == "," && !quotes)
        {
            line += ",\n";
            new_line = TRUE;
        }
        else if (character == "{" && !quotes)
        {
            line += "\n" + tabs + "{\n";
            tabs += TAB;
            new_line = TRUE;
        }
        else if (character == "}" && !quotes)
        {
            tabs = llDeleteSubString (tabs, 0, llStringLength (TAB) - 1);
            line += "\n" + tabs + "}";
        }
        else if (character == "]" && !quotes)
        {
            tabs = llDeleteSubString (tabs, 0, llStringLength (TAB) - 1);
            line += "\n" + tabs + "]";
        }
        else if (character == "[" && !quotes)
        {
            line += "\n" + tabs + "[\n";
            tabs += TAB;
            new_line = TRUE;
        }
        else line += character;
        if (new_line)
        {
            if (llStringLength (output + line) > 1000)
            {
                llOwnerSay ("Json2Text working..." + llStringTrim (output, STRING_TRIM_TAIL));
                output = "\n" + line;
            }
            else output += line;
            line = tabs;
            new_line = FALSE;
        }
    }
    while (++index < length);
    if (output + line != "") llOwnerSay ("Json2Text working..." + output + line);
    llOwnerSay ("Json2Text finished.");
}

I have encountered one problem that I think may be to do with LSL's implementation: when I insert a backslash as a JSON value ("\\") it seems to mess up its own and some or all subsequent llJsonGetValue calls. See the commented-out lines in the test script below.

default
{
    state_entry ()
    {
        integer count;
        string value = llList2Json 
        (
            JSON_OBJECT,
            [
                "JSON test", llList2Json 
                (
                    JSON_OBJECT, 
                    [
                        "item " + (string) (++count), PI, 
                        "item " + (string) (++count), TRUE, 
                        "item " + (string) (++count), FALSE, 
 //                      "item " + (string) (++count), "\\",
                        "item " + (string) (++count), "boring \\old text", 
                        "item " + (string) (++count), "\"", 
                        "item " + (string) (++count), "\n", 
                        "item " + (string) (++count), "\t",
                        "item " + (string) (++count), llList2Json (JSON_ARRAY, [1, "two", PI]), 
                        "item " + (string) (++count), "\nleading newline", 
                        "item " + (string) (++count), "trailing newline\n", 
                        "item " + (string) (++count), "inline\nnewline", 
//                        "item " + (string) (++count), "\\",
                        "item " + (string) (++count), "\boring ol\d t\ext", 
                        "item " + (string) (++count), "\tleading tab", 
                        "item " + (string) (++count), "trailing tab\n", 
                        "item " + (string) (++count), "inline\ttab", 
                        "item " + (string) (++count), "boring old text", 
                        "item " + (string) (++count), JSON_TRUE, 
                        "item " + (string) (++count), JSON_TRUE, 
                        "item " + (string) (++count), JSON_FALSE, 
                        "item " + (string) (++count), JSON_NULL
                    ]
                )
            ]
        );
        llOwnerSay (value);
        Json2Text (value);
//        integer count0;
//        do llOwnerSay ("item " + (string) (++count0) + ": " + llJsonGetValue (value, ["JSON test", "item " + (string) (-~count0)]));
//        while (count0 < count);
    }
}

I shall, of course, welcome comments, criticisms and suggestions.

[Non Physical Vehicle Script Tips]

It used to be that for large and complex boats the physical vehicle was pretty simple, while all the complex detail was actually an attachment worn by the skipper.

[Display message only once in a timer for loop]

4 hours ago, ellestones said:

i just add on a little note here about ++i vs i++

in LSL it doesn't make any difference.

It does work as it should LSL.

default
{
    state_entry ()
    {
        integer x;
        integer y;
        llOwnerSay ((string) (++x));
        llOwnerSay ((string) (y++));
    }
}

[11:47:06] Object: 1
[11:47:06] Object: 0

[Question: In your opinion, what have been the greatest controversies in the 15-year history of Second Life?]

In scripting I think it was whether one should use the constant PUBLIC_CHANNEL or just a plain 0 in the say functions.

[SL keeps log down computer after 5 minuts]

As this sounds like you'd've done a clean install of SL, it might be that the default logout settings have been reinstated.

In Preferences/General, at the bottom is the Away timeout setting. In Firestorm there's the additional Log out after being marked away setting. In the SL viewer you'll have to set the debug setting QuitAfterSecondsOfAFK manually.

ETA: Just looked in the SL viewer, and there doesn't seem to be a debug setting called QuitAfterSecondsOfAFK. There is one called QuitAfterSeconds, but that seems to work differently, maybe the time since login?

So I suspect I've been talking rubbish here. Sorry.

[Moving/zooming/focusing a camera to another avatar]

Using CAMERA_FOCUS_OFFSET, <0.0, 0.0, 0.5> (ish) will get your camera pointing at the target's boobs.

[My 'Click' is ignored - Why?]

10 hours ago, Skell Dagger said:

Quote

[...] There is no way for us tho know when a sim had a restart if we are not there [...]

 

changed (integer changes)
{
    if (changes & CHANGED_REGION_START)
    {
        llInstantMessage...
    }
}

[Deploy Plans for the week of 2018-08-06]

Ah, I now see from the SL status page that longer than normal downtimes were to be expected.

I guess it's my fault for having just read this thread and the status page RSS and not the status page itself as well.

[Deploy Plans for the week of 2018-08-06]

The long-offline region came back after nearly two and a half hours (I did put in a support ticket, but I don't suppose anyone saw it until later) and I've not had any more restarts in either region.