Open vrad-exe opened 5 years ago
What should we do for this in Aperture Tag and TWTM? Since they include the BEE1 by default, we don't really want to remove those assets.
I think what I'll do instead is to change our paths so they don't conflict. Additionally I'd then make the compiler treat the BEE2 folder as highest priority, so it'll pack those and then override the other files.
Ah, in that case I have a list of all the editor assets that currently conflict. Haven't checked in-game stuff, though I think the only thing that needs to be changed for that is P1 antlines. conflicting_files.txt I originally thought about doing this, but figured it would be better to just remove the old versions automatically during export.
There is currently an issue where some old BEE2.2 assets (most notably editor models) will override the newer versions, since they're in a higher search path (DLC2). When exporting, BEE2.4 should automatically detect these and remove them. An option should be present to turn off this behavior though, in case someone wants to keep BEE2.2 around for whatever reason.