Updating old modules thats req CEP1/2 with up to date haks - smart or Dumb ?

[Legacy_R-TEAM]

               Hi,

the short story behind this ...
I played NWN 1 now from 2004/2005 on ...
I haved never problems with custom modules.
Last week ... i and an other player would play endless-Night-IV CEP version ...(now i know an CEP2 working version is here '>  )
We have updated NWN to the Max - 1.69 with many overrides and the 1.71 patch ...
The game runs nice - but suddenly the client crashes (have the mod self running on the server NWNX and he still runs after the client crashes ..) ... after a little bit investigating, we found it crashes by entering the potions shop.
O.K. - we think the mod is outdated and move to another module - Hythum4.0 with CEP ... and he crashes too after try to open the alchemist shop (potions) .. that give me an bad feeling - everything is wrong with my NWN install .......

I delete the 1.71 patch - no luck
I remove the big override folder - no luck
I tryed with an pure 1.69 NWN - no luck ......

Then i remember an old thread in an forum i have read long time ago ... it was over updating the CEP hak files in an modul .... i think "the modul runs anyway not - so i cant make it more bad if i try this ..."
O.K. - load the modul (Hythum4.0) in the toolset and link the newer CEP 1 haks to it, from 1.50 to 1.68 version ..
And .................. IT RUNs ... no more crash by entering the alchemist shop .........

NOW i have a couple of questions .....

It is a bad or a smart idea to update old modules that uses an old CEP version ?
Will it be run better ?
Or my crash or make strange things ?

The second question is related to the first ....
IF updating an good/smart idea ... how it is with the "Inofficiall" 169 cep 1 update ?
I have read many rumors .. from "it will fix nearly all bugs left and run nice with NWN 1.69 ..." to " ... dont harm the CEP team for crashes of this bad pice of coding .." i have read all sort of things ... so i dont know will it run good ...

And at least .... how it is to update CEP2 modules ?
The same as with CEP1 ?
Have read here too, many "bad" thing ... (specialy over the 22 to 23 update ...)

So the holy gral of the CEP updating question is :
If its smart to update old modules to the latest available versions and if this going on with all CEP versions ( 1 and 2) and if this good for the "myserious" CEP1 169 update too ??

Hope of enlightment '>

Regards
R-TEAM
               
               

               

                     Modifié par R-TEAM, 15 mars 2013 - 09:49 .
                     
                  

            

[Legacy_Shadooow]

               if it crashes when opening shop then its probably related to the item with nonexistant baseitem, can you open that shop it in toolset? do you see all stuff here normally or you see X icons somewhere?

to your questions with CEP2: I wont suggest you use or not use CEP2 thats on a thread itself. But adding CEP2 hardly fix the issue you have, I suggest to track the cause of that issue and fix it first then consider switch to CEP2 if you like.

Do you have a last working version of that module? Something had to changed so thats where I would start. If not, send me the area with that shop with the baseitems.2da from your hak and I take a look whats wrong there.
               
               

               
            

[Legacy_R-TEAM]

               Hi,

Thanks ShaDoOoW to trying to help me '>
But you have a little bit missunderstand my post ....
(sorry - english is not my native language - and as the text grow - the errors grow too '> )

To answer your helpfull post and clarify some thing ... :

I have finaly managed to have the problem modules running.
One was EndlesNight 4 CEP1 version (maybe an older version) and i have found on the vault site an CEP2 version that is working - so this modul is working (the CEP2 version) flawless now ..

But it was in my "story" relevant as it was the first modul that crashes by me, but as an singular event i dont get much attention on this on this time .... only after the crash from the second module "Hythum 1 CEP1 version" and here on the potion shop too - i overthink the "problem" -> 2 modules with CEP1 crashes by entering the potion shop......

I try to fix then the Hythum module (no newer version is available) by "updating" the CEP1 version he uses ...
In the orginal only "cep1patch.hak" was bound to the module.
I add over this "cep1patch150.hak" and over this cep1patch152.hak and cep1patch168_ck.hak.
So it uses now CEP168, the last officiall CEP1 version.
And it runs now without crash by entering the potion shop ....

So ... my questions are related to upgrading old modules with newer CEP versions from the SAME general CEP version.As CEP1.50 to CEP1.68, NOT CEP1 > CEP2.

I like to know is this an smart idea (the hythum module runs now without crash), the modules get an newer/more bug-free version of CEP, or can this be going to instability or bad side effects, as the developer of the modul work with CEP1.50 as example, and i use it now with CEP1.68 ....

So i dont know should i modify all of my CEP1 modules to work with CEP1.68 now ?
Will i get an benefits of this ??
(besides the questions over CEP169 and CEP2 related ... this we can discuss later '> )

Regards
R-TEAM
               
               

               
            

[Legacy_Malagant]

               The only added benefit of CEP 1.68 that I remember was that it overrides visible cloaks to maintain compatibility with older CEP build modules, but made CEP compatible with the rest of NWN1.68. A separate cep1patch168_ck.hak was released with it if you wanted to use the cloaks.

As far as "newer/more bug-free version of CEP", the only thing CEP 1.68 added outside of cloaks or no cloaks were the tridents they copied over from NWN 1.67, but with no working trident-specific feats because those feats were not added until NWN 1.69. In that respect, I don't think there was anything remotely new or bug free over previous versions.

I don't feel that there is any real benefit unless you have to have those tridents, but that is just my thinking on it. There is little of a noticable return.

As for CEP 1.69, this was not an official CEP release to my knowledge. I seem to recall Barry launching a tirade about this a one point, though it's original vault page was somewhat deceptive about this by billing it as "CEP approved" and the author that posted it claimed to be "CEP 1 Team".
               
               

               

                     Modifié par Malagant, 25 mars 2013 - 08:24 .
                     
                  

            

[Legacy_R-TEAM]

               Hi,

thanks Malagant,
as a side note, i use the 168_ck version to have the new cloaks.
thanks to clarify that an use of the last official patch (168) is not a "musst have",
but should not harm if i musst edit the hak list anyway.
(if i add only the versions till 152 or one more,168, make not an diff)

But think you i can get into trouble if i add to an old modul newer CEP1 versions ?
As it have the modul fixed for my NWN169, i see ATM not an bad idea to update all of the moduls i play, that use CEP1, to open in the toolset an add newer CEP1 version Haks....

Thanks for the hint for the CEP169 version - i know it was non official relase and was an triade over this ... but this musst not mean the relase is bad or corrupt ...
But i dont know if it realy fix outstanding bugs in CEP1 and add better compatibility with NWN169 or make nothing real good and break maybe compatibility with CEP1 ..?
(the CEP169 patch is with 138MB not small like the 152/153/168 patches ...)

Regards
R-TEAM
               
               

               
            

[Legacy_Malagant]

               There should not be any issue with adding it to an older module most of the time, but keep in mind that when you save the older module it will now require whatever version of NWN you currently have installed. This sometimes causes conflicts within the module resources, but those conflicts will be specific to that module and will depend on things the builder has implemented.