Re: 0.7.2: Quest timings
Posted: Thu Jan 03, 2019 11:26 pm
I'm definitely interested in exploring a new resource with the express purpose of better emulation of timers in classic quests. I also appreciate all the time you've spent picking all this apart.
Would you be interested in creating a bulk script to export those timers for all the classic quest files matching your RFC? Then it becomes an issue of updating those lines in the quest scripts and testing execution of each quest again. Oh, and writing the new timer resource itself of course.
Just a couple of minor items. I'd prefer the new resource be called something like "ClassicClock" rather than "Clock2", as this also describes the purpose. And the symbol export should keep the underscores (e.g. _delay_) just to remain consistent with rest of file exported by TEMPLATE.
I also have a quick question about the link values:
What are these actually referencing? Is it just an index into the list of Person resources (if an NPC) or Place resources (if a location). If so, is the index zero-based?
I can't say when I'll loop back to work on the new timer resource itself, but if we have the new timer definitions exported then at least this can progress over time. I'd also be happy for yourself and/or Pango to work on this further and send a PR - if that's an interest either of you have of course. My only request is there's minimum touch to core outside of implementing new timer class and updating Clock definitions in classic quest scripts.
Cheers for all the information!
Would you be interested in creating a bulk script to export those timers for all the classic quest files matching your RFC? Then it becomes an issue of updating those lines in the quest scripts and testing execution of each quest again. Oh, and writing the new timer resource itself of course.
Just a couple of minor items. I'd prefer the new resource be called something like "ClassicClock" rather than "Clock2", as this also describes the purpose. And the symbol export should keep the underscores (e.g. _delay_) just to remain consistent with rest of file exported by TEMPLATE.
I also have a quick question about the link values:
Code: Select all
Clock2 questime TIMER_2REF_2DEST(5?) 0 0 flags 0301(769?) links 2 1
I can't say when I'll loop back to work on the new timer resource itself, but if we have the new timer definitions exported then at least this can progress over time. I'd also be happy for yourself and/or Pango to work on this further and send a PR - if that's an interest either of you have of course. My only request is there's minimum touch to core outside of implementing new timer class and updating Clock definitions in classic quest scripts.
Cheers for all the information!