Jump to content

Photo

RE_DreamTimer question


8 replies to this topic

#1 jastey

jastey
  • Gibberlings
  • 7532 posts
  • Gender:Female

Posted 16 May 2013 - 11:13 AM

I have to ask, again:

!RealGlobalTimerNotExpired("RE_DreamTimer","GLOBAL")

Means - what? The timer is expired?

So, if I want to prevent the situation in my mod that Ajantis comes to the PC the same time the RE_DreamTimer is expired, BUT I also have to make sure my script fires in case the RE_DreamTimer is not set at all, this would mean I'd had to include

RealGlobalTimerNotExpired("RE_DreamTimer","GLOBAL")

?

#2 Kulyok

Kulyok
  • Modders
  • 5771 posts
  • Gender:Female
  • Location:Moscow, Russia

Posted 16 May 2013 - 11:38 AM

My head doesn't work well right now, but I'll look over my answer in the morning - there's a nuance we need to keep in mind. In short, don't use the second command, EVER, use the first, if you even want to bother(my advice: don't. Let the Crossmod handle this, it's their eparchy), because it would mean that either the timer hasn't been set at all, or the timer's expired.

#3 jastey

jastey
  • Gibberlings
  • 7532 posts
  • Gender:Female

Posted 16 May 2013 - 12:43 PM

What I would need is "The timer has not expired OR was not set at all". Wouldn't that be the second option?

#4 Mike1072

Mike1072
  • Gibberling Poobah
  • 2535 posts
  • Gender:Male
  • Location:Canada

Posted 16 May 2013 - 01:22 PM

0x40B6 RealGlobalTimerExpired(S:Name*,S:Area*)
NT Returns true only if the timer with the specified name of the specified area has been set at least once and has now expired.

0x40B7 RealGlobalTimerNotExpired(S:Name*,S:Area*)
NT Returns true only if the timer with the specified name of the specified area has been set and has not yet expired.

So !RealGlobalTimerExpired returns true if the timer has been set and hasn't expired or has never been set.
And !RealGlobalTimerNotExpired returns true if the timer has never been set or has been set and has expired.

#5 jastey

jastey
  • Gibberlings
  • 7532 posts
  • Gender:Female

Posted 16 May 2013 - 01:34 PM

Thank you very much!

#6 jastey

jastey
  • Gibberlings
  • 7532 posts
  • Gender:Female

Posted 07 November 2013 - 10:46 AM

I changed all triggers in my dream script block to "!RealGlobalTimerExpired("RE_DreamTimer","GLOBAL")" - and now I have a report that dream scripts don't trigger at all. I am confused.

#7 Kulyok

Kulyok
  • Modders
  • 5771 posts
  • Gender:Female
  • Location:Moscow, Russia

Posted 07 November 2013 - 10:54 AM

It should be !RealGlobalTimerNotExpired("PrefixNightTimer","GLOBAL"), shouldn't it?

#8 jastey

jastey
  • Gibberlings
  • 7532 posts
  • Gender:Female

Posted 07 November 2013 - 11:19 AM

I want the RE timer to be not expired (or not set at all), because I want to use this trigger for the Ajantis rest dialogues (which should not trigger if Valygar or Coran or Aran are lining up..). I should have stated this in the above post, sorry. Fact is, that I have now a bug report about night talks not triggering, and before I used !RealGlobalTimerNotExpired("PrefixNightTimer","GLOBAL") for ages with no complaints. BUT from the logic of what I have in mind it should be "!RealGlobalTimerExpired("RE_DreamTimer","GLOBAL")" in my case - I think. But I think I will just take it out - and live with bug reports about PC having multiple lovers upon rest.

Edited by jastey, 07 November 2013 - 11:20 AM.


#9 jastey

jastey
  • Gibberlings
  • 7532 posts
  • Gender:Female

Posted 07 November 2013 - 12:48 PM

I think I had a fault in my logic, the timer probably doesn't run all the time, meaning there isn't always a triggered event after it run, so maybe it doesn't run most of the time - then the "!RealGlobalTimerExpired("RE_DreamTimer","GLOBAL")" wouldn't trigger, obviously.

I'll just leave it out and stop complicating things.



Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users