Zugg Software :: View topic

Novice Joined: 17 Nov 2008 Posts: 30

Hi, I am using several times the same spell to kill a mob.
I would like to repeat the same spell several times.
Let's have a look :

Wizard Joined: 22 Mar 2007 Posts: 2320

Yes, in principle it should be possible. It will probably not even be hard. The only trick is determining the passing of each 'turn'. Does a prompt mark the beginning of each turn? If not, can you identify some line or lines from the mud that determines a 'turn? Is a turn a specific length of time?

Novice Joined: 17 Nov 2008 Posts: 30

A turn :) well it's only a new prompt yep ("a prompt marks the beginning of each turn")
no timer, no specific length, it just requires some mana though (55M = 55Mana if it runs out of mana, it could stop casting)

so cast spell - wait one prompt - recast spell... - etc
I hope that's clearer Very Happy

Novice Joined: 17 Nov 2008 Posts: 30

Here is an idea, but maybe it's not very well-thought :( Could you help me ?

@tempo = 1
@tempo_ini = 1

TRIGGER : (%d)H (%d)M (%d)V
#if (@tempo == 1) {@tempo = 2} {@tempo = 1}
//alternate between first and second "tempo" (first round - second round - first round - second ...)

#ONINPUT chill
--> launch "listener" class
--> @tempo_ini = @tempo //initialize initial tempo
--> #t+ chill_listener

chill_listener
--> if (@tempo =~ @tempo_ini) {cast 'chill'}

Can someone have a look ? Thanks

Wizard Joined: 22 Mar 2007 Posts: 2320

Something like that could work, but I would rather do it with a multistate trigger. One thing I see about your idea is that you have no convenient way to turn it off when you are done combat. How do you intend to stop casting at the end of the fight? Is there an obvious line that we can trigger from, or do we have to have an alias to control it?

I'll poke at writing a multistate trigger to do this.

Novice Joined: 17 Nov 2008 Posts: 30

Thanks Rahab
You're right i need something to stop casting
so here is the end of the fight

Novice Joined: 16 Apr 2008 Posts: 37

statusmsgs="bleeding awfully|awful|few wounds|few scratches|excellent" (fill this in with all NPC status messages)
spellmsgs="The atmosphere turns chilly as you miss|Calm as ice you summon the destructive powers upon your enemy and speak" (fill this in with all successful/fail spell messages)
fighting=0
casting=0
spell="chill touch" (put the name of whatever spell you want to cast during combat here)

TRIGGER: V (*)> (on prompt, on new line, trigger on trigger)
#if (%pos(%left(%-1,%eval(%len(%-1)-1)),@statusmsgs)>0) {#if (@fighting=0) {fighting=1}} {#if (@fighting=1) {fighting=0}}
#if (@fighting=1 and @casting=0) {casting=1;cast @spell}

TRIGGER: {@spellmsgs} (on new line, trigger on trigger)
#if (@casting=1) {casting=0}

Basically, it tracks combat via the status text in the prompt, and sets the fighting variable to 1 or 0 depending on whether you are fighting or not. If you are fighting, it checks to see if you are casting or not (1 or 0) and if not, it sets the @casting variable to 1 and casts a spell. When that spell finishes (success or fail via 2nd trigger), it sets @casting=0 and as long as you are still fighting (via the prompt trigger), it will cast again. This doesn't "wait" per se until the next round of combat to cast, as I assume your mud will automatically delay the casting of the next buffered spell. If that is not the case, you'd have to do it differently, probably cast via an alarm.

Wizard Joined: 22 Mar 2007 Posts: 2320

It sounds to me as if the mud does not delay the casting of a spell if you cast too soon, so Torin's code won't work. Something like that could work. I'll think about it some more and get back when I can.

Novice Joined: 16 Apr 2008 Posts: 37

If it doesn't, then you simply put the casting of the spell in an alarm, instead of [trying to] casting it immediately.

Wizard Joined: 22 Mar 2007 Posts: 2320

I don't think an alarm is the correct solution, since turns are determined by prompts, not by time.

Novice Joined: 16 Apr 2008 Posts: 37

Well, every mud I've ever played had time based turns and time based ticks, but I suppose any theory it could be different.

You could of course just wait to see some text from the next combat round, although I don't know what universal bit of text could be gathered for any combat. The ability to track that combat is going would remain the same, just the vessel in which you deliver the casting would change. The method of ensuring that you don't cast if you are already casting would remain the same. Since it is done on a prompt trigger, either method could work based on the specifics of how the mud works.

Wizard Joined: 22 Mar 2007 Posts: 2320

There definitely are muds out there which do not use tick-based combat. However, looking again at the text Odeon has provided, you're probably right about this one. It is tick/time based. So an alarm would indeed be the way to go, with another trigger or alias to turn it off. I'm still not sure about making a trigger to turn it off. I'm guessing that the status messages persist after the combat is over, until the wounds are healed. If that is the case, status messages won't tell us when combat ends. Odeon, can you tell is if that is true? Also, do you ever have to fight more than one opponent at a time? If you do, we also can't trigger off a death message, and we might be stuck using a separate alias to turn it off.

Novice Joined: 16 Apr 2008 Posts: 37

I was under the impression that those status messages were the mob status, as they became worse and worse as combat ended and were very high at teh beginning of combat, and were not present at all when combat was over or before it had started.

Wizard Joined: 22 Mar 2007 Posts: 2320

Odeon hasn't shown us any prompts after the combat is over. Odeon, can you tell us what that status message is? Is it describing your own condition, or your opponent's?

Wizard Joined: 22 Mar 2007 Posts: 2320

If the status message is in fact the status of the opponent, here is some code that should work. I have tested it as far as I can. This is in XML form. You will have to add to @statusmsgs any other phrases that might appear as the opponent's status. It uses a simple multistate trigger instead of the variables Torin used to keep track of it's state:

Novice Joined: 17 Nov 2008 Posts: 30

Thanks guys, i'll test it :)

-- Info : complete fight below -

Novice Joined: 17 Nov 2008 Posts: 30

Yeah, really great working ideas, i'll modify a bit to apply it to several spells (and mobs :)
but that's a wonderful foundation! Thanks Torin & Rahab :) Very Happy