Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

Ideas For Permanent Data Storage?
Kyle Gilman
Registered User
Join date: 12 Apr 2004
Posts: 16
07-06-2005 16:11
Hey everybody, I am starting this thread as a place where we can bounce around some ideas about ways to store data in an object without the risk of it being lost when the sim crashes or the object is picked up. If there was already a thread about this topic please point me to it. :) Any ideas are welcome.
Satchmo Prototype
eSheep
Join date: 26 Aug 2004
Posts: 1,323
07-06-2005 16:28
To store permanent data: [LLEmail]-->[postfix]-->[perl/php]--> [mysql]

To retreve data: [LLEmail]-->[postfix]-->[perl/php w/ mysql/XMLRPC]-->[llOpenRemoteDataChannel]

But this doesn't store data in an object and I suspect you were looking for something quicker?
_____________________

----------------------------------------------------------------------------------------------------------------
The Electric Sheep Company
Satchmo Blogs: The Daily Graze
Satchmo del.icio.us
Torn Bobbysocks
Registered User
Join date: 6 Jul 2005
Posts: 11
07-06-2005 16:29
Hey, welcome to the forums!
I went digging around in the script library and found these:
/15/78/37866/1.html
/54/57/37861/1.html
I think they're relavent.
Jessica Qin
Wo & Shade, Importers
Join date: 16 Feb 2005
Posts: 161
07-07-2005 08:14
From: Kyle Gilman
Hey everybody, I am starting this thread as a place where we can bounce around some ideas about ways to store data in an object without the risk of it being lost when the sim crashes or the object is picked up. If there was already a thread about this topic please point me to it. :) Any ideas are welcome.

Also, the Wiki hacks page

http://secondlife.com/badgeo/wakka.php?wakka=hacks

has a suggestion for "Permanent Small Memory Information Storage":
From: someone
Besides using a script's memory as permanent storage (and just never resetting it), you can store short strings in the name (using llSetObjectName / llGetObjectName) and description (llSetObjectDesc / llGetObjectDesc) of each prim. If you don't want your object to change it's name, use child prims in a link set for that. You can also store floats in other object properties, such as texture rotation, offset, alpha, scale, etc. Basically anything that has a get/set combination. To store integers, you can simply convert them to floats and back by scaling them down to fit into the usual 0 - 1.0 range.

You can also use llSetTexture to store strings using the typecast (but your object will always have to be full permissions to read back the data), as well as llSetAlpha for floats, llSetColor for vectors. Combined, you can store a lot of information permanently.

I've always loved this -- it reminds me of EPR/Bell hidden variable theory :) :) :)

Jess
Toneless Tomba
(Insert Witty Title Here)
Join date: 13 Oct 2004
Posts: 241
07-10-2005 17:05
The store data in textures was a pretty cool thing. I tried this awhile ago almost made a vendor based on this storage system, luckily I didn't after they nerfed llGetTexture. If you can make whatever item w/ full perms may be worth while. It does get prim heavy depending on the amount of data being stored.