Current MIX loading order is
documented. I'm planning to modify it so expandmd* goes before langmd, and you can then put anything that is currently required to be loose in them. Or I can use a new, different filename/wildcard for that slot, if that is deemed too fragile. Thoughts?
Yes, I apparently can't wait till feedback comes before coding anything. All the more fun that way.
I'd like that.
Sick & tired of putting loadscreens loose in the RA2 directory............
(05.10.2008, 21:36:12)DCoder Wrote: [ -> ]Current MIX loading order is documented. I'm planning to modify it so expandmd* goes before langmd, and you can then put anything that is currently required to be loose in them. Or I can use a new, different filename/wildcard for that slot, if that is deemed too fragile. Thoughts?
Yes, I apparently can't wait till feedback comes before coding anything. All the more fun that way.
Keep them in the expand file keeps things tidy and not have 3 mixes instead of ecache and expand
Sounds good
i agree, to be able to put those things inside a mix would be useful, and why not expandmd?
And further to DCoder pointing out this load order, Launch Base will, in future, not create ecache at all - everything will go in expand.
I certainly don't see any point in a separate mix file such as "elang".
(06.10.2008, 10:18:57)Marshall Wrote: [ -> ]And further to DCoder pointing out this load order, Launch Base will, in future, not create ecache at all - everything will go in expand.
I certainly don't see any point in a separate mix file such as "elang".
I agree If its all in 1 Mix so much easier to compile and such
A seperate elang file might be useful actually since it would make localisation easier for any mod that attempted such a thing.