Zugg Software :: View topic

Magician Joined: 23 Nov 2004 Posts: 364

Ansi triggers that have been working from cmud 1.30, upon upgrading to 1.32 no longer work.

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

Some examples please?

Posted: Wed May 02, 2007 5:59 pm

Yes, please post the exact trigger that broke, along with the sample text from the MUD that would trigger it. We can't read your mind!

Magician Joined: 23 Nov 2004 Posts: 364

pattern: %e[42m({@botmobs})
mobs look like: <27>[42mLarge zombie [wounded]<27>[0m.

this worked perfectly before upgrading to 1.32

my room shorts
pattern: %e[1;32m* ~((*)~)%e[0mÑ
room short looks like: <27>[32;1mDark Maze - Level 1 (s,w)<27>[0mÑ

and so on, none of this works now. every trigger has ansi trigger enabled. And to repeat, everyone worked in cmud 1.30. Could it be that I upgraded 1.30->1.32 and didn't go 1.30->1.31->1.32?

Posted: Thu May 03, 2007 5:05 pm

Confirmed and added to bug list. Should be fixed in the next version.

Posted: Mon May 07, 2007 9:45 pm

OK, I *think* I've got this fixed in the next version to be released later tonight. But it was tricky, so if it doesn't work in v1.33 then post again. You might need to copy the line from the MUD and paste it into the Trigger Pattern field to see what CMUD thinks the proper ANSI codes really are. CMUD doesn't store the actual ANSI codes sent from the MUD...it re-creates the ANSI code based upon the color of the text on the screen. So, all of the bugs regarding the color changes with styles in the last couple of versions can mess this up.

Anyway, wait till 1.33 is out tonight, and then test it again for me. But your two examples shown above work now in v1.33 on my system.

Magician Joined: 23 Nov 2004 Posts: 364

It's working smoothly. Thanks a lot Zugg.

Posted: Tue May 08, 2007 5:34 pm

Great! Thanks for confirming that.