MrBot - Revision history

Licah Fox: RS IRC Bot moved to MrBot over redirect: More accurate title

2010-03-27T15:18:12Z

RS IRC Bot moved to MrBot over redirect: More accurate title

← Older revision	Revision as of 15:18, 27 March 2010
(No difference)

2010-03-27T15:17:46Z

← Older revision		Revision as of 15:17, 27 March 2010
Line 1:		Line 1:
	Currently online in the major RS channels as '''MrBot'''.		Currently online in the major RS channels as '''MrBot'''. MrBot has been online since August 4, 2007. He was offline for four months, 2008.02.07-2008.06.07, but has been back ever since.

			If MrBot is not online, send an email to Licah and he will investigate.

	See http://www.rebelsquadrons.org/irc/bot.help for instructions on using the bot.		See http://www.rebelsquadrons.org/irc/bot.help for instructions on using the bot.

2010-01-01T01:36:57Z

← Older revision		Revision as of 01:36, 1 January 2010
Line 7:		Line 7:
	* Bot doesn't reconnect sometimes :(		* Bot doesn't reconnect sometimes :(
	* Bot sometimes just vanishes and ceases operation without error. Only possible clues are that Josh was peered immediately beforehand, and there was a batch of mysql connection errors just before that. Bot should never reach end of script without !quit.. research!		* Bot sometimes just vanishes and ceases operation without error. Only possible clues are that Josh was peered immediately beforehand, and there was a batch of mysql connection errors just before that. Bot should never reach end of script without !quit.. research!
			* Aggressively attempt to regain nick MrBot if stolen
	=== and then ===		=== and then ===
	* Don't respond to !lookup in #db		* Don't respond to !lookup in #db

2009-12-02T16:30:28Z

db lookup

← Older revision		Revision as of 16:30, 2 December 2009
Line 8:		Line 8:
	* Bot sometimes just vanishes and ceases operation without error. Only possible clues are that Josh was peered immediately beforehand, and there was a batch of mysql connection errors just before that. Bot should never reach end of script without !quit.. research!		* Bot sometimes just vanishes and ceases operation without error. Only possible clues are that Josh was peered immediately beforehand, and there was a batch of mysql connection errors just before that. Bot should never reach end of script without !quit.. research!
	=== and then ===		=== and then ===
			* Don't respond to !lookup in #db
	* Fix topics to allow more than one word :P		* Fix topics to allow more than one word :P
	* MrBot loses track of you if you change your nick to the same characters, but different cases. (Licah > LICAH)		* MrBot loses track of you if you change your nick to the same characters, but different cases. (Licah > LICAH)

2009-11-16T02:41:05Z

← Older revision		Revision as of 02:41, 16 November 2009
Line 9:		Line 9:
	=== and then ===		=== and then ===
	* Fix topics to allow more than one word :P		* Fix topics to allow more than one word :P
			* MrBot loses track of you if you change your nick to the same characters, but different cases. (Licah > LICAH)
	* is there some kind of autotopic going on? weird...investigate		* is there some kind of autotopic going on? weird...investigate
	* Update "seen" if person PARTs a channel		* Update "seen" if person PARTs a channel

2009-10-16T04:22:50Z

← Older revision		Revision as of 04:22, 16 October 2009
Line 9:		Line 9:
	=== and then ===		=== and then ===
	* Fix topics to allow more than one word :P		* Fix topics to allow more than one word :P
			* is there some kind of autotopic going on? weird...investigate
	* Update "seen" if person PARTs a channel		* Update "seen" if person PARTs a channel
	* Automatically set +nst if opped or entering channel		* Automatically set +nst if opped or entering channel

2009-10-15T04:04:07Z

← Older revision		Revision as of 04:04, 15 October 2009
Line 8:		Line 8:
	* Bot sometimes just vanishes and ceases operation without error. Only possible clues are that Josh was peered immediately beforehand, and there was a batch of mysql connection errors just before that. Bot should never reach end of script without !quit.. research!		* Bot sometimes just vanishes and ceases operation without error. Only possible clues are that Josh was peered immediately beforehand, and there was a batch of mysql connection errors just before that. Bot should never reach end of script without !quit.. research!
	=== and then ===		=== and then ===
			* Fix topics to allow more than one word :P
	* Update "seen" if person PARTs a channel		* Update "seen" if person PARTs a channel
	* Automatically set +nst if opped or entering channel		* Automatically set +nst if opped or entering channel

2009-10-15T00:05:23Z

← Older revision		Revision as of 00:05, 15 October 2009
Line 8:		Line 8:
	* Bot sometimes just vanishes and ceases operation without error. Only possible clues are that Josh was peered immediately beforehand, and there was a batch of mysql connection errors just before that. Bot should never reach end of script without !quit.. research!		* Bot sometimes just vanishes and ceases operation without error. Only possible clues are that Josh was peered immediately beforehand, and there was a batch of mysql connection errors just before that. Bot should never reach end of script without !quit.. research!
	=== and then ===		=== and then ===
			* Update "seen" if person PARTs a channel
	* Automatically set +nst if opped or entering channel		* Automatically set +nst if opped or entering channel
	* Don't reply to X's msgs		* Don't reply to X's msgs

2009-09-18T16:24:42Z

← Older revision		Revision as of 16:24, 18 September 2009
Line 9:		Line 9:
	=== and then ===		=== and then ===
	* Automatically set +nst if opped or entering channel		* Automatically set +nst if opped or entering channel
			* Don't reply to X's msgs
			* Swear filter: allow setting via PM?
	* further standardize error messages? -- make everything work like !op - including self-op-recognition		* further standardize error messages? -- make everything work like !op - including self-op-recognition
	* resolve owner but not manager problems - e.g. Swifty #rid.		* resolve owner but not manager problems - e.g. Swifty #rid.

2009-09-18T16:21:55Z

+nst

← Older revision		Revision as of 16:21, 18 September 2009
Line 8:		Line 8:
	* Bot sometimes just vanishes and ceases operation without error. Only possible clues are that Josh was peered immediately beforehand, and there was a batch of mysql connection errors just before that. Bot should never reach end of script without !quit.. research!		* Bot sometimes just vanishes and ceases operation without error. Only possible clues are that Josh was peered immediately beforehand, and there was a batch of mysql connection errors just before that. Bot should never reach end of script without !quit.. research!
	=== and then ===		=== and then ===
	* ~~Swear filter~~		* Automatically set +nst if opped or entering channel
	* further standardize error messages? -- make everything work like !op - including self-op-recognition		* further standardize error messages? -- make everything work like !op - including self-op-recognition
	* resolve owner but not manager problems - e.g. Swifty #rid.		* resolve owner but not manager problems - e.g. Swifty #rid.