Entropy

Hello, Torley and Co!.

At the moment, it seems an attachment's memory/stack status is only recorded when a user detaches their attachment or logs off. This means, if a sim crashes then the attachment's most recent status will be lost and will be restored to it's previously recorded state after the user logs back in.

Or to put it another way - imagine the following steps:

- I make a virtual battery with a power level of 100. The power level is scripted to slowly drain away.

- I then take the battery into my inventory and then attach it to myself.

- After an hour or so, the power level is nearly at zero

- I intentionally crash the sim. (which I can do very easily)

- I then relog to find the battery's power level has reverted back to its initial state of 100

What happened?:

It seems the power level has been restored to 100 because the battery's low power state was failed to be recorded because of the sim crashing. and so the battery is restored to what it was when I had initially taken it into my inventory.

This problem could make it quite easy for people to cheat at energy/score based games.

What I'd like to know is that is it possible (via script) to force an attachment to record its status without having to constantly manually detach and reattach it?


Yours hopefully, me.


Edited:

Thanks for the reply, Torley, Phoenix!!

Hot damn, Starax, that "imagine the following steps" sequence is really easy to understand. What a great illustration. I don't know a way to do this, but please let me ask further to see how we can get a more accurate reading of our "battery charges"...

For much the same reason we cannot write to or create notecards from scripts, there is no plan to allow attachments to save themselves into central persistent storage. Anything that has a large dependence on lots of dynamically changing global state will either need to centralize that functionality in an SL script running in a safe place or externally on a remote server.

Currently, the easiest way to do this is through llEmail. The new HTTP API we are currently testing will ease this.