With the toolset, we now have access the 2DA files (tools\\Source\\2DA).
If I wanted to create a small test mod that simply overrode--oh, I don't know--AOE.xls, for instance, is that something we can do under this semi-new scheme used for DA:O? And if so, how?
Mind you, I only installed the toolset a couple of hours ago, but from reading things here and in the Wiki, it seems a lot more complex to add stuff to the game as opposed to previous BioWare games where you just threw stuff in the override folder. (Note: I prefer complexity over simplicity since complexity generally allows for greater control, so that's not a complaint!!)
Overriding 2DA Files
Débuté par
Talian Kross
, nov. 07 2009 11:31
#1
Posté 07 novembre 2009 - 11:31
#2
Posté 08 novembre 2009 - 12:43
That's possible. I think what you'd do is copy the excel file, rename the workbook to create a new M2DA extension to the original (see the 2DA page on the wiki for an explanation of M2DAs), delete all the rows except the ones you'd like to modify, modify those rows, and then export the 2DA to the appropriate override directory (again, see the 2DA page on the wiki for instructions on how to export a 2DA). For something like AOE that'd probably be the core override directory for your mod.
#3
Posté 08 novembre 2009 - 01:05
First, I'm embarrassed to admit I didn't know there was a 2DA entry on the Wiki.
It's not directly cited on main page, but typing "2da" in the search box just now, I see what you are talking about. That's a lot of info there! 
Second, you mean now we can just alter specific rows and leave the unaltered rows out? That is just too fantastic. Mutually exclusive 2da mods overriding each other will be a thing of the past now.
Third, off-topic, and not that you did it for us in mind, of course, but thanks nonetheless for switching to excel format rather than the old plain text, csv-ish format. In former games (of yours), I always imported them, edited them, and then export them in excel anyway, so this was a pleasant surprise.
Anyway, thanks! I'll go read that 2da wiki entry page now.
Second, you mean now we can just alter specific rows and leave the unaltered rows out? That is just too fantastic. Mutually exclusive 2da mods overriding each other will be a thing of the past now.
Third, off-topic, and not that you did it for us in mind, of course, but thanks nonetheless for switching to excel format rather than the old plain text, csv-ish format. In former games (of yours), I always imported them, edited them, and then export them in excel anyway, so this was a pleasant surprise.
Anyway, thanks! I'll go read that 2da wiki entry page now.
Modifié par Talian Kross, 08 novembre 2009 - 02:05 .
#4
Posté 08 novembre 2009 - 01:13
Just remember that not all 2DA's are like that. If you look at 2DA.xls, you will see the list of them. For instance, if I am not mistaken, var_creatures actually has to be overrided, so to speak (possibly because it is read from within the toolset?).
I can't check, because I uninstalled the toolset so I won't be tempted to build, instead of playing the damn game at least once through!
I can't check, because I uninstalled the toolset so I won't be tempted to build, instead of playing the damn game at least once through!
Modifié par Challseus, 08 novembre 2009 - 01:13 .
#5
Posté 08 novembre 2009 - 01:23
I'll keep that in mind. Thanks!
#6
Posté 08 novembre 2009 - 01:54
As a follow-up, the wiki states how 2daExplorer.xls is used to convert the excel file into a 2DA usable by the game (Wiki Reference).
That file didn't seem to get included in the toolset. Am I just not finding it, or was that an oversight?
Note: I did find ExcelProcessor.exe, so I know there is a viable alternate solution; but still, I am curious about 2daExplorer.xls and why I can't find it.
That file didn't seem to get included in the toolset. Am I just not finding it, or was that an oversight?
Note: I did find ExcelProcessor.exe, so I know there is a viable alternate solution; but still, I am curious about 2daExplorer.xls and why I can't find it.
#7
Posté 08 novembre 2009 - 02:27
Could be that it was left out of the toolset download. It wasn't the greatest tool, though - we used it internally and it worked for us, but the macro in it blew up when presented with a path that had spaces in it (such as ones containing "My Documents" or "Program Files".) So perhaps it's for the best, the alternatives are superior in this case.
#8
Posté 08 novembre 2009 - 04:24
Okay. Thanks!
#9
Posté 08 novembre 2009 - 04:59
Yeah, there's a method for the batch file mentioned somewhere in there. That should work instead.





Retour en haut







