 |
mastiff34
Beginner
Joined: 24 Sep 2009
Posts: 12
|
 Posted: Mon Nov 23, 2009 12:45 am
Tagging Bug with cmud 3.12
|
I been trying to get the mapper to work with my mud to no avail, so I decided to try to the tagging approach,
my mud rooms and prompt look like this:
A junction in The Castle of Greenlight (n,s,e).
}
I have setup the following tags to name the name, exit and prompts:
<trigger priority="22370" id="2237">
<pattern>^(*) ~((*)~).</pattern>
<value>#tag name,exit {%1} {%2}</value>
</trigger>
And the prompt is:
<trigger priority="22380" id="2238">
<pattern>^}$</pattern>
<value>#tag prompt</value>
</trigger>
--------------------------
Then, when I go to reconfigure the mapper I get the entire mud line with the name and description as an exit.
Anyone have any clues? I have tested my patterns and they match using the mud output, so not sure what
is going on.
thanks!
-Matt |
|
|
|
|
Rahab
Wizard
Joined: 22 Mar 2007
Posts: 2320
|
Posted: Mon Nov 23, 2009 2:55 pm
|
Try doing the tag in separate lines:
| Code: |
<value>
#tag name {%1}
#tag exit {%2}
</value>
|
Your construction should work. If the tagging above works, perhaps there is a bug in #tag handling multiple fields at a time. |
|
|
|
|
mastiff34
Beginner
Joined: 24 Sep 2009
Posts: 12
|
Posted: Mon Nov 23, 2009 4:14 pm
|
I tried it with multiple lines, but same effect.
|
|
|
|
|
Dumas
Enchanter
Joined: 11 Feb 2003
Posts: 511
Location: USA
|
Posted: Mon Nov 23, 2009 7:43 pm
|
I feel stupid for asking this, but is there no space after the } prompt?
|
|
|
|
|
mastiff34
Beginner
Joined: 24 Sep 2009
Posts: 12
|
Posted: Tue Nov 24, 2009 12:55 am
|
No, it's an empty line from best I can tell I copy and pasted it from the mud to the editor.
If anyone wants to try its zombiemud.org and just set brief to reprodue it. |
|
|
|
|
Dumas
Enchanter
Joined: 11 Feb 2003
Posts: 511
Location: USA
|
Posted: Tue Nov 24, 2009 2:38 am
|
Oh, it uses the greater than sign as a prompt. Unless you set the } symbol through the muds prompt command.
Though I couldn't get it to work either. Was having the whole line marked as the exits for me. |
|
|
|
|
mastiff34
Beginner
Joined: 24 Sep 2009
Posts: 12
|
Posted: Tue Nov 24, 2009 11:41 am
|
Yah, that's what it does for me as well, seems like it's bugging. I set the } throught the prompt command yah.
But, it sounds like you confirmed the bug perhaps. |
|
|
|
|
Dumas
Enchanter
Joined: 11 Feb 2003
Posts: 511
Location: USA
|
Posted: Tue Nov 24, 2009 12:50 pm
|
Bleh, I converted that to regex but still get the same problem. It matches in the pattern matcher with the correct assignments, but for some reason it isn't then transferring it to the TAG correctly?
|
|
|
|
|
mastiff34
Beginner
Joined: 24 Sep 2009
Posts: 12
|
Posted: Tue Nov 24, 2009 12:56 pm
|
Yep, that is exactly what I am seeing it's like the tagger is not feeding/overriding the mapper correctly, at least from what I have read on this forum and the help about what tagging is suppose to do.
|
|
|
|
|
Rahab
Wizard
Joined: 22 Mar 2007
Posts: 2320
|
Posted: Tue Nov 24, 2009 9:48 pm
|
Did you verify that the trigger was actually firing, by putting a #say statement or something into it? That's the only other test I can think of offhand, before I leave for the day.
|
|
|
|
|
Dumas
Enchanter
Joined: 11 Feb 2003
Posts: 511
Location: USA
|
Posted: Tue Nov 24, 2009 9:55 pm
|
Yes, it is firing.
Hmm, the prompt trigger isn't though.
Bleh, forgot to change it to Trigger on Prompt and uncheck Trigger on Newline.
Still getting pegged as one long exit line. |
|
|
|
|
Dumas
Enchanter
Joined: 11 Feb 2003
Posts: 511
Location: USA
|
Posted: Tue Nov 24, 2009 10:11 pm
|
Oddly enough, even though the configurator is not detecting it right, I'm still getting proper rooms being made.
Try this in a text file then import the configuration
| Quote: |
Version: 211
Name Start: 0
Desc Start: -1
Desc End: 32
Exit Start: 0
Exit End: 0
Exit in Prompt: 0
Exit in Name: 1
Exit contains key: 0
Name paragraph: 0
Desc paragraph: 0
Exit paragraph: 0
Bracket prompt: 1
Short exit names: 1
vNum in Name: 0
Exit keyword: exit
Exit after keyword: 0
Match room name mode: 1
Use Descriptions: 0
Entire exit paragraph: 0
Single char exit: 0
Autoprompt detect: 1
Complex prompt: 0
Prompt char: >
Name ends in period: 0
Number prompt: 0
No MUD Prompt: 0
Room Name Propercase: 0
Prompt trigger: ^\>\s*$
Prompt Regex: 1
Description changes: 0
[End]
|
The Prompt trigger there is the regex you should use for the prompt tag trigger (though change the > to }).
And as it is preferred not to use the * so much, use this regex for the room name/exit line
^((?:\w+\s)+)\(((?:\w+,*)+)\).\s*$ |
|
|
|
|
mastiff34
Beginner
Joined: 24 Sep 2009
Posts: 12
|
Posted: Wed Nov 25, 2009 2:33 am
|
That works great in the mapper, but the cofiguration doesnt work at all, but all i really care about is the mapper, thanks for the excellent support.
I do think it's a bug tho that its not showing correctly |
|
|
|
|
|
|
|
