siashim Posted January 29, 2018 Share Posted January 29, 2018 Hey everyone!I'm having an issue with a script I'm trying to run. I searched for running a script once, and from what I found out, the best way to this is to run the script as quest. So I followed the tutorials(created a quest, added the script to the quest, and so on), but after testing it seems like the script doesn't work. I do get the debug message, but the script doesn't do what is suppose to. Here is my script: Scriptname ModCompanionsQuestReset extends Quest CompanionsStoryQuest property C00 auto Event OnInit() C00.Stop() Utility.Wait(10.0) Debug.Notification("ModCompanionsQuestReset is initialized") EndEvent I would appreciate any help with this. Link to comment Share on other sites More sharing options...
Evangela Posted January 29, 2018 Share Posted January 29, 2018 Change CompanionStoryQuest to simply Quest, and Stop() will work. Link to comment Share on other sites More sharing options...
siashim Posted January 29, 2018 Author Share Posted January 29, 2018 Change CompanionStoryQuest to simply Quest, and Stop() will work.Doing that did not stop the C00 quest. Sqv command shows the state as running. Link to comment Share on other sites More sharing options...
Evangela Posted January 29, 2018 Share Posted January 29, 2018 You also need to make sure the property is filled with the quest. Also c00 has a stage where it is checked as quest being completed. This will register the quest as running even though is no longer in the active quest list. There's no documentation on issues with Stop though, so I don't know what could prevent a quest stopping. It's so easy to prevent a quest from starting though. I guess you can call CompleteAllQuestObjectives() on c00, and then call stop and see if that does anything. Link to comment Share on other sites More sharing options...
siashim Posted January 29, 2018 Author Share Posted January 29, 2018 You also need to make sure the property is filled with the quest. Also c00 has a stage where it is checked as quest being completed. This will register the quest as running even though is no longer in the active quest list. There's no documentation on issues with Stop though, so I don't know what could prevent a quest stopping. It's so easy to prevent a quest from starting though. I guess you can call CompleteAllQuestObjectives() on c00, and then call stop and see if that does anything.I'm not sure how to check to see if the property is filled with quest. Do I just output the value for the property to see if it's not NULL? Link to comment Share on other sites More sharing options...
Evangela Posted January 29, 2018 Share Posted January 29, 2018 https://www.creationkit.com/index.php?title=Bethesda_Tutorial_Papyrus_Introduction_to_Properties_and_Functions Link to comment Share on other sites More sharing options...
agerweb Posted January 29, 2018 Share Posted January 29, 2018 In the CK go into the scripts properties and check that c00 still has the quest you set it to in the first place. Link to comment Share on other sites More sharing options...
siashim Posted January 29, 2018 Author Share Posted January 29, 2018 Thanks guys, as you mentioned the problem was that no quest was assigned to the property. I did need to change the property type to only quest for the the specific quest that I was looking for to show up in the list. Thanks again.Here is the corrected code: Scriptname ModCompanionsQuestReset extends Quest Quest property C00 auto Event OnInit() C00.Stop() Utility.Wait(10.0) Debug.Notification("ModCompanionsQuestReset is initialized") EndEvent Link to comment Share on other sites More sharing options...
Recommended Posts