When I combine .2da files to integrate various haks into my campaign, I am sometimes compelled to change the line number because the line number from the .2da that came with the hak is already taken by some other custom content. Everything seems to work fine, but I am concerned that there may be unforseen trouble. Am I missing something, or is everything okay?
What happens when I change the line number of a .2da entry
Débuté par
M. Rieder
, avril 06 2011 01:22
Retour en haut
#2
Posté 06 avril 2011 - 01:57
MasterChanger
-
- Members
- 686 messages
I think it really depends on the 2da, but there will very often be issues that you need to address. What will make the difference is where the entry is referenced by other content.
For example, placeables.2da or appearances.2da might have blueprints that reference those entries. I'm almost positive that the blueprint will NOT update when the line # it refers to changes (yes, an orc blueprint might tell you the appearance is "Orc" but it's really using the line linked to the "Orc" tlk entry). You'd probably have to manually update these blueprints--don't do anything else in the TS while doing this because there could well be crashes.
Spells.2da or feat.2da very often reference each other. You definitely want to preserve these connections. Feat or spell ID's are also frequently referenced by scripts, whether by using a constant or just the line number every time. I'm not positive, but I'm pretty sure that every time you update a constant's defintion you also need to re-compile the scripts that use it in order for them to be udpated as well (I know this is true in nwscript for functions and can't imagine it's not true for constants).
In short, reserved ranges are very important. Unfortunately, sometimes it's not possible to follow reserved ranges or a creator simply didn't. I know sometimes I haven't paid attention to them when doing my own work, but actually publishing stuff that doesn't use these ranges really limits the usage that an author's work will get.
For example, placeables.2da or appearances.2da might have blueprints that reference those entries. I'm almost positive that the blueprint will NOT update when the line # it refers to changes (yes, an orc blueprint might tell you the appearance is "Orc" but it's really using the line linked to the "Orc" tlk entry). You'd probably have to manually update these blueprints--don't do anything else in the TS while doing this because there could well be crashes.
Spells.2da or feat.2da very often reference each other. You definitely want to preserve these connections. Feat or spell ID's are also frequently referenced by scripts, whether by using a constant or just the line number every time. I'm not positive, but I'm pretty sure that every time you update a constant's defintion you also need to re-compile the scripts that use it in order for them to be udpated as well (I know this is true in nwscript for functions and can't imagine it's not true for constants).
In short, reserved ranges are very important. Unfortunately, sometimes it's not possible to follow reserved ranges or a creator simply didn't. I know sometimes I haven't paid attention to them when doing my own work, but actually publishing stuff that doesn't use these ranges really limits the usage that an author's work will get.
#3
Posté 06 avril 2011 - 02:19
M. Rieder
-
- Members
- 2 530 messages
Right now I am only altering Appearances.2da and Placeables.2da. I have already noticed that the blueprints are off, but once I update them they are fine.
Thanks for the info. I will keep that in mind if I have to change any other .2da's.
Thanks for the info. I will keep that in mind if I have to change any other .2da's.
#4
Guest_Chaos Wielder_*
Posté 06 avril 2011 - 03:20
Guest_Chaos Wielder_*
Guest_Chaos Wielder_*
-
- Guests
Appearances don't update when changing lines. So, Orc at 1000, let's say, won't keep the constant appearance if you move the Orc's model reference to line 2000 and make a Stirge at 1000. Take it from the mouth of a frustrated 2da artist.
