[Clock]

You might also want to look at llGetTimestamp, which returns the standard UTC date and time string. The helper functions linked on that page could also prove useful.

[How does this work?]

The comments in the examples at http://wiki.secondlife.com/wiki/Typecast mention that leading white space and trailing non-numeric text is ignored when typecasting strings to floats or integers, but that's about it.

[Maximum Height for teleporting into a region?]

Two ways this could happen would be to go to that height, TP away, and then use the link in system message "Teleport completed from…" to return, or to log out from there and log back in again at the last location.

[Sparkly textures/Materials]

Here's a couple of textures I sometimes use to give things a sparkly effect, either singly or in combination. 

Normal:

Specular:

If anybody finds them useful, you're free to use them however you like. I'll stick them on Marketplace eventually, I suppose.

[Where's best to discuss Sailing?]

I guess the "organised" SL sailing "community" has always tended towards paranoia, megalomania and idiosyncrasy, but that does seem a bit extreme. Although the site offers me no resistance to visiting even when not signed in.

[Where's best to discuss Sailing?]

You could have a look at http://www.virtualworldsailing.com/index.php?/page/index.html. It appears to be active, but I've not  participated for years.

[How does this work?]

See http://wiki.secondlife.com/wiki/LlGetListLength#LSO_Optimizations

Quote

A faster and lighter (in bytecode) way to determine the length of a list is to do a not-equals compare with a null list. This works because the list not-equals compare returns the difference between the lengths, meaning that it returns the same result as llGetListLength(), minus the overhead in bytecode, and performance penalty of calling a non-native function. Note: This optimization is much less beneficial time-wise in Mono as Mono's llGetListLength function is almost twice as fast, however the bytecode saving is still about 30 bytes.

 

[Script Practice]

Write a script that will distinguish between a single click (touch) on an object, a double click, and a long click.

Write a script for a calculator or keypad of some sort. For the output display you might use simple chat, floating text, or a series of linked prims. If you go for the linked prims, use only a single texture for all the digits and characters. Or, find or make a mesh panel with, say, eight faces, side by side, or find or make one of those tortured prims that present several similar faces to the viewer (hint: Xyzzy Text). For the body and buttons use only a single prim and a single texture (hint: llDetectedTouchUV). Add a key click sound.

Send an email from one object to another, or from an in-world object to your own email address.

Make a pair of objects act as an HTTP server and a client.

[Making a object walk aimlessly]

This sounds like a job for pathfinding.

[Trying to change texture uuid of a certain prim in my boat.]

Presumably the OP is trying out their textures on copies of boats they own, so they should be able to determine whether they've been scripted to use hard-coded link numbers or to determine link numbers from link names (or some other attribute) and adapt their applier scripts as necessary.

[Right clicking any object shows all lines]

Try Build/Options/Show Selection Outlines (Ctrl+Alt+H).

[dim object in background]

Take two photos, one using your preferred choice of lighting and windlight, the other using Ambient Dark windlight and with point lights turned off (local lights in graphics preferences). The photo taken using Ambient Dark will be black except for any objects set to full bright. You can use this in your preferred photo editor as the basis of a mask to darken the full bright objects.

[Skill Gaming Policy Thread]

Will there be a script function introduced to enable gaming scripts to determine if they're actually allowed on the land they've been rezzed on?

[How do I specify a vector value for a debug setting for use with the --set command line switch?]

How do I specify a vector value for a debug setting when using the --set command line switch?

For example, I'd like to set CameraOffsetRearView to <-2.5, 0.0, 0.5> at startup, but I haven't been able to figure out the correct format.

--set CameraOffsetRearView <-2.5, 0.0, 0.5> doesn't work.

Thanks

Edit... (in lieu of any apparent reply mechanism)

1. How do I reply to an answer in this forum?

2. Ansariel, both your suggestions produce a parsing error.

I have found, however, that --set CameraOffsetRearView -2.5/0.0/0.5 parses ok, but results in a 0, 0, 0 value for the setting.