Zugg Software :: View topic

Posted: Tue Jun 07, 2022 4:37 pm

Well, you probably don't want all of these variants simultaneously, or you will likely end up confusing the client or yourself.
I changed the code when you clarified what you wanted the settings do to. (killing one mob at a time versus all at once)

That means either scrap the old code or incorporate this code into the old code, as they might not work well together.

Assuming you have nothing else...
You want two variables: a list of potential targets, and another list of the positions they can use in the room.

killList=orc|goblin|dummy|etc

position=stands here|looks ready to escape her bonds|etc

This is so we can construct a pattern to properly catch all possible mobs you want to kill in a single trigger.

#TR {({@killList}) {@position}.} {target=%1}

That will define the target for your macros, just need to look after each kill to update your target, if there is anything left.

Adept Joined: 18 Jun 2019 Posts: 279

Without sounding too cynical why create all that mucky code to just 'alias' KILL MOB/NPC?

alias t=kill %1

t dwarf
t dummy
t fred
t ginger

Seems like you are reinventing a wheel/bread/dancing.

Posted: Tue Jun 07, 2022 7:58 pm

Autotargetting systems mean you don't have to type at all, but can go straight to using macros.

Sure, passing a parameter to an alias doesn't take long.
But over the course of weeks, you will spend longer typing that out than it takes to set up the system.

Newbie Joined: 21 Oct 2022 Posts: 1

We really need several different examples, otherwise, we don't know if there is any consistency in how they are displayed or not.

Newbie Joined: 28 Nov 2022 Posts: 1

I also found an auto rescue code on here and was trying to set my target list up like that as well so that no matter what "Approaches", "Surprises" me then it will go into the list and attack the charcter or creature attacking me

https://teatv.ltd/
https://hellodear.in