Aller au contenu

Photo

Blank Journal Entries


  • Veuillez vous connecter pour répondre
4 réponses à ce sujet

#1
Mr Ordinary

Mr Ordinary
  • Members
  • 57 messages
Hi all.

I have searched for a similar topic, but with no luck. I hve recently re-installed NWN2 OC + MotB + SoZ (On WinXP) and patched to 1.23. I have also installed TonyK's AI,  Kaedrin's PrC Pack (1.40.4) and The Complete Craftsman.

I have used this combo before,with no issues, yet now I find no text in any of my journal entries and quests do not complete. I would ask if anyone else is using this particular combination of mods/haks and has either suffered the same issue but been able to resolve it, or has a working installation?

I do not want to have to remove the mods, as they add to the gameplay, and would appreciate any suggestion as to how this journal issue may be resolved. Thanks.

#2
justAcigar

justAcigar
  • Members
  • 3 messages
I'm having the same issue, and I don't have any of those mods, Just the same version of NWN2 and all the xpansions.

I'm playing the Misery Stone mod from Bouncy Castle, and all my journal entries are now blank, and all new ones are being created blank..

#3
lolguidos

lolguidos
  • Members
  • 7 messages
You could try putting one in at a time and seeing which mod is the culprit. Then attempting to debug it.

#4
_Knightmare_

_Knightmare_
  • Members
  • 643 messages
I have no solution to offer, but a common cause of this is when the journal entries are written at the campaign level but are being called from the module level. No idea what may have changed for you to make that situation appear. The usual culprit is added custom content. I suggest following lolguidos' comment.

#5
Mr Ordinary

Mr Ordinary
  • Members
  • 57 messages
Hey all, thanks for the suggestions.

I looked through the mods I installed, as I had packed them all into one install file for easier installation and I found I had also included some fixes for issues with SoZ - notably one called SoZFIXES (can't recall the author). This set of scripts included a file called module.JRL which was the culprit causing the issue. I removed this file and all was okay (and it doesn't affect the other fixes.)