Zugg Software :: View topic - pattern matching suddenly not dumping into database

Newbie Joined: 26 Sep 2010 Posts: 8

Hiho

I had a nice little multistate trigger to track my spell improves. Upon seeing "you improved the spell" it asks for an output of my spell list, finds the name of the spell I was practicing (@spellname) and passes the line containing that name to the second state of the trigger. The line looks something like this:

Glittering Dust glitter verbal&gesture 6 lousy

It ignores the fancy spell name (Glittering Dust) and finds the @spellname (in this case, "glitter"), pattern matches that and the next three variables like so:

(@spellname) %s (*) %s (%x) %s (%w)

When I look at the captured subpatterns I see, just as I expect:

%1: glitter
%2: verbal&gesture
%3: 6
%4: lousy

Hurray! It is then supposed to dump @spellname, %time, @failures (calculated elsewhere), %4, and @failrate (calculated elsewhere) into the database "improves" via the following script:

#new improves {spell=@spellname|time=%time(c)|failures=@failures|level=%4|failrate=@failrate}

And it did! Perfectly! Until....I a) had to rebuild my machine from XP to Win7 (clean install) and b) downloaded the most recent build of cmud (3.32). Since then it creates the new record, puts the @spellname variable in the right place, but nothing else. I have a third state to the trigger that does a simple echo on the screen and that works fine.

Woe is me. I have double checked that all the calculated variables are correctly registered, and in fact, I can echo them to the screen...they just *will not* dump into my database. What up?

Thanks in advance, smart types :)

-Estelle

Sorcerer Joined: 10 Oct 2000 Posts: 706 Location: USA

Estelle,
Can you post the the complete trigger. Just goto your trigger in the editor click on the XML tab, highlight the text and post it in the code tags. Also give us the text from the mud too. Make sure you place it in the code tags also.

Newbie Joined: 26 Sep 2010 Posts: 8

here's the trigger:

Wizard Joined: 22 Mar 2007 Posts: 2320

Early in your code, you have:

Wizard Joined: 22 Mar 2007 Posts: 2320

I don't see any other oddities in your code. It's been a long time since I used the internal database, but your #new command seems to conform to the documentation. You could try reformulating that command as:

Newbie Joined: 26 Sep 2010 Posts: 8

Whee! That did it. Thank you!