Zugg Software :: View topic

Newbie Joined: 19 Jan 2002 Posts: 6 Location: USA

Ok In a previous topic I talked about making a bot that would walk around in an area and kill things automatically...

For the message go here:

http://www.zuggsoft.com/forum/topic.asp?TOPIC_ID=5315&FORUM_ID=7&CAT_ID=1&Topic_Title=Need+an+experts+help+to+set+up+a+small+script&Forum_Title=zMUD+General+Discussion

Well I started setting some thing up on my own and I am finding myself running into a few walls

ok for starters I have a class folder called "PG Bot"
Within that folder is a folder called "Bot Attack" and a trigger set to my muds output at the end of a battle that performs these functions:

#alias Bot
this is the alias:
#T+ "Bot Attack"
#T- "Kill Triggers"
#ts @ticktime
#case %random {north} {east} {south} {west}
scan

As you can see it turns on my bot attack class and it turns off my other kill triggers for the mud

now within the "Bot Attack" Folder are triggers set to do the following when they see an enemy in the scan:

#T- "Bot Attack"
#TI
%1 <---This is dependent on how far away the creature is
@att beet <----this is the creatures name

With me so far?

so it should scan ,then go to the first creature in scan,kill it and repeat.

I have a button also set up to just ask how long the tick timer should be set for and then it does the alias Bot listed above

Now my problem is that it will scan but when it sees the Mob that is killable the trig is not set off so the tick timer stays on, I keep moving in random directions, and nothing gets attacked or killed.

If your confused my other post explains what I am *TRYING* to do

Can anyone help?

MASTER Joined: 28 Nov 2000 Posts: 4817 Location: USA

quote:
Now my problem is that it will scan but when it sees the Mob that is killable the trig is not set off so the tick timer stays on, I keep moving in random directions, and nothing gets attacked or killed.

If the problem is a trigger that doesn't fire, there are two possibilities:
1) The trigger phrase doesn't match what you are seeing
2) The trigger (or the class it's in) is disabled

LightBulb
All scripts untested unless otherwise noted