@Bmac load order?

[peardox]

OK - we get exported first and override last

 

With lax* is there an order?

 

I notice SOME things override others in lax* but as there are many lax* directories it is possible that one override overrides another unless there is a specific order to lax*

 

Can you please clarify? How's this work? Alpha / date?

 

[Fhav6X]

I'm not Bmac, but judging from the game's code there is a package index and a load order of bundles. The last loaded bundle would have the highest priority.
 

       public enum PackageIndex
    {
        // Token: 0x04005333 RID: 21299
        BaseGame,
        // Token: 0x04005334 RID: 21300
        BackerBeta,
        // Token: 0x04005335 RID: 21301
        LAX1,
        // Token: 0x04005336 RID: 21302
        LAX2,
        // Token: 0x04005337 RID: 21303
        LAX3,
        // Token: 0x04005338 RID: 21304
        LAX4,
        // Token: 0x04005339 RID: 21305
        LAXA,
        // Token: 0x0400533A RID: 21306
        LAXB,
        // Token: 0x0400533B RID: 21307
        LAXC,
        // Token: 0x0400533C RID: 21308
        LAXD,
        // Token: 0x0400533D RID: 21309
        Unused,
        // Token: 0x0400533E RID: 21310
        LAXE,
        // Token: 0x0400533F RID: 21311
        LAXF,
        // Token: 0x04005340 RID: 21312
        LAXG,
        // Token: 0x04005341 RID: 21313
        LAXH,
        // Token: 0x04005342 RID: 21314
        Count

 

I can't say, if the package index is used as the load order though.

[BMac]

Yes, that enum shows the order the built-in bundles will be loaded in.

[peardox]

Cool

 

I'm trying to sort out what is current - at least I have a clue how to process these now

 

Is this anywhere in /exported?

[BMac]

The load order is not specified in data, it's in code where Fhav6X showed.  You can assume the order will always be BaseGame, followed by numbered major DLCs in order, followed by lettered minor DLCs in order.