6 réponses à ce sujet

[Travus]

I've been toying around with custom packages for clerics with different domains. I make the edits in the packages.2da file, put it in the override folder, and it works in game with no problems. But when I put the packages.2da in a the campaign folder or in a HAK file associated to the module, it doesn't work.

I can read the edited 2da file in the toolset regardless if it's in the override folder, campaign folder, or a HAK. I've also checked to make sure there are no other copies somewhere that are causing a conflict.

 

I remember reading somewhere that some 2das don't work outside of the override folder. Could the packages.2da be one of those files? If not, is there something I'm doing wrong that's preventing the packages.2da working from the campaign folder or a HAK?

[andysks]

I think all 2da work from a hak. I could be wrong, but I always thought that that's the case. It would be false design to have a file that can't work outside of an override folder, which most of us use solely for testing and building and not packaging. 

[Psionic-Entity]

Yeah packages.2da has known (at least to me through previous work) problems when running out of a hak file. I believe the issue is running outside a certain index. I found that editing default packages worked just fine from 2da, but custom ones (added to later rows) weren't having their magic-related entries read properly. You might be able to work something out if you shuffle around and edit pre-existing packages but when you want to add ones lower down you might not get good results.

[Travus]

@Psionic

I used your advice and edited an already existing package. Unfortunately, it still doesn't want to play nice outside of the override folder.

 

It's strange, as I've seen other mods use the packages.2da from a hak and it appears they work well enough. I don't know why mine is being stubborn. Oh well. I'll just keep the 2da in the override for now and tinker with it a bit more.  

[Psionic-Entity]

The problem I had was related to spell selection, not domains, and those were actually fixed by moving rows. Are you able to clarify which parts of the new packages aren't working for you and what the error looks like? There could be workarounds if it's not too severe.

[Travus]

The problem really revolves around the fact that cleric companions always get the air/animal domain spells regardless of what their domains actually are. For example, I have a cleric companion with the healing /protection domains, but his domain spells end up coming from the air/animal domains due to some bug in the game. To get around that part of the problem, I just edit the companion's OnSpawn script to do a  SetLevelUpPackage and ResetCreatureLevelForXP. Normally, with an already existing package, this method works fine. But with a unique package like healing/protection, I need to create a new package in the 2da. This brings us to the issue at hand. I create a new package in the packages.2da (in this case, it's line 203 in the 2da) and apply the edits to the OnSpawn, which are:

 

SetLevelUpPackage(OBJECT_SELF, 203);

ResetCreatureLevelForXP(OBJECT_SELF, 0, TRUE) 

 

The new line in the 2da is essentially a duplicate of the default cleric line. The only difference is the sun domain number is changed to the protection domain number.

 

Everything works just fine if the packages.2da is in the override folder. But if I have the 2da in the campaign folder or an assigned hak, it doesn't work.

[Dann-J]

Yeah packages.2da has known (at least to me through previous work) problems when running out of a hak file. I believe the issue is running outside a certain index. I found that editing default packages worked just fine from 2da, but custom ones (added to later rows) weren't having their magic-related entries read properly. You might be able to work something out if you shuffle around and edit pre-existing packages but when you want to add ones lower down you might not get good results.

 

I tried replacing one of the existing packages with one of my new ones, and renaming my override folder so I was only using the 2DA from a HAK. Unfortunately It didn't work for me - although admittedly I replaced one of the non-functional packages left over from NWN. I'd rather not replace a functional NWN2 package, since it might be one that a player chooses for their PC.

 

This is a problem, since one of the companions in my current module has a custom PrC (Warsling Sniper), so he needs a new package in order for the player to level him up manually. Since I'd rather not have to instruct players to put one (and only one) of my modified 2DAs into the override folder, that leaves me with two options; strip him of his custom PrC, or create an automatic level up script for him. The latter prevents the player from having any say in how the companion levels up, but at least he retains his cool halfing-specific PrC.

 

I'll also have to rethink the cleric companion. He currently has the Animal and Sun domains, and relies on a custom package to auto-level him at the start of the game to get around the Air/Animal bug. However any package with Animal in it should do, since his animal companion is an integral part of his backstory.

 

It will be easy enough to change the fighter/weapon master companion to specialise in longswords. He currently specialises in battleaxes (the favoured weapon of Tempus), but statistically speaking a battleaxe isn't much different to a longsword, and the many fighter and weapon master packages that already exist seem to have longsword fetishes.