Looking for betatesting CPP 1.72 and NWNX_Patch plugins

[Legacy_Shadooow]

               

Since not everyone checks my overspammed development thread I decided to cry for help in this way.

 

I am desperately looking for a players and builders who would test my new CPP and nwnx_patch/nwncx_patch version. I would like to release a final version soon but I can't release it in this state as one guy can't test project of this scope alone and so I expect there will be bugs and issues. This is not ordinary hak, I can't release it and provide fixes later when issues will be found, it must be perfect without flaws.

 

To do that I need more peoples using my newest versions.

 

You can get CPP 1.72beta14 here.

 

To install it, follow as in 1.71 manual installation: simply unpack the archive into folder with NWN files (thus if you do this right it will want to overwrite bunch of files which you have to confirm). The 1.72 is international, works for all languages as there are no changes in dialog.tlk file yet. Note: you don't need previous CPP versions installed before installing 1.72.

To uninstall it, either run 1.69 critical rebuild, 1.71 installation, or manually delete/rename the xp2patch.key file and rename the xp2patch171.key which is included in the 1.72 beta distribution.

 

You can get latest nwnx_patch and nwncx_patch here. (version 18a, newer than what contains the 1.72beta14package!) To run this you need NWNX2 package (if you are running server) or NWNCX package if you are player and run game/server with respective loaders.

 

 

 

What I need from betatesters is to install these files and just play or build as normal but report anything unusual in this thread. You don't need to play with NWNX if you don't have it or you don't want to risk any potential issues, just testing CPP1.72 without nwnx will help me.

 

Also while the NWNX_Patch has some features dependant on CPP 1.72 (like softcoded scripts) it must be working flawlessly and without issues with vanilla NWN as well. So, I need to also test using nwnx_patch with vanilla 1.69.

 

You can report any issues or unexpected behavior here (or send me a PM if you prefer), I will try to react as fast possible and fix any potential issues you will find. Note, that the best way to help me is to provide a savegame (with required haks if any) with the bug or before the bug so I can reproduce it.

 

If you want to know what it should do, here is incomplete readme [WIP].

CPP 1.72 readme

CPP 1.72 NWN©X_Patch readme

NWNX_Patch, custom spellcasters feature notes

NWNX_Patch, effect caster level notes

but since this is incomplete and I will be slowly updating that, maybe you can skip reading readme at all, just report anything unusual, I will tell you if its intented or not.

 

PS. Like this post if you will help with this task, don't like it otherwise - this way I can know who is helping with this and who to perhaps contact privately if needed.

               
               

               
            

[Legacy_Gruftlord]

               Sadly i don't have the time for extensive testing atm.


Does the link here go to the very latest version already?


I like the new readme/documentation. Are the old ones (1.70+1.71) up to that standard already? And is there a complete version listing the whole content of the most current CPP?
               
               

               
            

[Legacy_Shadooow]

               

I like the new readme/documentation. Are the old ones (1.70+1.71) up to that standard already? And is there a complete version listing the whole content of the most current CPP?

I haven't finished readme for new version and you ask me if I went back and upgraded readme for older version '> .

 

No, not yet, I really hate this job. Also my english is not perfect and I write with lot of grammar errors .

 

But I don't know if making a full readme of 1.71+1.72 is good idea. Lot of peoples are already read the 1.71, if I will add new changes into that readme, it will confuse them reading the same stuff over, even when I would distinguish that with color. I think its better to have separated readme for 1.71 and 1.72, afterall some players/builders will not want to adapt 1.72 at all (as it goes a little too far in some aspect, farther than builders need to).

               
               

               
            

[Legacy_Gruftlord]

               you could adopt the change log style of the unofficial skyrim patch. they add the new changes on top in pretty much the same fashion as your 1.72 change log, including subcategories starting with fixes for their own mistakes.
but what they then add to the older patchlogs found further down in the list are references to everything that has been changed in a newer patch, like stricken through entries that mention in which later patch the fix was revised. this is i guess a good way to keep an up to date full list, that still contains all relevant, temporally sorted, data and is easier to maintain than one complete log that you rework fully each time.