AE:Plugins: Difference between revisions

3 bytes removed ,  11 October 2016
m
Mac OS X -> macOS
m ("instance file" is just the .dat)
m (Mac OS X -> macOS)
Line 13: Line 13:




Oni loads instance files in a certain order. On NTFS partitions of Windows and on Mac OS X that order will be ASCII-based (case-sensitive, "B" before "a", etc). On Windows 98 and such the order is more random and depends on dates of creation. As for what happens to the ''instances'' in the files being loaded, there is no such thing as "overriding" - more like the first instance registered with a certain name being the only one accessible by that name. Instances without raw parts typically follow the intuitive rule "plugin loaded first - instance registered first". For things like [[OBJC]], the order is reversed, i.e., in order to "override" a level's OBJC you have make sure that the overriding plugin's name comes ''after'' level2_Final or whatever you're "overriding" (so, e.g., level2_OBJC). Finally, some instance types are stored dynamically in an array, so: 1) if you have, e.g., several instance files containing [[ONCC]]s, they will all end up in the "shapeshifter" array (first the ones from the first loaded instance file, ordered by name, then the ones from the second instance file, also ordered by name, etc); 2) If two of those instance file have an ONCC with the same name, both of them be loaded, at their respective places in the array: both will be accessible with F8 and by ID, but only the one loaded first will be accessible by name.
Oni loads instance files in a certain order. On NTFS partitions of Windows and in macOS that order will be ASCII-based (case-sensitive, "B" before "a", etc). On Windows 98 and such the order is more random and depends on dates of creation. As for what happens to the ''instances'' in the files being loaded, there is no such thing as "overriding" - more like the first instance registered with a certain name being the only one accessible by that name. Instances without raw parts typically follow the intuitive rule "plugin loaded first - instance registered first". For things like [[OBJC]], the order is reversed, i.e., in order to "override" a level's OBJC you have make sure that the overriding plugin's name comes ''after'' level2_Final or whatever you're "overriding" (so, e.g., level2_OBJC). Finally, some instance types are stored dynamically in an array, so: 1) if you have, e.g., several instance files containing [[ONCC]]s, they will all end up in the "shapeshifter" array (first the ones from the first loaded instance file, ordered by name, then the ones from the second instance file, also ordered by name, etc); 2) If two of those instance file have an ONCC with the same name, both of them be loaded, at their respective places in the array: both will be accessible with F8 and by ID, but only the one loaded first will be accessible by name.