One of the limitations of Mubot is that if karma is altered multiple times in a message, only the first alteration is actually made. For example, if someone says: John++ Cameron++ Cromartie-- Mubot only alters John’s karma (lambdabot would alter all three).

So after I had made the change to fix it, but before I restarted the bot, I demonstrated the current problem:

< carlin> mubot: karma mubot
< mubot> mubot is of an unknown quantity
< carlin> mubot++ mubot++
< carlin> mubot: karma mubot
< mubot> mubot has a karma of 1

Restarted the bot and proceeded to demonstrate the fix:

-!- mubot [n=zaslon@phoenix.theintersect.org] has joined #perl6
< carlin> mubot: karma mubot
< mubot> mubot has a karma of 1
< carlin> mubot++ mubot++
< carlin> mubot: karma mubot
-!- mubot [n=zaslon@phoenix.theintersect.org] has quit [Read error: 54
(Connection reset by peer)]

This is what the terminal said:

:sendak.freenode.net 366 mubot #perl6book :End of /NAMES list.
:carlin!n=carlin@phoenix.theintersect.org PRIVMSG #perl6 :mubot: karma mubot
:carlin!n=carlin@phoenix.theintersect.org PRIVMSG #perl6 :mubot++ mubot++
Segmentation fault

Worked fine after I restarted it:

< carlin> mubot++ mubot++
< carlin> mubot: karma mubot
< mubot> mubot has a karma of 3
< carlin> \o/

I believe the segfault was caused due to the size of the karma.log file (and subsequently the %.karma hash) as I imported every karma entry from lambdabot — About 1700 entries.

I might have to trim out some of the fluff, for example I don’t think we need to keep track of +++++[>+++++<-]>[>++<-]>'s 1 karma point …