I'm looking to trigger a quest stage after 24 hours of game time. I'd imagine a function as so:

Int Function GetPassedGameDays() GlobalFloat GameTimeFloat GameDaysPassedGameTime = GetCurrentGameTime()GameDaysPassed = Floor(GameTime)return GameDaysPassed as IntEndFunction

So if the function returns 1 or greater the quest stages advances. The part I'm unsure of, that I've never done before is call a function and do this kind of action based on the return value. Any tips or pointers? Much appreciated.

I'll post the script for you, give me 10 mins while I make a cuppa

Here is an example script.

Scriptname script1 extends ObjectReference  Quest Property Quest  Auto  Event (put your event here, so OnActivate for example)	  RegisterForSingleUpdateGameTime(24) ;in game hoursEndEventEvent OnUpdateGameTime()   Quest.SetStage(10)EndEvent

Obviously you need to make a quest property pointing to your quest, and call it whatever (usually whatever the quest ID is is good for organising)

Beautiful! Thank you MUCH!

No probs

One slight twist to this...what if I have over 80 quest stages to trigger? Doesn't make sense to have one script per stage.

You want them all triggering one after the other? At say 24 hour intervals exactly?

Yes, Viconia interacts with the player the same way she did in Baldur's Gate II. Every 24 hours she will advance to the next quest stage, approach the player and start a conversation. They talk. End of stage, rinse and repeat.

This was ridiculously easy in Oblivion. Not so much here. Just her approaching the player is a PitA.

If the stage is complete when the dialogue is over, you could add the script to the end papyrus fragment in the response window.

That may work anyway. You'll have to test it

Okay thanks, I'll give it a shot this week

Crea

Doesn't make sense to have one script per stage.

Make another Int property (I just called mine stage) and use it like this:

Int Property Stage Auto (I think this is what it was, lol. I'm at the office and can't look right now)

Quest.SetStage(stage)

That way, you can use the script over and over, and just change the values in the property.

(At least, I think that's what you're asking for?)

It's actually very easy with Skyrim, too. Something like:

Scriptname script1 extends SomethingQuest Property Quest AutoInt StageNum = 0Function SomeFunctionYouCallWhenSheStartsFollowing()	RegisterForSingleUpdateGameTime(24)EndFunctionEvent OnUpdateGameTime()	if StageNum < 800		StageNum += 10		Quest.SetStage(StageNum)		RegisterForSingleUpdateGameTime(24)	endifEndEvent

That assumes evenly-spaced stages. If your stage numbers are more arbitrary, you could put them in an array, and then cycle through them based on a counter variable that you add 1 to every 24 hours.

A potentially easier way to do it would be:

Function RunMyQuest()  MyQuest.SetStage(10)  Utility.WaitGameTime(24) ; Pauses the script for 24 in-game hours, then will let the next line run  MyQuest.SetStage(20)  Utility.WaitGameTime(24)  MyQuest.SetStage(30)  ; And so onEndFunction

That is awesome! That will simplify my construction timers considerably! I assume you can make each Uility.WaitGameTime(XX) whatever number of hours you need it like 48, or 72 or whatever. Thanks for posting!

It's things like this that have made me decide to do a course in programming. Simply fixing PC's 'aint enough for me anymore... Thanks for posting that, some cool ideas will come of this

Wow, thanks everyone. What's funny is I program in C# and I'm freaking lost in Papyrus but I'm getting there.

Ya, that thar skript is plum sixY!

It'll definitely cut down on the amount of Registerforsingleupdates I was looking at using

So for OP. if your quest dialogue is all in the one quest, and you want the stage to set 24 hours after a line of dialogue, put this in your end fragment papyrus box:

Utility.WaitGameTime(24)GetOwningQuest().SetStage(xx)

That's how I would do it. It'd be more organised for me that way

Yeah, that's why they're pro's and I'm a wanna-be hack, stumbling through this stuff and building it with duct tape and chicken wire, lol!

but won't this thread the entire function into the save game? correct me if i'm wrong, (sorry if i'm not understanding this correctly) but from what i understand of papyrus, this would work fine up until the user uninstalls the mod. if the function is threaded and baked into the game save, it will run the remainder of the function for rest of the time remaining (and error if the mod is no longer exists), in which in this case, would be a single function that lasts for 1920 hours. at least with the registersingle loop, you can terminate the threaded functions when the update event fails the first time, so it doesnt have to keep running the remainder of the 80 day intervals.

Good point. But it can be fixed by an if check after each stage set.

If I remember correctly don't I have to declare a couple of script properties to include Utility and GetOwningQuest?

Also is there still the line limit on scripts the way there was in Oblivion? I thought it was 255.

No.
I'm now working on a script with 683 lines and I think It had have more lines at some point. There is though a line limit. Someone reached it various months ago, but I'm not sure what that limit was or if even it was mentioned in the thread.

Could be a limit only applied to the CK though. I use notepad++ .

Yes, there's a limit to what the CK's built-in editor can handle--I don't remember what it is, but I ran into it--but larger scripts beyond that limit compile fine with an external editor; my largest is 2,000+ lines.