Hey quorn,
I'm a new member in the forums although I've been playing Morrowind for many years (since it first came out). Congrats on your work and to all the others involved; I have used the UMP in the past with success.
However, I seem to be having some trouble with the more recent release of MPP 1.6.4 and my problem does not appear to have been fixed with MPP 1.6.5b.
I started a new game for my wife who is a newcomer to the game and only installed some of the official plugins; and after a few game days I decided I should also add the MPP 1.6.4 for her.
(Btw, I did run the startscript patchscript and then I did look at sv and found no Bluescript or whatever it was I was supposed to be looking for; however when I first loead the game with the MPP mod added, I got an error, something about a 'yellowbook script' not found... I wonder if that is anything serious; anyway I wrye Mashed the savegame later on and it all seemed fine, as it was blue).
Now, she had already gone to the Balmora temple to pick up a quest that gave her a copy of the Pilgrim's Path book. She had not actually tried to read it yet, but did save the game before I made the changes (i.e. added the MPP mod later). Now it appears that after I installed the MPP bugfix she runs into a problem whenever she tries to read the book: clicking on the book returns a good old CTD when the book is placed onto the character's icon in the inventory menu
. I tested to make sure that the culprit was indeed MPP 1.6.4. First, I fired up an earlier savegame and the book can be read fine (when placed on the toon's icon in the inventory menu). I also loaded the first MPP-added savegame and noticed that it is the first time the CTD occurs when one tries to read the book. I reloaded the same savegame after unticking first the MPP (1.6.4) and of course got a lot of errors, I clicked 'Yes To All' and loaded it...I now attempted to have her character read the book...this time, she could read it without a problem.
In my desperation, as I am aware of how many bugs Morrowind has, I decided to see if MPP beta 1.6.5b made any difference; I installed it but the problem persisted (I even stopped the script and restarted it to ensure MPP 1.6.5b loads OK). So, I returned to 1.6.4 and simply fired up the savegame, dropped the offending book on the floor and went to the console and typed
player-> AddItem "bk_PilgrimsPath" 1
giving her character a new book. I tried to read it and it worked fine. Great...but...after I saved the game and reloaded and tried to read the new book, well it did'nt give me a CTD but it just did nothing i.e. it would not read it (i.e. clicking the book on the character's portrait in the inventory menu did absolutely nothing, no matter how many times I clicked on it, no matter what else I tried or to what cell I went to). I retried this, just to make sure and the problem persists.
Since this problem first appeared AFTER installing the patch it appears this is a bug the patch created (?).
I also have a side question that turned up because of this. How do I uninstall the patch? And how does one upgrade to the new beta version (from 1.6.4 to 1.6.5b)? I ask these questions because the readmes simply do not say anything. My understanding is that the textures and meshes that had been added during the initial installation of 1.6.4 remain exactly the same in 1.6.5b, so installing 1.6.5b simply overwrites the same textures and meshes and only adds the new .esm in Data files which (if you want to use the new version) you must run in place of the old 1.6.4 esm. So, in such a case I simply untick the 1.6.4 esm and tick the new 1.6.5b esm ... but the question is: do I need to re-run the startscript command in the console and then check sv at the global variables etc? And do I have to stop the script first (stopscript patchscript) before Ire-run it (startscript patchscript) or do I do nothing at all the second time around? Because any savegame I tried under the updated 1.6.5b in this fashion was turned red in Wrye Mash, and not blue or green I expect something I did was wrong... even after re-saving etc. the red stayed.
Anyway, if any help to my problem (bug?) or to my question is available I would be most grateful
Thanks again to quorn and to whoever else may read this!
Cheers
Opus Pi