aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/OpenSim/Region/ExtensionsScriptModule
diff options
context:
space:
mode:
authorMW2007-12-02 14:56:23 +0000
committerMW2007-12-02 14:56:23 +0000
commitcac98171e5143dbcd37acca00a9e4ed87ec4e477 (patch)
tree5df6b0bc82d928f318b5c988765b5fadf7b2998f /OpenSim/Region/ExtensionsScriptModule
parentFixes a bug that my last commit introduced. (diff)
downloadopensim-SC_OLD-cac98171e5143dbcd37acca00a9e4ed87ec4e477.zip
opensim-SC_OLD-cac98171e5143dbcd37acca00a9e4ed87ec4e477.tar.gz
opensim-SC_OLD-cac98171e5143dbcd37acca00a9e4ed87ec4e477.tar.bz2
opensim-SC_OLD-cac98171e5143dbcd37acca00a9e4ed87ec4e477.tar.xz
Very partial Avatar Appearance (ie, clothes/body parts) "storage". In standalone mode it will mean that when you log off and log back on ,as long as the region server hasn't been restarted , your avatar will start with wearing the clothes that it wore on log off. In grid mode its even more limited in that wearing/removing clothes/body parts are only stored in the region server instance you are one. so if you are in a different region to your login region (which are on different region server instances), and then change clothes, those changes won't be remembered. So as said, its very limited but is a small step towards having proper appearance persist.
Just need to store this data out to a database.
Diffstat (limited to 'OpenSim/Region/ExtensionsScriptModule')
0 files changed, 0 insertions, 0 deletions