|
77 | QELBot | WebAdmin | Planned Feature | Low | WebAdmin to support viewing Messages | New | |
2010-11-15 |
Task Description
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 ).
|
|
75 | QELBot | WebAdmin | Planned Feature | Low | WebAdmin to support configuring responses | New | |
2010-11-15 |
Task Description
Trac Ticket #40 - Originally reported by: Krayon
WebAdmin should support configuring of responses.
|
|
67 | QELBot | B.Database | Planned Feature | Low | Move custom messages to the database | New | |
2010-11-15 |
Task Description
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.
|
|
73 | QELBot | B.Messaging | Planned Feature | Low | Bot to support logging of messages, such as guild chan ... | New | |
2010-11-15 |
Task Description
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.
|
|
72 | QELBot | B.Other | Planned Feature | Low | Bot to support item abbreviations table | New | |
2010-11-15 |
Task Description
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.
|
|
9 | QELServ | S.Trading | Planned Feature | Low | Trading system | Assigned | |
2010-02-02 |
Task Description
Implement a trading system allowing players, NPCs and Creatures to trade items (client has existing trading window).
|
|
63 | QELServ | Server | Planned Feature | Low | Channels ACL | New | |
2010-01-28 |
Task Description
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.
|
|
32 | QELServ | S.Combat | Planned Feature | Medium | Sand Bomb and resulting opponent behaviour | Assigned | |
2010-01-24 |
Task Description
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)
|
|
61 | QELServ | S.Admin | Planned Feature | Low | Global item purge/list/modify | New | |
2010-01-22 |
Task Description
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.
|
|
60 | QELServ | S.Admin | Planned Feature | Low | Admin access player storage | New | |
2010-01-22 |
Task Description
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.
|
|
59 | QELServ | S.Admin | Planned Feature | Low | Admin access player inventory | New | |
2010-01-22 |
Task Description
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.
|
|
54 | QELServ | S.Admin | Planned Feature | High | Add support for banning | New | |
2010-01-22 |
Task Description
As we get players, we will get trouble makers, that much is already clear. We need the ability to ban users for a configurable amount of time, as well as preset amounts. These SHOULDN’T effect the forum bans however a ban on the forum SHOULD be a ban in game also (I think).
Something like this might do:
#ban PLAYERNAME [[[Y:]D:]H:]M REASON
eg.
#ban testuser 1:4:6:3 Because you're a tool
This would ban ‘testuser’ for 1 year, 4 days, 6 hours and 3 minutes because he’s a tool. He would be informed of such when trying to login.
Other examples:
#ban testuser 5 Come back in 5 minutes when you've learned to behave
#ban testuser 7:0 You're gone for 1 week buddy!
Should we support banning per player or per forum account (given that 1 forum account can have multiple players)?
Should we have pre-sets like: #ban7 for 7 days, #banwarn for 1 hour, #banladen for life?
|
|
58 | QELServ | Server | Planned Feature | Low | Add lastseen ability | New | |
2010-01-22 |
Task Description
Add the ability to see when the last time a player was on. This would be a useful feature for players I would think.
|
|
56 | QELServ | Server | Planned Feature | Low | Add player list command for players | New | |
2010-01-22 |
Task Description
It’d be good for players to be able to get a list of who’s online. Perhaps if we require a PATTERN when more than say 20 are on, that would hopefully stop too many people abusing it.
Perhaps the easiest way would be to stop once you get to 20. So:
#online
Would list ALL the players if there were ⇐ 20 online at that point, however if there were thousands, it’d only return the first 20 (in order of Actor ID I guess).
|
|
53 | QELServ | Server | Planned Feature | Medium | Storage | New | |
2010-01-22 |
Task Description
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).
|
|
46 | QELServ | Server | Planned Feature | Low | Party drops | New | |
2010-01-20 |
Task Description
Once we have parties ( FS#45 ), we will be able to have party drops.
4 ways this can be done:
You drop many bags around with % of loot, first in best dressed.
You drop 1 bag but when a player takes items, it gives a % to each in the party instead of all to the one.
You don’t “drop” at all, just allocate items straight to the party members.
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.
|
|
45 | QELServ | Server | Planned Feature | Low | Implement party system | New | |
2010-01-20 |
Task Description
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 ;)
|
|
31 | QELServ | Server | Planned Feature | Low | Finish channel system | New | |
2009-12-19 |
Task Description
The channel system needs to be checked to confirm everything is working properly (active channel might not be working correctly for example).
|
|
17 | QELServ | Server | Planned Feature | Very Low | Equipment swap | New | |
2009-09-24 |
Task Description
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).
|
|
11 | QELServ | S.Trading | Planned Feature | Low | Add support for storage trading | New | |
2009-09-21 |
Task Description
Trading should support transferring items to/from storage as well as inventory.
|
|
1 | QELServ | Uncategorised | Planned Feature | Very Low | Make QELServ BESTEST EVER!111 | New | |
2009-09-20 |
Task Description
QELServ needs to be the BEST ... just BEST ... ever!
|