10 réponses à ce sujet

[mikemike37]

Here are a few common questions: 

• Why do i need to export/post to local?
• Where do exported files go?
• Which files do you need me to give you for this to work?
• I want to override this, where do I put it?
• When I install a dazip, where does it go?

And I've never really been satisfied that any one page could give a full understanding of Dragon Age files, folders and the database. So I started with a diagram... and decided it needed to be explained in a video tutorial. 

Toolset Fundamentals - Files, Folders and the Database

The Builder's page with the diagrams can be found here:

Understanding Files and the Database



It took me long enough to figure it all out, I hope this video helps others get up to speed faster than me!

[Beerfish]

Great job mikemike

[Wulfeous]

Thanks a lot

It always a good idea to have a good understanding of the overall project before delving into it's individual parts

[d0de]

These videos are so helpful please keep them coming.

[BloodsongVengeance]

i still have one question that's been puzzling me...



for "The Override," i use the game directory\\packages\\core\\override.



what's up with the documents directory\\bioware\\etc\\override?



...okay, sorry, another question from looking at the charts...

addins\\addinname\\ core and module override stuff... says that it affects my add-ins and its extentions only.



is this to say that files IN the addins sub-directories DO affect my module? in the game?? because wouldn't that conflict with the override files in the game-directory override?



have i totally been doing it wrong all this time???? hey, i came from nwn, we had ONE game directory and it had ONE override directory, and you couldn't even use sub-directories in it!

[DarthParametric]

The global Override folder is My Documents\BioWare\Dragon Age\packages\core\override\. If you are only overriding files in a specific addin then you use that addin's Override folder. Mike addresses this in the video.

Modifié par DarthParametric, 21 septembre 2010 - 03:09 .

[mikemike37]

BloodsongVengeance wrote...
i still have one question that's been puzzling me...

for "The Override," i use the game directory\\\\packages\\\\core\\\\override.

yes, this is the global override, which affects everything for all users all of the time.

BloodsongVengeance wrote...
what's up with the documents directory\\\\bioware\\\\etc\\\\override?

the "etc" you miss out is quite critical here: the override in "packages core" (the user's global override) affects all modules for only that user, all of the time. in "addins core", it affects all core resources for ONLY the module (and anything it is marked as extending). in "addins module", it affects the module resources for ONLY the module (and anything it is marked as extending).

BloodsongVengeance wrote...
...okay, sorry, another question from looking at the charts...
addins\\\\addinname\\\\ core and module override stuff... says that it affects my add-ins and its extentions only.

is this to say that files IN the addins sub-directories DO affect my module? in the game?? because wouldn't that conflict with the override files in the game-directory override?

yes, stuff in addins CAN affect your original game. This is the CORRECT way to do so (rather than heaping everything into either of the global overrides). What it affects is dictated by the choice made for "extended module". Here, the modder MAY choose ONE of:
Core Game Resources (affects everything)
Single Player (affects Single Player only)
*3rd party mod* (affects only *third party mod*) - can be used for patching or modding other people's mods.

If it is NOT set to extend anything, then it only affects stuff within its own module (ie. it is a standalone module)

[ladydesire]

mikemike37 wrote...

BloodsongVengeance wrote...
...okay, sorry, another question from looking at the charts...
addins\\\\\\\\addinname\\\\\\\\ core and module override stuff... says that it affects my add-ins and its extentions only.

is this to say that files IN the addins sub-directories DO affect my module? in the game?? because wouldn't that conflict with the override files in the game-directory override?

yes, stuff in addins CAN affect your original game. This is the CORRECT way to do so (rather than heaping everything into either of the global overrides). What it affects is dictated by the choice made for "extended module". Here, the modder MAY choose ONE of:
Core Game Resources (affects everything)
Single Player (affects Single Player only)
*3rd party mod* (affects only *third party mod*) - can be used for patching or modding other people's mods.

If it is NOT set to extend anything, then it only affects stuff within its own module (ie. it is a standalone module)

I hate to be the one to throw the monkey-wrench into the works, but this is the "Ideal"; due to a bug that I am trying to work around, this does not happen in practice. It's my understanding that the Extended Module property, along with Module Priority, should control whether or not a given add-in's Core Resources are available or not, but it seems to ignore the Extended  Module when a Stand Alone campaign is selected.

[Wrathra]

Thank you for this.

[mikemike37]

youre welcome

[DahliaLynn]

Thank you very much for making this. Definitely sheds *sigh* -much needed- light !!

Modifié par DahliaLynn, 24 septembre 2010 - 02:22 .