In my LTGJ I added a quest with 3 aliases filling with Unique Actor (see which below) and one for a book with Create Reference that is using text replacement. There are also the globals for text replacement and a simple dialogue supposed to give the book to the player. The quest itself is Start Game Enabled and Run Once. For me everything went well. But I had two users reporting they are not seeing the dialogue, one of them followed up and gave me this:
- 4 Aliases for quest 'LH_LGJ_TGRRewards'(44009A09)-REF 'Vex'-> NONEREF 'Delvin'-> NONEREF 'Karlia'-> NONEREF 'PlayerLog'-> NONE--- Quest state ------------------Enabled? YesState: RunningCurrent stage: 0Priority: 0
As we can see the quest is running but aliases, which are Unique Actors as I sayed, not filled. Then the user reported that after (ingame) days of playing or waiting all became good and working...so don't think the NPCs themselves were messed or dead or something.
BTW, the user just started using the mod, didn't update from previous version. Also, starting using the mod on an older save didn't had the issue.
How is this possible? What could delay the filling of the aliases so much?
I suspected the thing I'm talking about http://www.gamesas.com/topic/1447502-sendstoryeventandwait-not-returning-either-true-or-false-what-can-it-mean/to have something to do and when the user gave me the http://pastebin.com/ppxWctG1 I saw this:
...[02/21/2014 - 12:17:25PM] ----Node '' failed conditions[02/21/2014 - 12:17:25PM] ----Node '' passed[02/21/2014 - 12:17:25PM] -----Quest 'DialogueRiftenRaggedFlagonScene08' failed to fill aliases[02/21/2014 - 12:17:25PM] -----Quest 'DialogueRiftenRaggedFlagonScene07' timed out filling aliases[02/21/2014 - 12:17:25PM] Timed out processing event[02/21/2014 - 12:17:25PM] -----Quest 'DialogueRiftenRaggedFlagonScene07' failed to fill aliases[02/21/2014 - 12:17:25PM] ----Node '' passed[02/21/2014 - 12:17:25PM] -----Quest 'TGDialogueHQScene08' failed to fill aliases...
A single timeout is not enough to clearly say it is related, but note that after that line is not starting to process a new event (actually retrying the same) as usually happen in the logs I have in the other topic.
So, any ideas?
Thanks