Hi, Hello. New Here. Advice of Repos Please

So extensions, and rulesets, can have a "loadorder" defined. a value from 1 to 100, higher order loads last. But it is not required that a loadorder be defined. I don't know if its predeictable what happens with two extensions with a conflicting loadorder or if none is defined (maybe it defaults to 0?)

The later an extension is loader, the more authority it has, i.e. the last read instance of a function overwrites what was defined before. unless a MERGE=join is defined for that file, windowclass or function.
Rulesets can also define a parent, which in itself can have a parent. So most rulesets are children of CoreRPG. So CoreRPG loads first, then D&D5E (or such). I think PF1E is actually a child of 3.5, so its Core>3.5>PF1.

Often extensions completely overwrite core or parent ruleset functions and files that they don't need to. It's because most of us are not coders either, and we hack. SmiteWorks over the last year or so has made Core and the supported rulesets much easier to modify in part, without us having to overwrite everything to achieve what we want. But again, most of us are hacks, not coders :)

Quote:

---

Originally Posted by LordEntrails

The later an extension is loader, the more authority it has, i.e. the last read instance of a function overwrites what was defined before. unless a MERGE=join is defined for that file, windowclass or function.

---

This reframes what I thought I understood. I didn't think the later the function was the more authority it derived. I thought the nature was inverse and that each following function had to align strictly with the previous. so this is good information to have.. I think my interpretation of signal flow may have been fundamentally wrong then.

Thank you. And from what I've seen, hack is far from the correct term. I also have a tendency to do exactly what I described above and over clarify to the point of exhaustion, so this was a good pull back.

So just to make sure it's clear, it goes something like this:

CoreRPG - Loads First
Defines Function A
Defines Function B
Defines Windowclass 1
Defines Windowclass 2
... etc

Child ruleset loads second
Overwrites Function A
Defines Function C
Alters Windowclass 1 via Merge=Join
Defines Windowclass 2
Defines Windowclass 3
... etc

Extension loads third
Defines Function D
Overwrites Windowclass 3

This results in the final code that FG executes as:
Function A from child ruleset
Function B from CoreRPG
Function C from child ruleset
Function D from extension
Windowclass 1 as altered by child ruleset
Windowclass 2 from child ruleset
Windowclass 3 from extension

Thank you very much. this is appreciated :)

Core can't alter Rulesets, or EXTs
Rulesets can't alter EXTs.

Having said that, some APIs are not open for Core, Rulesets, or EXTs to alter. Those are considered in the "client" .exe.