Today's update changed an internal portion of the wardrobe appearance system. It broke my program. I haven't received any word that they are upset or trying to block me out, so I assume it's coincidental.

I spent tonight working on a fix. Got it implemented within an hour and further optimized the code. Now down to an estimated 3 days 10 hours. Not bad for losing a day's worth of ripping.

Updated for Rift Discoveries 2018-02-13. The new system works great. Two items with no appearance. A few columns added at the end, existing columns kept their index. Also available as a JSON file if interested.

Updated for Rift Discoveries 2018-04-03. Same 2 items with no appearances. 706 items added since the 2018-03-13 discovery file. Many of these items have Item Name = Appearance Name. They said they added many items to the Rift store, guessing it's a bunch of appearance/costume items. Yay!

Is anyone using the TemplateId, PreId, or PostId columns from the Rift Ripper exports? If not, I'm going to remove them.

I'm also planning to add a column called LangId that will include the appearance ID from the language files. This will expand our localization abilities. Right now, we can match ItemKey to its localized item name thanks to Items.xml, but we don't have ItemKey matched to localized appearance text, only English text. Initially, this new column will contain a key that returns a value that matches the appearance text BUT it may not be the correct key for the item. Effectively, this will be unnoticeable. Later, if we find a way to connect ItemKey and LangId, we will update accordingly.

If multi-language support interests you, please like this post so I have some idea of priorities.

You mentioned vfx... We are looking for a way to connect ItemKey to a model ID so we can batch export pictures/3D objects for fan sites. If you happen to know what databases/tables/fields hold that secret sauce, we'd be most delighted if you could share.

You mentioned vfx... We are looking for a way to connect ItemKey to a model ID so we can batch export pictures/3D objects for fan sites. If you happen to know what databases/tables/fields hold that secret sauce, we'd be most delighted if you could share.

Second! Any information that would allow us to map this stuff would be awesome. I know some data is held server side only, but making it available for data mining/scalping would help us assemble some cool stuff!

Even if we don't have an ItemKey, it would be awesome to get some sort of map of wardrobe appearance name to model filename.

Rift Ripper has been updated to 4.4.
-TemplateId
-PreId
-PostId
+LangId
-+16 appearances (200+ items) had previously been updated, so their names had been purged from the language file, so they didn't get a LangId. I removed their existing appearances, re-ripped them, and then their LangIds were populated without issue. Here are the old appearances from before their renaming.