All Projects

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 :)

Trac Ticket #6 - Originally reported by: Catspaw <dobiesnaga@googlemail.com>

I wondered about a command to report back the 5 best / worst selling items over a period of time (either since the bot was active or defined in a number of days with a command like sales_days). The command could be something like sales_rep and I am not sure if it would be worth setting the number of items it reports with another command like sales_number (set from 1 - 10).

Trac Ticket #12 - Originally reported by Krayon:

As well as listing guildies in the web admin area (see #9), I think the ability to msg them from the interface would be useful. Additionally messaging to the entire guild (via #gm) would also be nice.

Trac Ticket #22 - Originally reported by: Krayon

Customisable messages are currently stored in the config.py file. They should be moved to the

When this is done, the messages should be changed from REQUIRING the data placeholders (%s etc) to optionally containing them. The system can be made more advanced, for
1. %normal_cost% = cost of item before
2. %cost% = item
3. %discount% = discount percent
4. %guild% = guild they belong to, %player player’‘s

msg_trade_total_guild_discount = “Well %player%, because you belong to guild %guild%, we are
give you a %discount% percent discount off the price. This will therefore only be %cost%gc


This would allow for much better customisability with messages.

Trac Ticket #24 - Originally reported by: Korrode

When buying something from the Bot, after the trade is done it gives the wrong responce. Instead of saying “Thank you” it says “Sorry We couldnt come to an agreement.

Trac Ticket #29 - Originally reported by: SleepyDragon

Ok, I discovered by accident why she is not correctly recording all transactions in the db. When you trade with her if you don’t press the accept buttons in the right order so that she comes up with the message “It’s been a pleasure doing business with you” etc and instead comes up with the message “sorry we couldn’t reach an agreement”, even if the transaction has been completed it will not register in the db.

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 #41 - Originally reported by: Krayon

WebAdmin should support the viewing of transaction history.

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 #57 - Originally reported by: Korrode

Remove “Home” and “Storage” from both the WBI (General tab) and the in-game admin “help” command output until such time as those features are tested and confirmed to be working properly.

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 #59 - Originally reported by: Korrode

When a slot is empty, QELBot displays that slot as holding an item called “*unknown*”. i.e. a ling from her “dump_inv” command in-game looks like this:

PM from FlameKeeper: Slot: 32 Qty: 0 Item: *unknown*

The item *unknown* appears in the Items list in the WBI, probably best to make it now appear.

Trac Ticket #61 - Originally reported by: Korrode

QELBot to have “Leonard the Leopard” messages.

at 3:25 game time to say “Leonard the Leopard will wake up in 5 minutes!”

and at 0:30 game time to say “Leonard the Leopard has gone to sleep”

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 #74 - Originally reported by: Korrode

requesting the ability to have people in the “Guild” list have a “GuildAdmin” settable option, and when turned on, they have access to bot’s “say” command, but no other normal admin features.

(very useful for a guild with multiple guild masters that need access to rank 20 ability, but are not all owners of the bot, or using it to sell their wares).

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 #84 - Originally reported by: Krayon

As listed in #77 item 3, a list of the bot’s current inventory would be useful. You could therefore see exactly what it has on it. Potentially, the items list could have a column for currently holding and have a toggle for “only show items currently in inv”.

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.

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.

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.

QELServ needs to be the BEST ... just BEST ... ever!

( from: http://qelserv.quadronyx.org/forums/?topic=15.msg238#msg238 )

Quote from: collardhills on 2008-11-13, 02:50:29

It seems if you click somewhere, and someone/thing is next to you, or gets in your way (even in an open map) you just stop, until the thing moves. On main server, you move around the object/person whenever this happens. Could you implement the same thing here?

This is indeed the case as no actor checking occurs while navigating at this point.  At least not until it finds an actor in the next square in sequence.

( from: http://qelserv.quadronyx.org/forums/index.php?topic=15.msg318#msg318 )

If you attempt to flee during combat preparation and actually succeed, the battle still takes place.

Creatures move in a very stupid way and inevitably end up stuck and/or blocking paths etc. Whilst paths will be fixed in maps by making them wider, creatures should probably not stop on any narrow area anyway and should, in general, “think” about where they’re going

At some point the client should be “cleaned” of all the truly ridiculous RAW_TEXT scraping code and changed to support simple server messages. These will eventually interfere with “normal” functionality.

Implement a trading system allowing players, NPCs and Creatures to trade items (client has existing trading window).

Trading should support transferring items to/from storage as well as inventory.

Dropping an inventory item on to an equipped item, should swap with that item. Undecided as to whether it should swap with what you drop it on, or the equipment of the same type you have equipped (ie if you drop a sword onto a shield, should the new sword swap for the shield or your existing equipped weapon).

At the moment, all actors can see all other actors on the map they are on. Instead they should have a limited range of vision.

If you attack someone in a PK area, and whilst in the PENDING fight state they leave the PK area, server lag occurs as the server tries to initiate combat.

If a player takes multiple of a non-stackable item, in one go, from a bag where they are stacked, their carry capacity gets screwed. ATM this is only causing an issue with #airdrop but could potentially cause other issues if we choose to allow bags to be non-stack exempt.

When equipping an item that is stackable (and you have more than one), it equips ALL of that item, not just one.

The channel system needs to be checked to confirm everything is working properly (active channel might not be working correctly for example).

Change “Getaway thing” to “Sand bomb” and make it so when you flee off opponents they can’t move/attack for 2 seconds, and when you use the “Sand bomb” they can’t move/attack for 5 seconds.

Sand bomb can have 60 sec cooldown (to start with, it may come down a little)

A party system where you can “party up” with people and go on missions together. Perhaps an NPC interface that allows you to select the people from those around you for your party or something.

NOTE: Different to guilds ;)

Once we have parties ( FS#45 ), we will be able to have party drops.

4 ways this can be done:

1. You drop many bags around with % of loot, first in best dressed.
2. You drop 1 bag but when a player takes items, it gives a % to each in the party instead of all to the one.
3. You don’t “drop” at all, just allocate items straight to the party members.
4. Drop 1 bag. But once it’s picked up, all other party members automatically get a bag under their feet, opened, containing their % of the spoils.

Whilst the most complicated, the 4th option sounds the most attractive and flexible from a player perspective.

Despite the changes for  FS#47  the CLIENT doesn’t sent the right number of items to pick up as it expects items in bags to be stacked.

Since stacking in the bag is reasonable, and because it’ll save a client modification at this stage, bags should be made to support stacking of non-stackable items.

Equipment should support being degraded. At the moment we have break percentages but once these kick in the item is simply lost. We should support the item transitioning to another state, optionally allowing for a modification of it’s stats.