All Projects

Summary says it all :)

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

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

The ability to purge, modify and list (who has and where) items would be advantageous.

It would allow for the easy removal or substitution of an item, on a global scale. Ideally it should handle things like subing a sword for a piece of fruit - which should remove sword, give fruit and stack with existing fruit if req’d.

To be able to list all players who are currently in possession of a given sword, and how many etc would be part of this presumably.

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

Trac Ticket #49 - Originally reported by: Krayon

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

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

The mode names should be simpler than “F3”, “F4” and “F5”. They were only named
this way as that was the hex code for the mode, hardly user friendly.

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.

We should have a musl build for a lean standalone binary version.

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.

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.

At present, the original configuration is lost once you modify the modes of the
mouse. An option to return the mouse to it’s factory defaults would be
advantageous.

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)

We need storage fully functioning. The design for categories isn’t decided as yet. User defined perhaps? The problem with custom is the tediousness of defining each item’s category (unless you have it manual category selection but that’d suck).

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

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

WebAdmin should support the viewing of transaction history.