mirror of
				https://github.com/Mikaela/Limnoria.git
				synced 2025-11-04 01:27:21 +01:00 
			
		
		
		
	
		
			
				
	
	
		
			48 lines
		
	
	
		
			1.8 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
			
		
		
	
	
			48 lines
		
	
	
		
			1.8 KiB
		
	
	
	
		
			Plaintext
		
	
	
	
	
	
Roughly in order of precedence (the closer to the front of the file,
 | 
						|
the more likely it'll be done before next release):
 | 
						|
 | 
						|
* Update the database infrastructure to allow other RDBMSes.
 | 
						|
 | 
						|
* Improved (and perhaps integrated) Services and Enforcer plugins.
 | 
						|
 | 
						|
* Filters need to be added to the logs during testing so many logs
 | 
						|
  (useless during testing) won't occur.
 | 
						|
 | 
						|
* We should probably add a "hello" command to make things more
 | 
						|
  compatible with Eggdrop, since we've been replacing many eggdrop
 | 
						|
  bots lately.
 | 
						|
 | 
						|
* Config.list should prefix ChannelValues with #.
 | 
						|
 | 
						|
* We should be able to set the log level for plugins individually.
 | 
						|
 | 
						|
* Rbot has a "remind" plugin that seems pretty cool, we should get
 | 
						|
  one as well.
 | 
						|
 | 
						|
* MozBot has a "list" plugin that seems pretty cool, we should get
 | 
						|
  one as well.
 | 
						|
 | 
						|
Problems that involve a lot of tedious minutiae, but really need to
 | 
						|
be done at some point:
 | 
						|
 | 
						|
* ircutils.{isChannel,isNick,toLower} should be static methods on
 | 
						|
  each Irc object, since they can vary per-network.  That's not the
 | 
						|
  tedious part; the tedious part is having every other place that
 | 
						|
  uses them use those methods instead.
 | 
						|
 | 
						|
Hard problems that won't get done until someone really wants to have
 | 
						|
some fun:
 | 
						|
 | 
						|
* Redundant relaying -- having more than one bot handle relaying,
 | 
						|
  where a secondary one will automatically take over if the first
 | 
						|
  becomes incapacitated.
 | 
						|
 | 
						|
* Have the bot detect when other bots are in the channel responding
 | 
						|
  to the same prefix character, and do something based on that.
 | 
						|
 | 
						|
* Unicode support.  Basically, we'd have to have a way to set the
 | 
						|
  encoding for the server, and use unicode throughout internally.
 | 
						|
  The real issue is how much it would affect the current code to
 | 
						|
  switch it over to unicode, and what kind of burden it would put on
 | 
						|
  plugin authors to deal with that issue.
 |