repeatedchatter was the first refactoring bit that actually got applied. I disliked how huge the message opcode routine is and started down the road of making each chatter /command a separated node with common routines for parsing out a user name/number, etc. I got distracted making something like htmlcode() but that could return a list and so never split up the big elsif block.

And repeatedchatter turned out to be enough refactoring such that 'insertmessage' and such weren't a high priority. However, they still might be useful for places like '/msg me when I get a reply' and such; but those don't matter for this table split since it is the public chatter that is moving.

So I'd still like to eventually split up the message opcode by returning output values via a passed-in hash ref (a technique I think you came up with). And eventually remove the last couple of 'insert into message' chunks of code (unless they are already using repeatedchatter).

But when you identify code that would no longer be useful for such refactoring, make it as dead, sure.