cumbrianlad Posted July 12, 2020 Share Posted July 12, 2020 Hi. This is just FYI. I've sorted it now, but boy it had me stumped! I went to test a quest that should fire after another quest ended. It appeared to fire but by jumping straight into stage 40! The reason I thought it was firing was that I got on-screen notifications that are displayed when the player picks up 2 quest items in stage 40. I checked my inventory and didn't have the items. What? The aliases were created in an NPC alias and a chest alias. My script used the 'OnContainerChanged' event. I hadn't checked if the new container was the player, because I hadn't seen the point, so added an 'If' statement to the script. It seems that in creating the reference alias this way, that counted as changing the container. Surprise number 1. The new container check sorted that out. I never thought that a script would fire just when an alias was being filled. I still couldn't see how this stage was running before all the others. Testing again showed that the quest wasn't actually starting. Now I'm even more confused! it turned out that I'd assigned the same NPC to 2 different aliases by mistake, lower down the list. They weren't flagged 'Allow re-use in quest' because they shouldn't have needed to be. I corrected that and Bingo! Quest starts. No more messages from the quest object aliases, either. All I can think is that when the Story Manager ran down the list of aliases those 2 scripts fired, then the SM hit the alias it couldn't fill, so it aborted starting the quest. Does that seem right? Link to comment Share on other sites More sharing options...
Recommended Posts