CooKyzz Posted March 9 Share Posted March 9 Hello there, quick questions, in the dependencies drag & drop section (in the "mod" tab) : What's the difference between "Must Deploy After" and "Require"? I mean what do they really do ? Does "Require" assume that it must deploy after as well ? That kind of thing Link to comment Share on other sites More sharing options...
showler Posted March 9 Share Posted March 9 If A "requires" B then removing/disabling B will either display an error for A or automatically disable it. Link to comment Share on other sites More sharing options...
CooKyzz Posted March 9 Author Share Posted March 9 15 minutes ago, showler said: If A "requires" B then removing/disabling B will either display an error for A or automatically disable it. Got it, does it also do something with the load order ? Or that's only "must load after"'s role ? Link to comment Share on other sites More sharing options...
showler Posted March 9 Share Posted March 9 I'm not sure about that. I'm not sure how strict BG3 is about dependency order. Link to comment Share on other sites More sharing options...
CooKyzz Posted March 12 Author Share Posted March 12 After some testing on my end, neither seems to have any effect on the load order. Soooo yeah, i don't have a clue about "must deploy after". If anyone knows, i'm all ears ; either way i'll use "requires" but i'd like to know anyway ! Link to comment Share on other sites More sharing options...
Solution vortexposer Posted March 12 Solution Share Posted March 12 (edited) Although I'm not familiar with that game specifically, "deploy after" is for all intents and purposes useless regarding conflict resolution or their load order management. The only practical use of "deploy after" I've ever seen (in BGS games) is when making one game config ini file deploy after another copy of the same game config ini file that don't share the same name (not in direct conflict), which both edit the same values = deploy after enforces these value changes in one game ini config file over another. Edited March 12 by vortexposer Link to comment Share on other sites More sharing options...
CooKyzz Posted March 12 Author Share Posted March 12 1 hour ago, vortexposer said: Although I'm not familiar with that game specifically, "deploy after" is for all intents and purposes useless regarding conflict resolution or their load order management. The only practical use of "deploy after" I've ever seen (in BGS games) is when making one game config ini file deploy after another copy of the same game config ini file that don't share the same name (not in direct conflict), which both edit the same values = deploy after enforces these value changes in one game ini config file over another. Ooh that makes sense ! I didn't thought about ini config files, well thanks ! I think i have a pretty good idea of each function now, i'll mark it solved. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now