KT Kingsley

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

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

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.

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?)

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.

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.

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.

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

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

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.

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

Have you tried camming at it from underneath?

Opps! Sorry, I missed that bit.

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

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

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.

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.

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

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

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.

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

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

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.

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.

I just had that too. Sometimes it's because something horrible that hadn't been spotted in beta shows up, and they decide to roll back to the previous version. This time, though, the server version showing is the one that's been posted above. Meanwhile, another region I use has been offline for over an hour. ETA: Well this is unusual: a third restart, and this one only took a couple of minutes. Same new server version. The other region remains offline after nearly two hours.