Pragmatic Software
9845bd3b00
Tip to ask for a hint after 4 wrong streak
2016-12-06 17:57:50 -08:00
Pragmatic Software
ddd543146f
Minor typo fixes
2016-12-06 17:54:27 -08:00
Pragmatic Software
2cc4302c0b
Update version
2016-12-04 22:00:55 -08:00
Pragmatic Software
c2a2debf3e
Nick-floods are now once again detected
2016-12-04 22:00:50 -08:00
Pragmatic Software
4d2a89987b
Update version
2016-12-01 05:19:04 -08:00
Pragmatic Software
ba7149f518
Add missing parentheses to recently added SQL statements
2016-12-01 05:18:56 -08:00
Pragmatic Software
af02bc43d3
Update version
2016-12-01 05:05:10 -08:00
Pragmatic Software
a4d23bc445
Er, use OR instead of AND...
2016-12-01 05:05:07 -08:00
Pragmatic Software
9eca3d5adc
Update version
2016-12-01 04:57:28 -08:00
Pragmatic Software
d47edc100b
Improve robustness of message history tracking
2016-12-01 04:57:25 -08:00
Pragmatic Software
a5260ef056
Update version
2016-11-30 20:57:28 -08:00
Pragmatic Software
ff51114a4f
Missed a couple of account/ancestor replacements for nick-changes
2016-11-30 20:57:26 -08:00
Pragmatic Software
961f54f261
Update version
2016-11-30 09:28:36 -08:00
Pragmatic Software
3091516cc6
Reduce scope of $ancestor to nick-changes only
...
Move message account debug log messages behind a debug toggle
2016-11-30 09:28:19 -08:00
Pragmatic Software
8ba4ffffe4
More robust coverage of aliases when managing message history accounts
...
When adding a new unknown hostmask to the message history accounts, we now
take significant advantage of the aliases table to find an existing account
id for the hostmask before assigning it a new account id.
Likewise, we now take significant advantage of the aliases table when looking
for a nick-change match.
Fix misc channel case-sensitivity issues, add missing last-seen hostmask
updates, reduce message account linking log verbosity level.
2016-11-29 01:50:49 -08:00
Pragmatic Software
bbf45a3fab
Fix potential channel name case-sensitivity issues; misc minor fixes
2016-11-29 01:44:31 -08:00
Pragmatic Software
3537b74877
Update last_seen hostmask field in WHO replies
2016-11-29 01:43:11 -08:00
Pragmatic Software
5012886d71
Update version
2016-11-28 12:15:32 -08:00
Pragmatic Software
ecd5feced1
AntiKickAutoRejoin: Fix channel case-sensitivity discrepancy and ignore roulette kicks (*BANG!*)
2016-11-28 12:15:26 -08:00
Pragmatic Software
31cb645f30
Update version
2016-11-17 18:34:15 -08:00
Pragmatic Software
a5bb523f96
Make secret stuff more secret
2016-11-17 18:34:11 -08:00
Pragmatic Software
e37b48822b
Update version
2016-11-17 15:57:53 -08:00
Pragmatic Software
df8e15b39e
Fix factlog for deleted factoids not in global channel
2016-11-17 15:57:48 -08:00
Pragmatic Software
01cb062c82
Update quotegrabs
2016-11-16 19:20:56 -08:00
Pragmatic Software
13fade748e
Update factoids
2016-11-16 19:20:27 -08:00
Pragmatic Software
107b4e9883
Update version
2016-11-16 19:15:50 -08:00
Pragmatic Software
3fbefa6746
Put some alias linking messages behind a debug toggle
2016-11-16 19:15:45 -08:00
Pragmatic Software
5d3298462a
Add error messages to a couple of commands
2016-11-16 19:14:39 -08:00
Pragmatic Software
0e4f2d1447
Minor effective-level /kick derp
2016-11-16 19:14:00 -08:00
Pragmatic Software
fdf529f2ae
Update version
2016-11-16 19:07:04 -08:00
Pragmatic Software
f3b3e90cdc
Add factoid effective-level metadata and ability to kick from such factoids
...
Factoids can now have an effective-level metadata field. When set, certain
functionality requiring an effective-level will be enabled.
For now, that is currently only the /kick command, which has an effective-level
of 10.
Factoids with an effective-level set will also have the locked metadata
attribute set as well to prevent people from changing the factoid. The
locked and/or effective-level attributes will be removable only by admins
whose level is equal to or greater than the effective-level.
2016-11-16 19:07:01 -08:00
Pragmatic Software
39399e78ae
Allow debug tracing of event handlers; don't remove handlers on error
2016-11-16 18:59:13 -08:00
Pragmatic Software
4ed61096dd
Missing hash dereference
2016-11-04 12:40:17 -07:00
Pragmatic Software
6fbd6d5620
Update version
2016-10-29 10:47:12 -07:00
Pragmatic Software
3bd424aacc
Fix possible case-sensitivity issues
2016-10-29 10:47:08 -07:00
Pragmatic Software
72faa9169f
Update version
2016-10-23 03:52:03 -07:00
Pragmatic Software
170dac5776
Improve !cmd and nick: !cmd processing
2016-10-23 03:51:59 -07:00
Pragmatic Software
0397068a7f
Undo recent blink addition
2016-10-23 03:50:34 -07:00
Pragmatic Software
7f00047af8
Update version
2016-10-14 05:56:57 -07:00
Pragmatic Software
8addeb5d49
Allow "nick: !command" to address to nick; minor improvements
2016-10-14 05:56:54 -07:00
Pragmatic Software
4764b034e1
Update version
2016-09-28 14:13:47 -07:00
Pragmatic Software
c64dca7b07
Forgot a return 0 in an IRC handler, causing other related handlers to not fire after that handler
2016-09-28 14:13:44 -07:00
Pragmatic Software
49a21b2027
Update version
2016-09-25 12:59:05 -07:00
Pragmatic Software
c56b9662b8
Whoops, fix nick-similarity behavior for non-nicks
2016-09-25 12:59:03 -07:00
Pragmatic Software
c6473d0255
Update version
2016-09-25 00:24:52 -07:00
Pragmatic Software
2001fc1908
Whoops, return proper nick-casing for exact-match is_present_similar() result
2016-09-25 00:24:49 -07:00
Pragmatic Software
81e106285e
Update version
2016-09-25 00:03:40 -07:00
Pragmatic Software
f34854fcec
Add nick similarity completion
...
Previously, the bot wouldn't address people by nick if the provided nick
argument doesn't exist in the channel.
Now, the bot's nick list is searched for a nick with a certain similarity
percentage in the order of most recently spoken nicks first. This allows
the bot to address nicks when somebody may have forgotten to add a trailing
underscore/punctuation or may have typoed the nick.
The similarity percentage can be set via the interpreter->nick_similiarty
registry key. A value of 0 should disable the behavior.
2016-09-25 00:03:37 -07:00
Pragmatic Software
6369a8df99
Update version
2016-09-23 18:32:03 -07:00
Pragmatic Software
3fd2519a87
Minor text change; don't aggressively pursue ping-timeouts
2016-09-23 18:32:00 -07:00
