Zugg Software :: View topic

Beginner Joined: 05 Jul 2006 Posts: 15

Because my triggers are so complex, it is hard to give a definite "compact" box with which I could actually POST these triggers.

But I do have a small enough block of self-contained triggers that I might actually be able to post these. These work on the Duris, land of bloodlust, using the MSP terminal (tog term until it reports MSP terminal).

This is an Export Text version of the entire folder.
I have Bolded the more important triggers.
Note, a lot of leftover values are still present from previous groupings.
The variables are not listed, because they are so many, and it should be fairly obvious what they contain, by the name of the variable used.
Here goes:

Beginner Joined: 05 Jul 2006 Posts: 15

If anybody specifically requests some of my other trigger types, I've got a few categories for you.

Chat - copies all communication lines to another window which isn't scrolling 100's of lines per second. It's also useful to review what somebody has said to you recently, without scrolling your entire mud history.

Mapping - the built in mapper is great, but if I export text this folder, I use 16 kilobytes of triggers to keep the mapper in line. This also colors the rooms by terrain, detects when you try to walk somewhere you can't, maps while FOLLOWING somebody else, rather than moving manually (and as it turns out, this is MUCH more efficient), and several aliases to renumber all the room vnums, in case you somehow ended up with duplicates. In a subfolder, I have a bunch of triggers that control my character when people want me to consent, group, follow, and other simple group commands and instructions.

Names - Use one zmud icon to control all your characters! Keeps track of what class/specialization you are, what your name is, what level you are, and turns on/off specific triggers/aliases/etc to match what your class can currently do. It is actually pretty small, considering how much it has to keep track of.

SmartCommands - Want to use ONE alias to do a whole bunch of things depending on what the current situation? Then you need a SmartCommand!

Spells - This is a HUGE list of all the aliases I use for spells. Lots of subfolders on each class.
It also keeps track of the spells I have memmed, how many seconds I have left to mem my spells, keeps track of "spellwords" and translates them into the actual spell rather than 'waaixzrr'
This also keeps track of the spells I have set into triggers, like the above healthbar system, and my autoBotCleric system.

Storage - Keeps track of your container. loot an unlimited number of corpses! Loot an unlimited number of corpses for a specific item! Loot an unlimited number of <keyword>! Loot an unlimited number of <keyword> for a specific item! The number is quickly definable with a macro key, which scrolls up or down the number. And of course, if you're constantly using different keywords for your container, you can use the same alias for ALL of this, and it already knows what bag to put all your loot in! As a subfolder to this, it also keeps track of your weapons, and an alternate set of weapons you can swap in and out rapidly with a single alias. Also, it has a fairly extensive list of "hot items" that if you notice these just laying around for some stupid reason, you'll grab them, stick them into your <keywordBP> so fast that nobody else will match your speed.

TriggerBot - One of my best and most advanced trigger systems. This one is about a meg worth of triggers, but it's....... awesome. Although most muds consider it illegal, I can turn this on, autoBotCleric for HOURS without ever touching the keyboard. In a good group, with a good leader, this autoBotCleric could literally handle itself indefinitely. Go to sleep, wake up tomorrow at max level. It's that good.

Beginner Joined: 05 Jul 2006 Posts: 15

I recieved a PM which was the following:

Beginner Joined: 05 Jul 2006 Posts: 15

Now, you may be wondering "why does he keep the ENTIRE line, practically unchanged in the variable NumberMobsParseString?
That is because this is going to be a recursive alias. This alias is going to call itself. Now you may be thinking "OMG PANIC", but don't worry, we won't destroy your zmud.

Recursive case:
The string NumberMobsParseString is not empty.
Base case:
the string NumberMobsParseString is empty.

So, now, as it turns out, once we've decided that the contents of NumberMobsParseString are DEFINITELY a list of mobs (this is 100% the job of the trigger, once the alias is called, we have decided "BY GOD IT'S A MOB LIST") we can begin counting them. Which is 100% the job of the alias.
Simple version of what I said:
Trigger determines if it is a mob
alias counts the mobs.

In case you're not familiar with my terminology NPC=mob and vice versa.

OK.

Beginner Joined: 05 Jul 2006 Posts: 15

It took some doing.
My original plan was to parse the FIRST mob in the list of mobs.
IE
parse : "A devilish gnome is sitting here, six cute gnomes are standing here and a big gnome is leaning here."
would process like this:
+1 mob, parse : ", six cute gnomes are standing here and a big gnome is leaning here."
+6 mob, parse : " and a big gnome is leaning here."
+1 mob, parse : "."
which would fail to match, and then it would report 8 mobs.
BUT, because of the way the trigger matching occurs, mainly that the (*) seems to eat up as much as possible, rather than as little as possible, I had to reverse the parsing order:

parse : "A devilish gnome is sitting here, six cute gnomes are standing here and a big gnome is leaning here."
would process like this:
+1 mob, parse : "A devilish gnome is sitting here, six cute gnomes are standing here"
+6 mob, parse : "A devilish gnome is sitting here"
+1 mob, parse : ""
Which returns 8 mobs.

Resulting code as follows: