summaryrefslogtreecommitdiff
path: root/indra/newview/character
diff options
context:
space:
mode:
authorNyx (Neal Orman) <nyx@lindenlab.com>2009-11-17 16:22:12 -0500
committerNyx (Neal Orman) <nyx@lindenlab.com>2009-11-17 16:22:12 -0500
commit8c99b37ac0480addcf14cb8643cba85bebe822ad (patch)
treea803bd6edc9b4a205d2e4075cdd2c3fc0a7b09fc /indra/newview/character
parent70b605e4196b538cb7831e8821f765b5c99d9ae0 (diff)
EXT-2535 wearables saved in 2.0 don't load in 1.23
Incrementing wearable version number was a bad thing here - we want to keep all wearables reporting as version 22 until we make a breaking change. Reverted the version number and put in a hack to force any version 24 wearables to be re-saved as version 22. The hack can be removed before release, as it should only affect internal testers. Code reviewed by Seraph --HG-- branch : avatar-pipeline
Diffstat (limited to 'indra/newview/character')
-rw-r--r--indra/newview/character/avatar_lad.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/indra/newview/character/avatar_lad.xml b/indra/newview/character/avatar_lad.xml
index 10c197d09e..d7182dfaab 100644
--- a/indra/newview/character/avatar_lad.xml
+++ b/indra/newview/character/avatar_lad.xml
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="US-ASCII" standalone="yes"?>
<linden_avatar
- version="1.0" wearable_definition_version="24">
+ version="1.0" wearable_definition_version="22">
<!-- The wearable_definition_version is checked during asset upload. -->
<!-- If you increment it, check indra/lib/python/indra/assetutil.py. -->
<skeleton