Zugg Software :: View topic

Beginner Joined: 15 Aug 2007 Posts: 10

Ok this is what I am trying to make but I honestly don't know how to do it.

I want to make a trigger that summons a mob every tick and kills it.

But this is the issue. I want it to switch targets once it can't find a certain mob.

For example:

Trigger Pattern: -- TICK!
Trigger Value: c 'summon' bozak

but I want it to be able to switch targets if the mud sends the response.

You failed.

this is how I wish it would work.

-- TICK!
c 'summon' bozak
You failed.
c 'summon' mall
A mall rat arrives suddenly.
kill mall

that way it auto changes mobs if the summon fails.

Thanks.

I hope you all can help me. Someone told me to use a List and another said make an array.
The only problem with those solutions is I have never made either one. I have no clue how to.

Please help if you can.

Anything is better than the crap I made.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

This is totally untested and written off the top of my head. Just copy and paste into the commandline and you should be able to start going. Add all your targets with the AddSTarget alias. As soon as you put your first target in it will activate the bot. You can then turn the bot on and off with just the SumBot alias. Finally it includes a 30 second rest state when it runs out of things to kill. Also included is a state to keep from summoning many things and only killing 1. You may have to correct the text for that since you didn't supply it initially.

Beginner Joined: 15 Aug 2007 Posts: 10

Access violation at address 004BDAB4 in module 'Zmud.exe'. Read of address 756E254D.

Beginner Joined: 15 Aug 2007 Posts: 10

But this is exactly what I do want to make. And for some reason when I do get it in the DoSummon just shows up like this.

Alias Name: DoSummon
Alias Value: {#IF

Nothing else. Exactly like that.

BTW, I play Temporal Rifts if you would like to test it. Thanks alot I really do appreciate this.

Crisis

SubAdmin Joined: 18 Nov 2001 Posts: 5182

It was just missing a closing brace. You should probably check that everything else pasted in alright as well.

Posted: Thu Aug 23, 2007 4:47 pm

As always, make sure this trigger isn't breaking any MUD rules. Many MUDs do not allow the use of a bot in which you can be away from your keyboard for any length of time and your character will continue to run in an automated sequence. Please note that you are responsible for your character and any consequences rendered to your character for any illegal activities. ;)

Charneus

Beginner Joined: 15 Aug 2007 Posts: 10

I have it in now. But for some reason the Tick trigger and the Cond trigger keep deleting. On their own. And everything is being thrown in one folder. I hope I didn't do it wrong.

Thanks,

Crisis

Beginner Joined: 15 Aug 2007 Posts: 10

These three I am having issues with:

#TRIGGER "SummonTime" {^--TICK!$} {#IF (@InCombat=0) {DoSummon}} "" {disable}
#COND {^(?:(?:A|An|The) .*? arrives suddenly.|You failed.)} {#IF (%line="You failed.") {#ADD FailCount 1;SummonTarget=%item(@SummonTargets,%eval(%ismember(@SummonTarget,@SummonTargets)+1));#STATE SummonTime 1;DoSummon} {InCombat=1;kill @SummonTarget}} {regex}
#COND {^You have killed} {InCombat=0}

And if I stick them in manually, they disappear after 1 kill and make a new trigger named: You have killed.

I am not sure where the problem could be and also the @InCombat=0 changes after 1 kill to @InCombat=1 and I have to go back in manually and replace all the above and reset InCombat to 0

Hope this helps some.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

This is likely caused by the original error of a missing closing brace. Also I did mention that you have to adjust the "^You have killed" pattern to correctly match something indicating the completeion of fight. I will put the whole together with a #DELCLASS so it cleans up anything you have right now. You will have to add your targets in again. Please take the time to actually try to understand how the script works.

Beginner Joined: 15 Aug 2007 Posts: 10

But I am still having one problem.

#COND {^(?:(?:A|An|The) .*? arrives suddenly.|You failed.)} {#IF (%line="You failed.") {#ADD FailCount 1;SummonTarget=%item(@SummonTargets,%eval(%ismember(@SummonTarget,@SummonTargets)+1));#STATE SummonTime 1;DoSummon} {InCombat=1;kill @SummonTarget}} {regex}
#COND {is DEAD!!$} {InCombat=0}

Those two lines don't get put in the system.

I am using Zmud 7.21

Not sure if it can't accept those values. For some reason when I copy and paste the whole Text and then open the class folder and hit all to see everything, they are no where to be found. I also have show hidden on and details and no where. Is it suppose to be that way? I also added the mud specific text in to the 2nd Condition.

Thanks,

Crisis.

Posted: Fri Aug 24, 2007 9:24 am

Those lines have to be put in at the same time as the trigger statement before them.

See #CONDITION for more help.

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

They also don't show as normal triggers in the editor. They are STATES of the trigger before them as Tech mentioned.
With that in mind you need to click on the trigger before them and click the states tab to be able to see them.

I just copied the above script and pasted it into the command line and they showed up exactly where I said for you to look, under the states tab of the ^--TICK!$ trigger.