Gruftlord wrote...
could someone be so kind as to answer a few questions for me?
currently i have the latest release candidate (V2) of 1.71 installed and working.
i'm trying to find out how much 2da merging and hak editing i have to do for various situations.
hi, first of all, you dont have to
but if you want to get all CP changes working its quite a lot actually - but for this task there is Auto2DAMerger tool that should do that automatically - if you arent that type like me who needs control over this, if you are then you have to do it manually to easier maintain/see changes over vanilla and maybe decide to discard some of them
now to the questions:
say i have a module that uses CEP (lets assume v2.3). will i benefit from all the spell and class changes and other client side changes?
yes you should be automatically benefit from class/spell/feat changes and improvements because CEP doesnt use these 2DAs afaik - Ive already merged CEP2.4 2DAs for one builder, you can find it in
project fileshow mayn of the spell and feat changes are overwritten by the CEP?
CEP doesnt uses these 2DAs but if it was, then read my next answer
or do i need to merge the 2das and put them in my CEP custom hak?
for those 2DAs that CEP contains and which were changed, you should merge/re-apply CP changes in them and then place in cep2custom hak which should have top priority in your module hak list - alternatively you can place these 2da into any custom top hak you might have or even back to the any of the cep2top hak to avoid cep2custom if you have some reason to
and what is with old modules from the vault? it says in the description that scripts in the module will overwrite the fixes/take precendence over CPP. under what circumstances are those scripts in there anyway?
good question, mostly if the module creator changed some spells to deal more damage or changed behavior if caster wears item of specific tag - very rare but happens, not something you should be worry about as most bugs CP fixes are minor, merely visible or very specific.
all vanilla scripts all the time, and i basically have to update every mod myself?
or are only those scripts packed inside a module, which have been changed specifically for said module (i.e. usually only very few changes to base spells)
this, any script that is not in module is automatically loaded from data/patch_171.bif so if you feel its neccessary and I assure for random SP modules its definitely not - you have to manually update only scripts inside such module
from the wiki about CPP i figured nothing will break i any case (at least this is supposed to be that way). i.e. if the module/hak contains a custom overwrite, this will work as always, and just not benefit from any new changes/fixes. does this still hold true?
yes but there are special cases where its true only partially, say you have AD's first version of colored spell icons, but you still have default scroll icons-aka you dont have any custom spell icons in your override - then after installing CP1.71 you might notice some of the scroll icons changed and now, since spell icons from your override are used, they dont match their counterpart as CP1.71 uses AD's gen2 spell icons and some of them are brand new - and scroll icons now reflect this.
edit: if i use the 2damerger and use first "replace only vanilla" and then try to use "hak version" the merger aborts and the appearence.2da is messed up at the first column in line 307 (so first edit from hak merge script). did i do something wrong?
you have to be carefull with this tool, its wasnt tested in every possible situation and the author lost source so he can't further support this tool - regarding your issue, its very probably limitation of the tool itself, sometimes its bugged and you should recheck if the outcome is okay. In case that not, try to "standardise" your 2da - remove empty line after columns definition, fix the row numbers (Im using 2daEdit 0.63 for that - after resacing automatically renumbers lines) etc... in case there is need to add new collumn, you have to do it manually this tool will not handle this...
anyway one word of caution woth hak version changes - if you dont use anything else than CEP, you can't use these changes, because clients need them too. It would make a incompatibility issues and players wouldnt be able to see for example "new" NPC models because their appearance.2da in CEP haks doesnt have them. A truly compatibility with CEP can be done only if CEP inherits the 2DA edits from CP and make a new version - which I fear never happens :innocent: (I approve that btw)
hope that answers most of your questions
