Shattered Kingdoms

I ran into a few issues with this trigger, since the prompt format was conflicting with generic wild card matches for cabal and tribunal names. The trigger below should work until I can think of a more elegant workaround. If you find any bugs, let me know. Copy/paste on the command line in zMUD:

#TRIGGER {{~[HAMMER~]|~[DRUID~]|~[FIST~]|~[MIDNIGHT~]|~[HARLEQUIN~]|~[CRUCIBLE~]|~[PEACEKEEPER~]|~[HAND~]|~[GUARDIAN~]|~[TALON~]} %*: %*} {#CAPTURE "Chat"} "Chat Catcher"

finney I see you posting and I hope you have a character.

Replaced the Combat.txt file with CombatEvents.txt. The new file has a scan alias, kill alias, an output message for faerie fire and I fixed a highlight/syntax error with pronouns - {his|her|its} - on failed bashes.

http://nothingxs.net/inbound/uploads/Combat%20Events.txt

EDIT - I also uploaded a new master file that includes the changes to the CombatEvents.txt file and edited the URLs on the first page.

http://nothingxs.net/inbound/uploads/SK.txt

FYI - the old files are still available, if you want the previous versions for whatever reason.


EDIT2 - Scan alias and kill alias below for those that messaged me on YIM.

#ALIAS scan {
look north
look northeast
look east
look southeast
look south
look southwest
look west
look northwest
}
#ALIAS k {kill}

EDIT3 - Yes, it is possible to have scan only check available/visible exits, but it will take a bit of work. I'll add that to my to-do list for the next version of Combat Events.

Removed scan and kill from the combat class to make it easy for people to delete/change those - especially if you prefer to use "h" to initiate combat instead of "k". Updated the URL on the original post.

Still working on scan to only check for available/visible exits.

http://nothingxs.net/inbound/uploads/SK_Master2.txt

Recently updated my CMUD with the new set of triggers, and I seem to be having a problem.

Whenever it prints the >>>>>>> %1 BASHED %2 <<<<<<<< (or disarmed, tripped, whatever), it prints it exactly like that, without the %1 being replaced by the NPC in question.

I don't use cMUD, so I probably won't be much help. All of my triggers, aliases, etc. are written in zMUD 7.21 and while it usually transfers seamlessly to cMUD there will be an occasional hiccup. Frankly, I don't purchase and/or use cMUD on principle. I have a real problem with Zugg abandoning zMUD and discontinuing all support, and then forcing people that purchased zMUD to purchase yet another license for cMUD. In reality, cMUD is just zMUD version 8.xx that he forced people to buy another license to use.

Your character getting bashed and third parties bashing/getting bashed are separate triggers. I am not sure why cMUD is interpreting the third party version of the bash trigger when your character is the bash target.

Cut/paste your stuff from the Combat Events class in cMUD and I will take a look.

Those are the lines in the 'Wizard'.

This is the XML

Its an issue with the trip trigger, too, at least when its the third party version. I think the reason its interpreting the third party version of the bash trigger (and probably the same reason I can't seem to find a separate version in your master file) is because the syntax "slams into you/target and sends you/target sprawling!" is the same in either case, which is not the case with trip.



I copied your format and added my own trigger specifically for being bashed and it gave me this:



Here's the XML for the trip trigger.



I'm going to peruse the help files and see if I can't something about the differences between cMUD and zMUD.

It looks like the trigger system in cMUD allows for priorities (similar to MUSHclient). You should be able to set the triggers for your character getting bashed to a higher priority than the trigger for third parties bashing/getting bashed.

Imagine that will solve the problem.

EDIT - FYI, the lower the number the higher the priority. So set the priority for your character getting bashed to a lower number than the trigger for third parties bashing/getting bashed.

From the CMUD helpfile...



I wonder if that is the issue?

It could be. Try this and see if it works:

#TRIGGER {%1 slams into %2 and sends %2 sprawling!} {#SAY ~>~>~>~>~>~>~> %1 BASHED %2 ~<~<~<~<~<~<~<;#CO 11,under}