Main menu
Secondary menu
You are here
CEP1 Complete (Pre-Release)
Warning: This is pre-release version and its possible this will be yet changed on the suggestions from community, so you might need to redownload this in near future. Consider as beta for testing purposes for now. If you struck into any issue with this version please report immediately in comments.
This is a new version of the CEP1 intented to work as an ultimate all-in-one and all-updated to 1.69+CPP. This CEP version is 100% backwards compatible with every CEP1 version and every module using CEP1.
With this version, every single module using CEP will be automatically updated to 1.69 regardless of which CEP1 version it was created for.
The actual file size on disk is 40megabytes less than original version due to the number of duplicated/conflicting files removed.
Contains these haks:
cep1patch169 (but the hak content is from cep1patch171, but this version is from now on unsupported)
cep1patch168
cep1patch168_ck
cep1patch153
cep1patch152
cep1patch150
cep1patch
cep2da
cepanatomy
cepbaseitem
cepcreature
cepplace
cepportrait
ceptexture
But their content is very different from the original version. Basically all content from the cep1patch* haks has been pushed into core haks. The cep1patch* haks now contains only 2DA files (for compatibility reasons). Thus even if module uses first CEP version, with CEP Complete it will act as a CEP1+150+152+153+168+169 applied.
Except cep1patch168.hak, all haks now use new 3D cloaks from NWN Patch 1.68. But modules created with non "ck" version of cep1patch168 will be of course with old inventory-icon style cloaks and no 3D models upon equipping as intented.
Info for builders who wish to build with CEP1:
While with this version, normally all you would need is the non-patch haks, there are still players without this version, so you must take this in consideration. From this reason, you have to add into your haks even the ceppatch haks to provide backwards compatibility.
So the hak list should look like this:
cep1patch169
cep1patch168 or cep1patch168_ck (doesn't matter really)
cep1patch152
cep1patch150
cep1patch
cep2da
cepanatomy
cepbaseitem
cepcreature
cepplace
cepportrait
ceptexture
Info for developers:
I can do only so much for this project. There are still some features that needs to be added:
- installer (or just the 7zip executable but with the CEP1 icon - like in CEP v1.X Installer)
- some readme
- perhaps modify the readme.txt files inside CEP haks and also CEP haks descriptions which are telling fairy tales about CEP Updater and point to no longer existing site nwncep.com
- new page for CEP that would act as a CEP hub (this is something that CEP2 would benefit from as well)
- possibly move this into former CEP v1.X Installer page and delete this one once it will be all set up
History:
6.6.2015 - added documentation, ef, module and tlk from CEP v1.X, this means its allinone package now, not needed to get CEP from elsewhere first
25.1.2015 - several miscelanious icons conflicting with 1.69 restored to previous old cep version in order to maintain consistency with possible premade items
| Attachment | Size |
|---|---|
 cep1complete.7z (7000) | 136.73 MB |
This has helped so many mods.
I agree with Savickster. My older modules are running much better with this hakpak.
Missing .tlk file and cep_crafting.erf apparently.
Still the best version.
Is this still pre-release? It seems to work pretty well from the CEP1 modules I've played with it, certainly stable.
My understanding is that this project is obsolete.
If I'm right, the only version you need to play CEP1 modules is:
http://neverwintervault.org/project/nwn1/hakpak/combined/cep-v1x-installer
I think this project includes cep1patch169.hak, which is not in the combined cep-v1x installer.
The CEP 1.X Installer only includes up to the last officially released version. This updates all of them to the 1.69 one to prevent bugs. That way modules which were made on the first version of CEP still function identically to one made with the CEP 1.69 update and all that.
Well, this is very confusing. Last time we tried to reach consensus on this, CEP 1.x installer seemed to be the one; the discussion got sidetracked on Community Patch, though.
EDIT - reading the small print, this version includes CPP. Bearing in mind that very few modules are certified for CPP, and that CPP remains controversial, It seems to me that we ought to recommend CEP 1.x installer for genreal puposes, with a link to this one for anyone who wants CPP.
It would be a big help to new and returning users if we archived the other versions, linking modules to CEP 1.x installer (where links to this CPP version and the others could be provided for good order).
I think this one would probably be the best since it encompasses all the fixes and brings all the older CEP1 modules on the same page version-wise. It's just a lot of links to change since quite a few modules use CEP1.
One solution could be just merging this project page with the CEP1.X Installer one, that cuts down on changing links and keeps it all in the same page, like he mentioned in description.
Sorry, I edited my post after you replied. We seem to agree though that offering CEP 1.x installer with the CPP version as an option is the way forward. That way, neither is "best", but players should understand that choosing CPP has pros and cons.
Im starting to get seriosly offended by post like this.
It is clear you are not using CPP, nor do you know what it does and how it does it. It is clear you dont like the project personally too.
This CEP version is not obsolete. It is meant to be the all in one CEP package and replace cepvx you linked.
The difference here is that this version makes all cep haks to be compatible. with 1.69
If you will play an old module madefor CEP 1.50 with CEP from other sources you wont get 1.69 features and fixes. This is mostly the issue of cloaks, there are defintely more but I dont remember. With CEP from this pakage, this wont happen and everything will work just like the module was made under cep1patch169.
As for CPP, the only thing thats here are the 2da merges. This CEP version doesnt include CPP it is just compatible with it which means that if you have CPP you wont lose its features/fixes that are done in 2das which CEP1 contains. Those without CPP simply get these features from CPP along with this version of CEP.
We are speaking of:
- removal of the door portrait
- gender fix to several soundsets
- fix position of the ambient light for "flame placeables"
- possibly the new baseitems from CPP, thats miscsmallstack10 miscmediumstack10 misclargesack10 and cloak_old
- possibly but notsure whether DOA Base Items are also included
thats all
If you want to nitpick into CPP, please get some info first, learn what it is and what it does, open these haks, take a looking glass compare files with cep v1.x and then say "its bad because it contans this change from CPP which is stupid". Before that dont write this generic nonsense without any specifics or proof. And I would be very suprised if you could actually come with specific change thats somehow wrong, gamebreaking, incompatible, imbalanced or I dont know what.
An offering like CPP gets adopted when there is a compelling reason. Being afraid of offending the author is never a sufficient motive.
As far as I can tell, CPP is not generally regarded as a de facto standard.
I've looked at it, but I don't see any must-have features.
It seems to change many details (not just unequivocal bug fixes), which, in the absence of a must-have, strikes me as an avoidable risk.
I'm not against CPP, but I don't think we should be promoting it as a standard offering, any more than say, PRC or Project Q.
So, what I'm arguing for is the presentation of CEP 1.x installer as the latest, vanilla offering, with the CPP-compatible version as an optional add on.
If there are serious bugs in CEP 1.x installer that prevent people playing CEP 1 modules (which is not the same thing as 1.69 compatibility), perhaps we should consider fixing them separately.
Yes its not standard. Due to several ppls CPP gets deleted from every mention of being something more, categories were changed, links got moved. Someone took great pains to made it clear CPP is absolutely unofficial and its not even supported by "the community", whoever this community is.
To me over 7000 downloads means CPP is used and its used by a lot. I dont know whats the regress rate, but since over past 3 years there was only few reports and those were mostly of type "its crashing" which I resolved by explaining that GOG is bugged get 1.69critical rebuild I wouldnt bet its more than few percents.
But amongs the PW admins, module builders and generally the "NWN Experts" there is huge antipathy to this patch. These peoples you including thinks they know everything better and when someone else gives them something they never though of doing then its smell fishy. Or they read the readme find something they think they understand but they do not and say "ha this is a crappy idea/change/modification, this guy who made it is an idiot I know this is wrong" and never actually get into installing this and trying it. And this is "the community", these peoples decide what is and whats not the standard, thus CPP is not a standard and never will be.
I think you would be actually suprised what everything CPP can do for a PW/module builder, but unless you make a leap of faith you never gonna find it. And I dont care, delete this patch from vault, remove all the tracks of it. Remove the tag "Included in CPP" thats definitely aslo bothering you, but this is too much. Throwing out this CEP only because it has 2DAs merged with CPP which doesnt even contain anything more than visual fixes is something I cant understand.
Well, if thats so and this CEP version will be never supported as a standard I will gladly remove it so ppls are not deceived and bother by my CPP sneaky advertisement.
I understand that there has been discussion back and forth about the CPP, but since it's been pretty much established that this doesn't include anything that could be considered controversial from it then I don't think there's any reason to not link it up with the CEP1.X Installer page, or even just keep the 'Related Projects' link if the seperate project pages are kept. That will give this package more publicity since all the links point to the official installer and it helps solve the issue of many different CEP versions by tidying it up a bit. I'm sure Proleric wasn't trying to offend you, simply being cautious and clarifying so that end-users don't get confused over what is being offered.
I think we can all agree on one thing though, keeping the other CEP1 versions like 1.52/1.53 would only confuse people. It's better to center it around the installer and this as an update package/alternate version. That way people have the choice of going with what was last officially released and this one as an all-in-one update/standalone, as mentioned above.
I advise every person complaining about this to get 1.53 module and open a store with grenade weapon. Or worse open a container or loot bag with important quest item AND grenade.
Instant crash.
Shadooow, would it be "fast" to make a copy without any compatibility with CPP whatsoever for all the naysayers?
It would but I wont do that sorry, I wont support CPP haters by giving them CPP free version when what we are talking here about are 5 visual fixes and improvements, I think peoples who needs this will find it those who dont see any value in CPP dont have to bother with this CEP version either.
But this package is a gift for the community, do what you want to do with it, remove any track of CPP, remove any track of my name from it, call it whatevre you like make any change you want, just exclude me from it I dont want to particiate in any way on this anymore.
I wholeheartedly support you.
I am of course using it for some time already. It is certainly better than my ad-hoc fixes, so far it works with every feasible hak order, every module etc. That is the beauty of it - you don't have to mess with toolset, hak orders and rebuild every module each time.
Solid 10 from me.
I personally think whether you had not mentioned 1.7x or CPP here, noone would see it.
Of course every one is welcome to use what they want, but so many people whine that their older modules don't work properly..
Unless every one agrees that this one should be a standard CEP 1.x I can't force it, but I will continue to recommend it for solving bugs. Bugs that are far more serious than the ones solved by CPP from my perspective.
Just thought I would rate this mod - solved a number issues I was having, contains everything and I have not had any problems running it.
Many thanks for the hard work Shadoow - its is appreciated.
Werelynx - your comment about grenades is important new information here.
I assume that isn't fixed in CEP 1.x installer, and that it affects many old modules?
What would sell this version to me as definitive is a module description that says upfront (a) this version is tried-and-tested (b) it fixes fatal errors in CEP 1.x installer (one-liner for each) (c) it works without CPP. That's what I meant by "compelling reasons" in an earlier post.
Shadooow - I'm sorry you take this personally. I doubt whether anything I say will change your mind, but, for the record, my concerns are purely professional. After a lifetime in software integration, I have learned that "if it ain't bust, don't fix it". In other words, never do anything unless it achieves something really important, because the risks usually outweight the benefits, and besides there are more urgent things to do.
If the scope of this work is to fix CEP 1 so that old modules work, the KISS principle tells us that the CPP hooks are undesirable, but if everyone is happy that they are harmless, I'd reluctantly accept the kludge.
What matters most is that we agree on a recommended version for new & returning players. I'm not quite convinced yet, but I'm open to persuasion based on fact, as outlined above.
One of the problems with the older CEP1 modules is that they aren't all on the same version of CEP1 anyway. Some were built with 1.5, others 1.53 and so forth. This makes sure they have all the fixes up to what was last released by CEP Team, as well as what was fixed in the 1.68/1.69 compatibility patch which can be found here. It's a convenience for the user because it ensures that each module will at least be running on the same version of CEP1, so you can better determine what is a module error from what was built with an outdated verison that never got the full benefit of the bugfixing patches.
The CEP1.X Installer does a good job of ensuring that the user has everything necessary to run all CEP1 modules, but this does the job of making a more stable, enjoyable experience playing them; the grenade bug crash and broken glass sound bug being amongst the gamebreakers/annoyances fixed. Besides what Shadooow listed above, the changes made could be found in the official CEP1 changelogs and the 1.69 patch page linked above.
Well, then, I guess we should recommend this version.
Is there a problem with one of the haks called cep1patch.hak? It's size is 908 bytes (modified 8/9/14) vs. the one it's trying to replace in my hak folder at 167,977,461 bytes (modified 7/24/05) .
No problem. The whole point of this project is to migrate everything in the patch haks into the base haks so that the fixes/updates work on modules made with earlier CEP1 versions.
Thanks for this! Supports 1.69 too. Excellent.
Thank you for all the hard work!