I use a completely different mprog scenario now, so I cannot give specifics.
I've done this two different ways. The easiest: Sete of progs: #1 sayto $n Greetings! mob delay 10 2 ~ #2 sayto $n If you wish to to look at our wares, please do so. ~ I changed the delay trigger a bit. When it go to 'mob delay' it recorded the delay time and the prog vnum in the char_data struct and bailed out. Then in comm.c I loop through the mobs every pulse (or something) and subtract one from the delay. When it reaches 0, it called prog 2. ========= The other method was far more complicated. I created a new mob prog struct which help many of the local variables in program flow. Each line was executed until a delay, or a goto, or whatever changed the track of the program. I assigned the struct to the mob. If it was in a delay, then (same as above) once the delay was executed it picked up at the next line in the prog. This took forever to perfect for very little affect :) #1 sayto $n Greetings! mob delay 10 sayto $n If you wish to to look at our wares, please do so. ~ Since I've changed mob programming again, I'm not back at the original method except a little less stressful on the CPU. I created a linked list of all progs executing so I don't need to loop through all the characters to pic up 3 or 4 executing progs. > -----Original Message----- > From: Josh [mailto:[EMAIL PROTECTED] > Sent: Friday, November 22, 2002 2:50 AM > To: Rom > Subject: Re: Delayed Responce in Progs > > > Hmm, well Its still a helluva lot more complicated looking > then a simple > delay #, between them, to me anyways:) > > Not saying your way is bad, just most of my builders beg me > to keep things > as simple as possible for them. > > 8 or 9 extra lines for just that small of a prog can add up > too, although I > do like how they are somewhat like functions, maybe I'd > consider adding > something like that, with a modified version of call too, and > allow someone > to call a progress and such... Its definately something to > think about. > > Josh > > > -- > ROM mailing list > [email protected] > http://www.rom.org/cgi-bin/mailman/listinfo/rom >
