That is unfortunate.
However I noticed that Process Monitor does capture the offset at which a compressed data file is being read, so maybe that could somehow be used with the existing CASC explorer / export tools.
Theoretically one would need to translate that offset into a file id / file name. I assume the files are stored with some sort of index, which does eventually translate into an offset, so that they can be exported by these tools. 🤔
Of course this wouldn't be an instant solution, but at least you could record some gameplay with ProcMon running and then afterwards run a compare script that matches the offsets to the packed files.
At least that's an idea in my head right now, I'm not sure if it's even possible (or if I want to dive into that, that CASC format seems pretty complex).
Code:
Time of Day Process Name PID Operation Path Result Detail
14:12:59,04 Wow.exe 24968 ReadFile E:\Games\World of Warcraft\Data\data\data.098 SUCCESS Offset: 496.959.488, Length: 5.308.416
14:12:59,04 Wow.exe 24968 ReadFile E:\Games\World of Warcraft\Data\data\data.098 SUCCESS Offset: 502.267.904, Length: 65.536
14:12:59,07 Wow.exe 24968 ReadFile E:\Games\World of Warcraft\Data\data\data.098 SUCCESS Offset: 309.133.312, Length: 65.536
14:12:59,07 Wow.exe 24968 ReadFile E:\Games\World of Warcraft\Data\data\data.098 SUCCESS Offset: 309.198.848, Length: 5.242.880
14:12:59,07 Wow.exe 24968 ReadFile E:\Games\World of Warcraft\Data\data\data.098 SUCCESS Offset: 314.441.728, Length: 65.536
14:12:59,10 Wow.exe 24968 ReadFile E:\Games\World of Warcraft\Data\data\data.096 SUCCESS Offset: 997.064.704, Length: 65.536
14:12:59,10 Wow.exe 24968 ReadFile E:\Games\World of Warcraft\Data\data\data.096 SUCCESS Offset: 997.130.240, Length: 3.932.160
14:12:59,10 Wow.exe 24968 ReadFile E:\Games\World of Warcraft\Data\data\data.096 SUCCESS Offset: 1.001.062.400, Length: 65.536
14:12:59,13 Wow.exe 24968 ReadFile E:\Games\World of Warcraft\Data\data\data.096 SUCCESS Offset: 562.036.736, Length: 65.536