This is a blocker for further Elemental Shift releases - I can't balance anything until it's fixed.

Not sure I get it. Why do you want to move the XML files to the Collection folder? Why not leave them in the Extensions folder?

Note that if there is a TDB in the collection folder, we use it instead of the XMLs in the Extension folder, but if you use /debug, then it always uses the XMLs from the Extensions folder if found.

 That’s the issue: The Extensions folder isn’t being read. (Moving XML/TDB files was just for testing purposes.)

 Try running the following with Elemental Shift in your Extensions folder:

TransData.exe /itemTable /criteria:"w +extension:0xDC4E0000" /balanceStats

Almost certainly the problem is that you need to specify the extensions to use explicitly. It won't automatically use all extensions.

First, run TransData /stats, which will dump out the set of extensions being used. Most likely you won't see Elemental Shift.

Next, edit TransData.xml. It should be something like:

<TransData>
	<Option name="extensionFolder" value="c:\Users\GPM\Documents\Elysium\Extensions, ..\Extensions, .\Extensions"/>
	<Option name="extensions" value="0x00800000, 0xA0010000, 0xDC4E0000"/>
	<Option name="debug" value="true"/>
</TransData>

The first option specifies where the Extension folders are.

The second option lists the set of extensions to load. In my example, the last one is Elemental Shift.

After that, try TransData /stats again and you should see it loaded.

You can also do that on the command line:

TransData /extensions:"0xDC4E0000"

Let me know if any of that helps.

 Speaking for myself, the filepath to the Extensions folder was wrong (previous laptop, not current laptop). I can’t speak for Song.

 Song has reported that a similar solution to mine has TransData working for her again. Resolving.