Hello. I’m having an issue with EE’s toolset. I have a module of my own and all of a sudden I get “Could not load the module file. Module might be corrupt.” as an error message. I can load the module fine in the toolset but when it comes to playing or hosting it, no luck. Weird thing is that I tried saving an entirely different mod with a different hak set and then that module became corrupt as well. Any ideas?
Of course the first thing what springs in mind is to check your EE if override is clean and if it’s free of third party add ons.
The fact that it happens to more than one module points to a more global infestation.
Indeed.
If the modules still load in the toolset, make a back up copy of your .mod and .BackupMod files. You can use these to recover the module if further toolset activity causes damage.
Next thing to check is that you’ve added no files whatsoever to the game installation. A common problem, for example, is to put haks in the .hk folder.
Ensure that your .mod and .hak files are in the correct subfolders in Documents (see guide) and that nwn.ini (in Documents) specifies the correct paths to those files.
I’ve seen this error before, when files were in the wrong place, but unfortunately it is also possible that the modules are indeed corrupt.
In that case, copying the component files from the old module to a new one often helps. Load the old module in the toolset, then copy the component file from the \module\temp0 folder. Make a new module. Copy all the components into temp0. Make any trivial change to the new module, then save.
If the old module won’t open in the toolset, try nwhak or nwnexplorer.
1 Like
In that case, copying the component files from the old module to a new one often helps. Load the old module in the toolset, then copy the component file from the \module\temp0 folder. Make a new module. Copy all the components into temp0. Make any trivial change to the new module, then save.
Yes, this works. I’ve experienced this more time than I care to count. But in every case it was a corrupt module.ifo file. Something very small and easy to overlook. Do not copy that over when you copy all the components from your Temp0 file. Let your new module make one on its own from scratch.
4 Likes
This can sometimes be caused by using F9 to test the module from the toolset and not having saved the module before pressing it. Even though it prompts you to save, I’ve had experience where it corrupts the module if you save from that dialog box. Instead, hit exit and save the module yourself. Then instead of using F9 start the game normally - via a shortcut to nwmain.exe. It’s safer than using F9.
2 Likes
Thanks for the help everyone. It ended up being the module.ifo so it’s all running smoothly again.
1 Like
I had an instance of this message which was NOT resolved by reloading the module, so while corrupt module.ifo is the first thing to suspect, it’s evidently not the whole story.
In this case, the problem was missing resources, owing to a hak having been removed by mistake (toolset resource check was off). I just had to reinstated the hak in the toolset.
2 Likes