All Projects

It would be advantageous to have the bots on the public listing(s) out there. From greypal ( via http://greypal.el-fd.org/csv-doc.html ):

If your bot has no method to access the data via web -> FAIL
If your bot is hostey by el-services.net or learner -> np should work already

You need to provide a URL where a csv file can be retrieved
Format of the URL:
the URL should look like http://www.foo.bar/mybots/Testbot.csv
where "http://www.foo.bar/mybots/" is the base for all your hosted bots.
"Testbot" must match the botname.
and the extension ".csv"

Format of entries:
  botname,Testbot
  owner,Greypal
  location,Testmap,40,50
  buying,Fire Essence,1,2.5
  selling,Fire Essence,1,3.5
Selling/Buying In Detail:
  1. field = action, atm buying or selling
  2. field = "Item Description"
  3. field = amount, a positive number including 0, or * if there is no limit.
  4. field = price, just in gc, please do not use k or such, just for sorting reasons
There should be only one entry for botname, owner and location.
The location entry has the following structure "location,<mapname>,<x-coord>,<y-coord>

Buying and selling entries as needed.
The item description must match the description seen in sto,inv or trade.
If you have a bunch of bots you can also provide a "index" file under the base-url like http://www.foo.bar/mybots/botlist.txt
at minimum there should be one botname per line in raw ascii.
Optional you can add separated by a space-character a url for a existing web-interface.
Just PM me ingame or via forum

First seen on 2010-11-14 23:28 EST (UTC - 5:00), from the error log:

File "/home/qelbot/adversary/bot.py", line 848, in process_pm
  price = get_selling_price(requestor, item_name)
File "/home/qelbot/adversary/bot.py", line 1773, in get_selling_price
  my_db.execute(sql,(v.guild, item))
File "/home/qelbot/adversary/database.py", line 44, in execute
  self.cursor.execute(sql, args)
File "/usr/lib/python2.6/site-packages/MySQLdb/cursors.py", line 173, in execute
  self.errorhandler(self, exc, value)
File "/usr/lib/python2.6/site-packages/MySQLdb/connections.py", line 36, in defaulterrorhandler
  raise errorclass, errorvalue
_mysql_exceptions.OperationalError: (1267, "Illegal mix of collations (latin1_swedish_ci,IMPLICIT)
and (utf8_general_ci,COERCIBLE) for operation '='")

Might be good to be notified when certain items buy/sell. Each item could have a checkbox saying if you want to be notified or not. Then when that item is traded, a notification is sent.

Ultimately this could be configured to send via PM, gossip, email etc

When the bot has an empty inventory, it will continually loop. It’s particularly bad as you can’t stop it from the WebAdmin and it spams the server with reconnect after reconnect.

Trac Ticket #30 - Originally reported by: Krayon

The bot should have a table of item abbreviations. When someone wants to buy/sell an item, they can then use the abbreviated name for that transaction.

Trac Ticket #31 - Originally reported by: Krayon

The bot should support the ability to log guild channel (or any channel for that matter), #GMs, #IGs etc for later retrieval by direct interaction (PM) or the web based interface.

Trac Ticket #39 - Originally reported by: Krayon

The WebAdmin interface should support configuring discounts for players and guilds.

Trac Ticket #40 - Originally reported by: Krayon

WebAdmin should support configuring of responses.

Trac Ticket #43 - Originally reported by: Krayon

The WebAdmin interface could include the ability to view messages as stored in the Messages table. This contains a history of messages sent to/from players using the bot’s “msg” command ( and maybe messages sent via the messaging system developed in #12 (FS#66) too ).

Trac Ticket #49 - Originally reported by: Krayon

WebAdmin fields should perform (better) data validation, such as alpha/alphanumeric/numeric etc.

Trac Ticket #58 - Originally reported by: Korrode

Right now there is a “Stackable” entry for each item in the DB. This has to be set manually atm. If not set correctly it can make the allocated slots info output from the “status” command look confusing. (i.e. more than 36 slots allocated. 36 is maximum in EL).

Please make the bot determine if an item is stackable and set it as such.

Until that is done, if you can be bothered, remove “Stackable” column from WBI and allocated slot info from “status” command output.

Trac Ticket #67 - Originally reported by: Krayon

Bot causes exception when it fails to receive online players list. This can happen if the connection is reset for example (”Connection reset by peer”).

Example:
urllib2.URLError: <urlopen error (104, “Connection reset by peer”)>

Trac Ticket #68 - Originally reported by: Krayon

When the bot fails to connect to the server, or the connection is severed, the bot causes an exception.

Example:
socket.error: (110, “Connection timed out”)

Trac Ticket #75 - Originally reported by: Krayon

The WebAdmin should keep access logs with login/logout etc and times they occur. Perhaps even what modifications took place.

Trac Ticket #82 - Originally reported by: Krayon

Some bots have more than one owner. We need to ensure that they can ALL use owner commands etc. The owner list should therefore be something like a comma separated list. Alternatively it COULD be an Admin table attribute or a separate table. Either way it should be easily known if a player is an owner.

Trac Ticket #86 - Originally reported by: Korrode

Add total item gc value to “status” output.

(display gc bot would have if all items sold)

(currently running v0.10.0045)

Trac Ticket #87 - Originally reported by: Anonymous

Would be nice if we had the option to have bots add /bot name inv/wanted at the end of each advert. this wouldnt take up much space on #jc 3 adverts.

In light of FS#95, it would be good to have the ability to forcibly kill the bot no matter what state it’s in. It would also be useful if the bot had better monitoring and handling of itself ( FS#97 ).

The bot startup script should better monitor the state of the bot and kill it if necessary. See FS#95 and FS#96 regarding this also.

Currently, when the user issues a tell/ask command, the bot doesn’t parse out any punctuation IMMEDIATELY following the nick. This should be done for characters that are illegal for IRC nicks ( TODO: verify this list ).

Summary says it all :)