Well, I accidentally trained a bunch of mobs on to the opposing side in pande, so I figured that I'd try to apologize by way of code.  So I finished off everything on todo, and here are the results.

// Instructions:
// To start a vote,
//   !vote start <question>? <choice 1> <choice 2> ...
//   The question must end with a question mark, and contain no question marks within it.
//   The choices must be single words, seperated by a single space between each word.
// To cancel a vote,
//   !vote cancel <optional reason>
// To terminate a vote early and display results,
//   !vote end <optional reason>
// To display the last vote's results,
//   !vote results
// To display the vote history
//   !vote history
// To display the vote history details of a particular vote
//   !vote history <number>
// To change the output channel,
//   !vote output <gc|pgmsg|both>
// To place a vote
//   !placevote <number>
// To adjust the running time of votes
//   !vote length <number>
// To adjust the interval between messages to chat
//   !vote interval <number>
///////////////////////////////////
// Changelog:
// 2.1
//  * Fixed to use 2 sec cron instead of 1 sec cron, as 1 sec cron isn't fully supported
//  * Now has an internal counter for keeping track of time elapsed, to fix issues where cron
//   is called multiple times in the same second, or not called during certain seconds.
// 2.0
//  * Changed it to announce once per 20 seconds instead of once per 10 seconds
//  * !vote interval to adjust how often we announce to chat
//  * Fixed bug where "vote now" would appear multiple times in one interval
//  * Set cron dynamically when a vote is started.  (Thanks Snowsy!)
//  * Save and load settings between bot restarts
//  * !vote history, and changed !vote result to use DB
//  * Started using <botname> and <pre> where appropriate
//  * Helpfile updated
// 1.1
//  * Wrote a help file
//  * Added vote length adjustment
//  * Command responses are now sent to the same channel as the command was issued (where applicable).
//  * Added responses to some commands to show that they worked.
// 1.0
//  * First Version, includes start, cancel, end, results, output, and placevote
--
2.1 uploaded

nice one, im gonn edit it to fet my needs, nice work btw

I uploaded a new version that uses 2 sec cron.  Also, a minor fix that should help heavily loaded bots display properly, at the cost of reduced (theoretical) accuracy in voting time calculation in some unusual cases.

This is all pedantic detail that I don't think anyone but a programmer would care about, and even that's a bit iffy.  So, feel free to ignore this post.

Anyway, I'll explain the gritty details about my statement above.  The vote module sends a textbox link to chat every 20 seconds (configurable) indicating that the vote is still running.  The previous version used 1 sec cron, and checked delta time started and current time.  In some cases, under a heavily loaded bot, bebot seems to have multiple cron calls in the same second.  If this occurred during the 20 second time when the module was supposed to show the voting booth, it would spam private group rather nastily.  In other cases, it would skip that particular second entirely, and no "vote in progress, click here" message would appear at all.

The fix uses a counter to count elapsed time, and assumes that bebot is honest about the cron timer for accuracy.  So, with the 2 second tick, it will spam at 10 ticks, and again at 20 ticks, and complete at 30 ticks.  So, theoretically, this would produce the same result (a single text box every 20 seconds), in practice the timing may be slightly off, but it's close enough to make no difference.

Well, it sends a message to group every 20 (configurable) seconds stating that the vote is open.  An ideal solution would be cron with completely variable scheduling, instead of hard coded 2 seconds or whatnot.  That can only be done with some overhead that I'm not sure is worth the gain.  As is, I don't see a way to keep the click to vote spam without the admittedly overly short cron.

With that said, I set the cron dynamically when the vote starts, and clear it when the vote is over, so the performance hit should be minimal, and only occur during a vote.  If every module does that, then there won't be much of an issue because only a few modules will have a cron at any particular time.

That's my opinion, of course, feel free to prove me wrong.

Hi there,

found this and wanted to make it run on our bot (2.9).
But it only sends Messages to PrivGrp.
Any idea?

[Edit]
Ok, shame on me. Does not work in tells to the Bot. 
Sorry, works fine, ever did, I think.

But one thing regarding the database settings.
I think there is an error:
$results = $this -> bot -> db -> select("SELECT `setting`, `value` FROM settings WHERE setting='VoteTimer'");
if (!empty($results))
{
$this -> output_to = $results[0][1];
$this -> bot -> db -> query("INSERT INTO settings (`setting`, `value`) VALUES ('VoteOutput', 'pgmsg')");
}
There is at first a check for 'VoteTimer' but than an INSERT for 'VoteOutput'. Should this not be 'VoteTimer' too?
[/EDIT]

Regards,

 lulifuz