In the Early Days of Yore(tm), when Solaufain was a young mod, Smoketest and devSin and Nythrun battled Fierce Clashes in Arcane Languages, and the bigg was just cutting his baby teeth on OCaml, we went through some practice standardization about the position of the .tp2 and "best practices". While WeiDU kept legacy position maintained, most folks moved from
->[MyMod]
->setup-mymod.tp2
to
-> [MyMod]
- - >setup-mymod.tp2
It worked pretty well, as transitions go, with a few bug reports here and there due to users extracting the old over the new, with two setup-mymod.tp2 on the same install (one in the same directory as the mod folder and the other new one inside that folder), and there was some adjustment of priority order for .tp2, and voila... the Mountain Moved. (Most of the Mountain. My mod archive has a few lingering "old skool" behaviors floating about in the field like prehistoric mammoths, peering over at all the nice domesticated cattle with their fancy ".ini files" and their "AUTO_TRA", etc.)
Now I am reading great stuff back and forth here and at G3 between the Heavies - folks who really are rebuilding again great functionality behind the scenes. Way cool. But I am fuzzy on the way WeiDU now really handles mod setup.
Are we now at a point where the other huge Legacy Behavior is able to be changed, dispensing with SETUP-MYMOD?
Such that (yes for cross-system-architecture all lowercase, but with caps here for clarity)
-> [MyMod]
- - > MyMod.ini
- - > MyMod.tp2
- - > [lib]
- - > [lang]
- - > [media]
- - > [docs]
etc.
Is there still a need for WeiDU to see and verify SETUP- as the trigger to do things like run the autoupdate, and do all the other "here is the instruction set that takes priority and does the Heavy Lifting"?
I assume that this is the case, but I want to make absolutely sure and clear "frm the source". CamDawg has a great new Amber v5 package out, and I noticed the .tp2 change there. I am restructuring based on his example.
Follow-up question (probably for another topic, but might as well ask): Are there other extant legacy behaviors in .tp2/.d/.baf that are now really cruft being dragged along (stuff like DECOMPILE_AND_PATCH replacing DECOMPILE / COMPILE calls, etc.) ?