I'm still working on getting new Base Item Types working for Arms and Armor, and ran into something curious on the BITM_Base 2DA file:
As far as I can see, the only worksheet that contains which Variation worksheet a Base Type should use is _SourceData. My 2DA for Arms and Armor consists of three worksheets: BITM_Base, ItemStats and _SourceData. However of the three, only BITM_Base and ItemStats are converting to GDA format (I'm using DAToolchest to do the conversion). _SoureData is NOT converting. I didn't think anything of it at first, but now am wondering if this could be my problem since it's the only worksheet that specifies the Variation worksheet.
What's more interesting is that the ReadMe worksheet says that changes to weapons/armor should be made in THAT worksheet, not the BITM_Base and ItemStats sheets....
Anyone have any thoughts on this?
BITM_Base Question
Débuté par
Ambaryerno
, nov. 27 2009 04:35
Retour en haut
#2
Posté 27 novembre 2009 - 05:18
Phaenan
-
- Members
- 315 messages
Well... At the very least I can say that BITM additions through M2DA aren't fully taken in account without that _SourceData. I've also tried to add some base types, and while the toolset and scripts (Get*M2DA() functions) can see and properly access the new types without _SourceData, the game engine itself insist of pretty much ignoring the changes. Couldn't figure why.
I'll prolly try the convert that SourceData sheet, or create it from scratch with GDApp and see if it changes anything.
I'll prolly try the convert that SourceData sheet, or create it from scratch with GDApp and see if it changes anything.
Modifié par Phaenan, 27 novembre 2009 - 05:19 .
#3
Posté 27 novembre 2009 - 05:30
Ambaryerno
-
- Members
- 532 messages
Phaenan,
Yeah, that's the exact same problem I'm having. New base types work just fine in the Toolset, but the game itself won't use them.
I tried to rename the SourceData sheet by removing the "_" in front, and that got DAToolchest to find it, however there's a definite formatting issue. _SourceData is missing that second line that states whether a column is a String, INT, etc. I'm trying to modify it to include that line and see what it does....
Yeah, that's the exact same problem I'm having. New base types work just fine in the Toolset, but the game itself won't use them.
I tried to rename the SourceData sheet by removing the "_" in front, and that got DAToolchest to find it, however there's a definite formatting issue. _SourceData is missing that second line that states whether a column is a String, INT, etc. I'm trying to modify it to include that line and see what it does....
#4
Posté 27 novembre 2009 - 05:51
Ambaryerno
-
- Members
- 532 messages
FYI, this is something I've played with trying to get my mod to work:
I've set the Warden Sword to new base type (Arming Sword, replacing the 1H longswords which in my mod are becoming 2H). I added a line in my mod script to add this sword to inventory. It never appears.
I set the Warden Sword BACK to Longsword as the Base Type and the script successfully added it to inventory.
Next I set the Warden Sword to use the GREATSWORD as a Base Type. The script successfully added it to inventory, but it showed up as a LONGSWORD, despite what I set for the Base Type.
I'm thinking there HAS to be somewhere else the game is pulling Base Type from.
I've set the Warden Sword to new base type (Arming Sword, replacing the 1H longswords which in my mod are becoming 2H). I added a line in my mod script to add this sword to inventory. It never appears.
I set the Warden Sword BACK to Longsword as the Base Type and the script successfully added it to inventory.
Next I set the Warden Sword to use the GREATSWORD as a Base Type. The script successfully added it to inventory, but it showed up as a LONGSWORD, despite what I set for the Base Type.
I'm thinking there HAS to be somewhere else the game is pulling Base Type from.
Modifié par Ambaryerno, 27 novembre 2009 - 05:55 .
