Okay, I have a few hours to fix this so hopefully you guys can throw some solutions at me!

I have a simple setup; one quest completes via dialogue, it completes itself and marks the next quest for start, then stops. The issue is that the next quest won't start. Breaking the quest line. I haven't touched this setup in a long time, so I'm not sure what caused it to break.

The odd thing is that you can start the quest up with the console just fine using setstage. The script simply refuses to start it. I tried having it all in the end fragment of the dialogue, as well as setting the stage of the current quest. Then putting a fragment in that stage to start the next quest. Neither works. The current quest is completed and all goes well there, but the next one is never booted up.

This is NOT an alias issue, or setup issue with the second quest. It starts just fine via console, as well as the testing cell I have set up that plops you down right at it's start. It just refuses to start from this quest.

I'm wondering if scripts are lagging for some reason. So I'll be messing with when I tell the current quest to stop. But in the meantime, I'd appreciate if you guys could throw any suggestions you have at me! I'm releasing my mod tomorrow, so I need to figure out what the heck is going on here.

Thanks,

AJV

To-do list mate:

1. Check the property is still filled and pointing to the correct quest. Even add a new property, new name, and use that in your Start() function instead.
2. Check that the quest isn't set to start via any other method than default. IE not via Event.
3. Use Setstage() in place of Start().
4. Check you've not got another stage ticked as the Startup stage in the quest.

Go... quick, run!

1. Check. Checked it, and even moved the scripting into the stage for the current (ending) quest. No dice.

2. Nope. No event or anything, not SGE either.

3. Check, no dice.

4. No stages marked as startup.

I can start it via console just fine, just the scripting doesn't seem to want to let it fire. I've moved where I stop the quest, so I'm going to try that now.

post your script.

i just wanna see it. probably can't help but im intrigued by this script

If no stages have the Startup Stage box ticked, then I'm surprised they ever started before using Start()

Okay I think I'm close to the issue. The aliases are FORCED, but not allow reserved, (Though forced are by default supposedly, being forced and all). I've run into issues using even the console, so I think the engine finally figured it out and got finicky. I've marked them as allow reserved now and I'm going to test and see if that works.

My script is literally just something like this:

NewQuest.SetStage(5)

NewQuest.SetObjectiveDisplayed(5)
Self.Stop()

Simple stuff. I'm off to test this, I hope it works!

Okay, crisis averted. It was an alias reservation issue. Even though forced ref's are supposed to be inherently allow reserved, I had to mark mine as such manually. Now the quest continues with no worries. IT worked via console before because the current quest would stop after the new one failed to start up, freeing the aliases.

The odd thing is that the engine didn't care for the last year or so as this quest worked fine, but thank god I figured it out. I'm off to prepare other stuff as I think I've tied up all of the last minute loose ends. Thanks for the quick suggestions guys! I really appreciate it.

If you need anything else mate let us know

B1gBadDaddy earned +5 prestige as deputy Falskaar firefighter.