Can you use a script to write text to a notecard?

[Feafelme]

Dear all,

does anyone know of any work-around to have a script pick up data from a list datatype variable and write this information into a notecard, so as to create/append to a kind of data repository? Thank you very much.

KR

Fëafelmë

[ChinRey]

There is no way to get a script to write to a notecard. The only workaround is to get the script to say the text and then copy and paste it manually.

 

Edit: I didn't know of the Experiences function (thank you Rolig!) and thought the http option would be a bit too complicated but it's a good tip.

A fourth method we all forgot about is email. Every single object in Second Life has an email address and it's fairly easy to add a script to send you a message with the text you want.

But in the end, no matter what method you use to output text from a script, to get it onto a notecard in Second Life, you will either have to type or copy and paste manually. This is an intentional limitation btw. Linden Lab decided long ago that allowing scripts to write notecards would cause more load to the servers than it was worth. There have been several attempts to make them change their minds about it but they haven't so far.

[Rolig Loon]

ChinRey is quite right.  You cannot use a script to write to a notecard.  If you want to save list data to a permanent repository, though, the best way to do it is to use KVP in Experience Tools.  The llCreateKeyValue function will create a key for the data string you want to save and deposit the initial value you provide.  Thereafter, you use llUpdateKeyValue to modify the string and llReadKeyValue to get the value back out again.  You'll have to save your list as a delimited string (easiest if you use llDumpListString (my_list,"~") ) and then use llParseString2List when you need to unpack it later.

[Nalates Urriah]

Both answers are right. There is a third way. Using HTTP it is possible to write to an outside server. You'll see a number of things in SL that do that. Probably the most common ones are breedables and combat meters. A major draw back is the need for an external server on the net.

There are some examples around of people using various cloud services for storing data from SL.

[CaelumSanguis]

So, to be able to maintain a handful of status flags, having a little imagination and the ability to llSetColor and llGetColor takes on a whole new meaning as does the value of 9-sided (zero opacity) prims.

[Rolig Loon]

18 hours ago, CaelumSanguis said:

So, to be able to maintain a handful of status flags, having a little imagination and the ability to llSetColor and llGetColor takes on a whole new meaning as does the value of 9-sided (zero opacity) prims.

This is rather an old necrothread, but the information in it is still valid.  If all you want to do is retain status flags, though, you don't need to go to great lengths.  Do as all scripters have done since the dawn of SL: store your flags as s delimited string in the Description field of your object (or one of its links).  Those will survive script restart, so you can read them back again in the script's state_entry event or wherever you need them.

Edited March 1, 2019 by Rolig Loon

[Lindal Kidd]

The Dawn of SL....