Message

Hey=20 Alex,

Thanks for = the=20 response. However, I have tried what you described, but there=92s a = problem.=20 See, as soon as the =93fork=94 is encountered, all variables within it = are what=20 they are when the fork is called, not what they will be once it is = executed.=20 So changing the value of =93waiting_for_money=94 after it=92s been = done won=92t affect=20 the fork at all.

The = alternative that=20 I=92ve tried is to give the fork a task name, and then kill that task = once=20 something is read in:

fork = complain=20 (15)

= =20 statements;

endfork

read =3D=20 read(player);

kill_task(complain);

This works = fine, as=20 long as the user answers before the fork is executed. However, if the = user=20 answers after the fork is executed, then it gives an =93invalid = argument=94 error,=20 since that task is no longer running.

I tried = making it=20 conditional, like this:

complain = =3D=20 0;

fork = complain=20 (15)

= =20 complain =3D 0;

= =20 statements;

endfork

read =3D=20 read(player);

if=20 (complain)

kill_task(complain);

endif

However, = whatever=20 happens within the fork doesn=92t seem to affect the outside, so this = doesn=92t=20 work either.

Is there a = built-in=20 command that would quickly check if =93complain=94 is a valid task? = Something=20 like:

is_running(complain)=20 ?

Or any = alternatives=20 to what I have been trying?

Thanks!

Jean-Marc=20 Giffin

From:=20 encore-bounce@utdallas.edu [mailto:encore-bounce@utdallas.edu] = On Behalf Of Alexandre = Borgia
Sent: Thursday, July 06, 2006 = 11:47=20 AM
To:=20 encore@utdallas.edu
Subject:=20 [encore] Re: Wait For an Action?

Hi=20 Jean-Marc,

You=20 could keep state information in a property on the driver. For = instance,=20 after you talk with the driver set something like = =93waiting_for_money=94 to 1 and=20 fork a process that will check this property again 10 seconds = later. In=20 the meanwhile, if the player decides to give him two pounds set the = property=20 back to 0 and continue with your next actions. When your forked = process=20 responds back, make it first check if =93waiting_for_money=94 is still = set to 1=20 and if so make the driver react as if he had not received the money in = time,=20 else exit the process without doing anything since the driver got the = money=20 and everything is all right.

Hope this=20 helps!

- =20 Alex

-----Original=20 Message-----
From:=20 encore-bounce@utdallas.edu [mailto:encore-bounce@utdallas.edu] = On Behalf Of Jean-Marc = Giffin
Sent: Thursday, July 06, 2006 = 10:06=20 AM
To:=20 encore@utdallas.edu
Subject:=20 [encore] Wait For an Action?

Hey=20 all!

Because=20 of the nature of how I am making the MOO, I have bots that expect you = to give=20 them items.

For=20 example, to take a carriage, you have to talk to the driver and then = he asks=20 for 2 pounds. I want to make it so that he waits a bit of time for you = to=20 =93give driver 2 pounds=94, but if you take too long, he=92ll get = annoyed with you=20 and move on. I was thinking that it would be possible to do a = =93read(player)=94,=20 but then (as far as I know) it would take away from allowing the = normal =93give=94=20 command to take place, since it wouldn=92t parse the string. I then = thought of=20 making a =93fork=94 or =93suspend=94, but if the suspend was 10 = seconds (for example),=20 and I gave the coins after 2 seconds, I would have to wait 8 seconds = for the=20 driver to respond. Is there a good way to make the bot wait a certain = amount=20 of time for an event, and as soon as it takes place, things=20 continue?

Thanks!

Jean-Marc=20 Giffin

--
No virus found in this outgoing = message.
Checked by=20 AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.9.8/380 - = Release=20 Date: 30/06/2006

--
No virus found in this incoming = message.
Checked by=20 AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.9.9/382 - = Release=20 Date: 04/07/2006

Moo Database Browser

Tools for querying and exporting inactive Moo databases.

These applications allow one to easily extract information from a Moo = database which is not executing. For sporatic look-ups, they are more = efficient=20 than booting up a live Moo and faster than loading the emergency wizard = mode.=20 This is particularly useful when one has an archive of historical = databases, or=20 if one is just looking for a verb that recently got=20 deleted.