 |
marduk
Beginner
Joined: 05 Feb 2006
Posts: 14
|
 Posted: Tue Nov 23, 2010 1:10 am
gmcp trigger not working
|
I have been away from mudding for a while, and I just got CMUD 3.32 pro. My mud is Midkemia, and I am noticing that the mapper is not "just working". I'd like to do some manual tagging of exits and checking of vnums in order to fix this. The problem is, I can't seem to get a simple gmcp trigger to work.
| Code: |
<trigger type="GMCP" priority="330" newline="false" prompt="true" id="33">
<pattern>Room.Info.exits</pattern>
<value>stuff="got it"</value>
</trigger>
|
Nothing happens with this trigger when I walk around.
Clues? |
|
|
|
|
charneus
Wizard
Joined: 19 Jun 2005
Posts: 1876
Location: California
|
Posted: Tue Nov 23, 2010 1:20 am
|
Does your MUD support GMCP? Do you have GMCP enabled under preferences?
If your MUD supports GMCP, are you sure it's room.info.exits?
Also, go under Preferences->Protocols and make sure the things you want are set to 1. |
|
|
|
|
marduk
Beginner
Joined: 05 Feb 2006
Posts: 14
|
Posted: Tue Nov 23, 2010 1:53 am
|
Midkemia Online is an IRE mud, and it supports GMCP. I'm able to do a successful "#SHOW %gmcp.Room.Info.exits" from the command line, so I assumed that this was the correct pattern for a GMCP trigger.
Since, I can access the GMCP info, I assume that answers your questions, thus far? |
|
|
|
|
charneus
Wizard
Joined: 19 Jun 2005
Posts: 1876
Location: California
|
Posted: Tue Nov 23, 2010 6:43 am
|
Just logged onto your MUD and tested it... I should have seen this earlier, but meh... you can't go to a third key with gmcp... so instead of Room.info.exits, you can only do Room.Info.*... don't know why... but that's your reason.
|
|
|
|
|
marduk
Beginner
Joined: 05 Feb 2006
Posts: 14
|
Posted: Tue Nov 23, 2010 11:13 am
|
Sweet. That worked.
Interestingly, in the trigger pattern, I wasn't able to get this to work: #show "got it". Instead, I had to update a variable to verify the trigger: stuff="got it".
Thanks for your help! |
|
|
|
|
marduk
Beginner
Joined: 05 Feb 2006
Posts: 14
|
Posted: Tue Nov 23, 2010 1:28 pm
|
#print works, but not #show. Not an issue, just pointing it out.
|
|
|
|
|
Rahab
Wizard
Joined: 22 Mar 2007
Posts: 2320
|
Posted: Tue Nov 23, 2010 2:08 pm
|
You're saying that
didn't work? That's very strange. Do you have some trigger gagging that? |
|
|
|
|
marduk
Beginner
Joined: 05 Feb 2006
Posts: 14
|
Posted: Tue Nov 23, 2010 2:56 pm
|
My cmud install is very sparse, right now. I have just the one gmcp trigger for Room.Info, and I just added a simple pattern trigger to test #show. No gagging.
When #show is the only line in a trigger script, it will not display literal text. I haven't tested it beyond that. I'm just using #print now, so it's not a big deal to me. |
|
|
|
|
Anaristos
Sorcerer
Joined: 17 Jul 2007
Posts: 821
Location: California
|
Posted: Fri Nov 26, 2010 6:21 pm
|
It seems to me there is a problem with your trigger specification. I fail to see "param=201" in your xml.
|
|
_________________
Sic itur ad astra. |
 |
|
|
MattLofton
GURU
Joined: 23 Dec 2000
Posts: 4834
Location: USA
|
Posted: Fri Nov 26, 2010 6:46 pm
|
Param=201 is not the problem. CMud ignores it for GMCP triggers.
|
|
_________________
EDIT: I didn't like my old signature |
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon Nov 29, 2010 6:16 pm
|
The Pattern for a GMCP trigger needs to be just the name of the GMCP message. The "exits" information is one of the data keys for the "Room.Info" message. So your pattern should just be "Room.Info". No * or anything else.
Then in the trigger you can access the %gmcp.Room.Info.exits variable to get the data you need. |
|
|
|
|
|
|
|
