bMotion provides some measure of flood checking to stop people being too annoying with the bot (or to stop the bot being too annoying on its own). Although everything in bMotion is tuned to give a decent balance between saying enough to be entertaining and staying quiet enough to not be annoying, it's very easy for someone who figures out how it works to make the bot say the same thing over and over and over and over...

Flood checking in bMotion assigns each user who is interacting with the bot a score. Scores start at 0, although bMotion won't track a score for a user who hasn't talked to it yet, or hasn't talked to it in a while.

• Doing something that triggers a plugin will increase your score by a small amount.
• If it's the same plugin you triggered last time, you get slightly more points.
• If you use the same text to trigger the plugin, you get slightly more points.
• If you use the same text to trigger the same plugin, you get lots more points.

When a user's flood points goes over a certain threshold, bMotion will ignore 50% of their lines.

When a user's flood points goes over a higher threshold, bMotion will ignore everything from that user.

Flood points tick down at a rate of two ever sixty seconds. Once a user's points are below the relavent thresholds, bMotion will start paying attention to them again. There is no upper limit for the number of points a user can score.

When the bot ignores a line from someone, it will print "FLOOD CHECK on <nick>" to the partyline.

You can view user's flood scores with the .bmotion flood command.