You can select a project from the “All Projects” drop down combo box in the top right corner. Displayed below are the tasks for ALL Quadronyx projects.

Advanced

Miscellaneous

Search in commentsSearch detailsSearch for all wordsTasks I watchTasks not blocking other tasksTasks blocking other tasksBlocker or nonblocker, selecting both filter options doesn't make sense.Has attachmentHide SubTasks

Admins need the ability to see (and modify) a player’s inventory. This would allow them to remove items, add items etc. They would most likely have to use a bag as a go between but that would be acceptable.

Admins need the ability to see (and modify) a player’s storage. This would allow them to remove items, add items etc. They would most likely have to use a bag as a go between but that would be acceptable.

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.

Channels should have support for simple ACL. They can have a “list” that will function as either a blacklist OR a whitelist.

First person to join get’s “op” status.

The channel has a BLANK list, defined as a BLACKLIST.

op can at any time add a name to the BLACKLIST. By doing so, that person cannot join the channel.

If the list is empty, op can add a name as a WHITELIST entry, thereby making the list a WHITELIST. From that moment on, ONLY whitelists are allowed to join and anyone (other than op) that is currently in the channel will be removed.

List can only be changed from WHITE to BLACK when it’s empty.

op can at any point change someone else to op. They swap effective positions so if the new op was on the WHITELIST then the old op is added and the new op removed (op doesn’t need to be WHITE).

Undecided behaviour:

In the event that the op leaves, one of these should happen:

the (WHITE/BLACK)LIST is cleared.

if WHITELIST, the first person in WHITELIST becomes op, otherwise list is cleared.

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

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

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.

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

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