bored command weights

[Ixrec]

We've often wanted to tweak how likely a certain bored command is to get randomly chosen, but we don't have an exact design in mind for this yet.

The only prep I've personally done for this was thinking about it during #62 enough to convince myself that BoredCommands being a flat list of strings is fine because we'd probably want to store the weights as a separate config item.

[MercurialPony]

Potential idea for an implementation of this feature:

Each bored command will have an associated integer weight, could be 1 by default in case the user doesn't want to bother with it. The chance to run each bored command would be command_weight / total_command_weight so commands with a higher weight have a higher chance to run

This would keep things pretty simple for the end user allowing them to either not specify anything and just go with the default value or have to input only an extra integer

[Ixrec]

Oops. I was not talking about the complexity of implementing weights after they've been configured (which I agree is not that hard), I'm worried about the "UI" complexity of how a moderator edits bored commands and weights.

[MercurialPony]

I was partially taking UI into consideration in my suggestion

Looking at the code, one possibility would be to introduce a new ConfigItemType which would simply have an extra integer weight. The user could (optionally) specify the weight as the first argument so that both arguments could easily be distinguished