becauseofreasons Posted March 28, 2013 Share Posted March 28, 2013 I'm still hammering away at that quest, but I'm running into a nightmarish "feature" of the GECK / engine. I'm having major issues with retrieving quest variables upon a reload. I make a save, continue onward without issues, but once I've quit New Vegas and reloaded the save - autosave, standard save, doesn't matter - all of the quest variable information seems to disappear. This is a problem, because I have about thirty-seven quest variables that keep track of what the player's up to at any given point in the narrative. All of that information disappearing destroys my quest. So what's going on? I read that you have to instantiate the variables outside of begin blocks in order to make sure the information gets preserved, which I've done. I read that you're not supposed to manipulate any quest variables inside dialogue result scripts or it breaks things, which seems borderline impossible. That being said, I've been doing this less than two weeks. I really have no idea what I'm doing. So I'm hoping someone out there knows a bit more about variable persistence than I do, and how to control it. Thank you. Link to comment Share on other sites More sharing options...
viennacalling Posted March 28, 2013 Share Posted March 28, 2013 I read that you're not supposed to manipulate any quest variables inside dialogue result scripts or it breaks things Where did you read that? Link to comment Share on other sites More sharing options...
becauseofreasons Posted March 28, 2013 Author Share Posted March 28, 2013 Another modding forum. Again, it seemed a little spurious to me when I read it. Link to comment Share on other sites More sharing options...
luthienanarion Posted March 28, 2013 Share Posted March 28, 2013 I read that you're not supposed to manipulate any quest variables inside dialogue result scripts or it breaks things.I'm going to go with Complete Ass-pull for that statement. Show us the quest script. Link to comment Share on other sites More sharing options...
jazzisparis Posted March 28, 2013 Share Posted March 28, 2013 Make sure StartQuest is not being called by another of your scripts while the quest is already running. Doing so will reset all the quest variables to 0 when a saved game is reloaded. Link to comment Share on other sites More sharing options...
becauseofreasons Posted March 29, 2013 Author Share Posted March 29, 2013 Make sure StartQuest is not being called by another of your scripts while the quest is already running. Doing so will reset all the quest variables to 0 when a saved game is reloaded. You win! That was 100% the problem. Thank you so much, all of you. Link to comment Share on other sites More sharing options...
luthienanarion Posted March 29, 2013 Share Posted March 29, 2013 Make sure StartQuest is not being called by another of your scripts while the quest is already running. Doing so will reset all the quest variables to 0 when a saved game is reloaded. You win! That was 100% the problem. Thank you so much, all of you. Good to hear that the issue was found, and good to know that I can reset a quest's variables by starting it while it's running. Link to comment Share on other sites More sharing options...
Gribbleshnibit8 Posted March 29, 2013 Share Posted March 29, 2013 Good to hear that the issue was found, and good to know that I can reset a quest's variables by starting it while it's running.Good to know, and a good way to completely bork all kinds of things if you don't keep track of your StartQuests. I guess I can sort of see why they did that, but seems to me that should be a flag setting on the function. Link to comment Share on other sites More sharing options...
Recommended Posts