If I find more like this, I’ll reply to this thread:
https://neverwintervault.org/project/nwn1/module/companions-hall-night-thousand-zombies
edit - I just realized that the missing files are Gavin’s Tilesets. Maybe a link to the correct project page can be fixed:
https://neverwintervault.org/project/nwn1/hakpak/tileset/dwarven-chasms-catacombs-barren-lands-deep-dungeon-undercity-tilesets
If you look halfway down the comments you’ll see
so I’m not sure we should touch it.
Evidently, Turkeys (who couldn’t have reasonably known the above) added direct links to the files, the second of which seems to work after a long delay. These days, we recommend linking to the project page instead.
However, in deference to the tileset author and the module author, it might be more appropriate to delete both of those direct links, and the link you added in the final comment.
Having looked at the project page for this module and then at sixthrice’s project pages it is clear that @Kenneth J. La Mella misinterpreted this from the Wild Woods [v0.7] & Wild Lands Tilesets project page -
I would respectfully ask that the content found here is not repackaged or rereleased, or included in any other non-module or PW-specific package in an altered or unaltered state, without requesting my express permission
As links to the project pages does not fall under that, I see no problem with putting corrected links on the module in question’s project page. If nothing else it will mean that NIT will then be able to deal with this module and those that prefer to manually download and play the module will not have to pull their hair out and bang their heads against numerous walls.
TR
The issue isn’t the archive. It’s the required projects links that are broken:
If you click on the link to go to the page for either the Deep Dungeon Tileset or the Undercity Sewers Tileset, you’ll get “ERROR: no file specified for download.”
This lead me to initially think that these files were deleted from the vault for whatever reason until I realized what tilesets they were… thus I came back and ended my post. Those dead links need to be pointing to this page:
edit - I realized that when I went back and edited my post that I forgot to edit the title, it should state that the required projects links are wrong as that’s the issue.
Yes, that’s what I’m referring to in my post.
I’ve explained why there were no links originally, why they were added, and why they don’t work.
Thanks for the clarification. By all means go ahead and fix the links.
I would interpret this as they do not want it included in a compilation or other “repackaging”, so just linking to that page would in my view be fine.
Fixed.
TR
Found another:
https://neverwintervault.org/project/nwn1/module/court-night
This one requires Project Q, but it links to a page that produces a 404 Error:
https://neverwintervault.org/project/nwn1/hakpak/combined/project-q
Since I don’t know if it needs the newest version or one of the archived versions, I’d just change the link to the main project page (as that also links to the archived versions):
https://neverwintervault.org/project/nwnee/hakpak/combined/project-q-iv
Having had a look at this I see that this module is from 2010 and last updated in 2011. This being the case I looked on the archived previous versions of PQ. There are a lot of different versions there (going from V1.0 to V3.1) without dates. Anybody got an idea of which version to recommend?
TR
I have no idea as to what version is correct.
This module has the same issue in that it requires Project Q but the required project goes to the Error 404 page:
https://neverwintervault.org/project/nwn1/module/dragons-autumn-dark
It most likely needs one of the archive versions also:
https://neverwintervault.org/project/nwn1/hakpak/combined/project-q-archive
As for what version to recommend, no clue. My prior computers really didn’t have the hard drive space for CEP 1, CEP 2, Project Q, PRC, d20 Modern, and whatever else… so I pretty much avoided everything that would require any big custom content project or tons of haks in general.
Once I’m done browsing through the vault for interesting modules that I passed over, I’ll take a serious look at the Project Q archives to determine what the deal is with all the versions.
Most likely they will be migrate wizard/bot uploads. The thing to do in such a case is to look in the description for the original upload/last update and then compare the newest dates in the old PQ archives for the newest one before the module dates.
You may come across a similar problem with D20 modern but CEP should be OK as they are all on the one project page now.
Thanks.
TR
Here’s another that needs old Project Q
https://neverwintervault.org/project/nwn1/module/fa1-halls-high-king
Link to point here:
https://neverwintervault.org/project/nwn1/hakpak/combined/project-q-archive
I’ll let you know if that happens. I’ve only encountered one module so far that uses d20 Modern, and the link to it was fine.
Glad that @udasu actually put the version number of Q required. That was a much easier fix. TBH, if you find another module by them that has a broken link it might be better to let them know as they are still around.
TR
kk - I’ll post here if it is owned by the migration wizard or if there has been no recent vault activity from the owner.
Oh and I took a look at the Project Q archives, unlike CEP, there are no version specific patch files. The files for version 3 all have the same names as version 1 and version 2. If it turns out to really have downward compatibility with prior versions, it’s going to be very surprising that CEP has always been much more favored over it when Project Q would be a lot easier to use… but that’s just me liking things tidy.
The current version of CEP 2.x is fully backward-compatible, and should be used for all CEP 2.x and CEP 1 modules.
The historical 2.x archives are there “just in case” but should never be necessary.
We encourage builders to link to the current project page, whose url never changes.
Within the current release are top haks (only) for past versions. This allows builders to remain on old versions of the 2da files until they’re ready to upgrade (which may involve 2da merging).
Which makes CEP a lot easier than it used to be when it felt like there was 234923432 different versions, none of which were compatible with each other. I only meant that I don’t know if Project Q is like how CEP used to be or if it has build in backwards compatibility. 
