Hey.
Seeing as VhaBot (see 1) and BeBot doesn't seem to be maintained much (if at all) lately, and the BudaBot developers refusing to implement simple bugfixes without providing any convincing reason for why not (see 2a, 2b), I think it's time to get another alternative on the playing field. Therefore, I'm bumping the "Bot#" (bot-sharp) project up a few notches on my to-do list.
Bot# is an AO chatbot project initialized by Iriche and myself. It's written in c# (.Net 2.0), is based on vhabs Vha.Net library (the same library which powers Vha.Chat), and is intended to be a general-purpose guildbot with a simple yet powerful module system in mind.
Bot# originally came to be because both Iriche and I were working on our own, separate c# bots for personal use, and we decided to cooperate on making a common one. My motivation in this is to make a replacement for my existing PHP-based bot ("FLWBot").
Ideas & suggestions for features are welcome. Keep in mind, this is a brainstorming; A creative zone. I'm not interested in critique against the ideas people post here. You are not required to provide arguments for why we should consider your idea; But if you want to provide any points for/against, keep it short and clean.
It would be preferable if you post a small description of your idea, maybe an example. Again, try to keep it short & clean.
I'll start with what I have already decided to port over from my current bot to the new one. Nothing in this list is final, and items may be replaced with ideas posted by you.
- Inter-guild relay
- Through private groups
- Through IRC
- Through tells (discouraged)
- Support for relaying chatblobs and item links
- Shared alts list between connected guilds (optional)
- Compatibility with VhaBot, BeBot and BudaBot relay protocols
- Relay of public bots broadcast messages, preferably by joining their private groups
- The normal, expected commands: online, whois, history, lca, is, item(s), news, level, xp, ai, team, pvp, roll, roster, calc, notes (personal & guild/relay-friendly), timer (both realtime and online)
- Less common commands, such as RelayCommand, Show, quote
- Windows and Linux (through mono) support
- Easy setup & configuration (Easy to understand configuration files, and wizards)
- Per-user tracking lists (makes !online show if that person you're buying something from is online, etc)
- Integration with
- http://towerwars.info/ - for updated towerwar information & statistics (Even if your bot is on an unstable host, you'll have updated towerwar information) (optional)
- AOU Calendar (and more?)
- Market watchers (such as http://rubi-ka.com/services.php)
Please post your ideas & thoughts; What would you like to see in a guildbot?