|
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.
|
|
90 | QELBot | B.Admin | Feature Request | Low | Add total item gc value to "status" output | New | |
2010-11-15 |
Task Description
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)
|
|
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.
|
|
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).
|
|
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.
|
|
96 | QELBot | WebAdmin | Feature Request | Low | Add force kill to WebAdmin | New | |
2010-12-15 |
Task Description
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 ).
|
|
85 | QELBot | Bot | Feature Request | Low | Add bot access lists | New | |
2010-11-15 |
Task Description
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).
|
|
92 | QELBot | B.Adverts | Feature Request | Low | Add ability for bots to be on the "greypal" search serv... | Assigned | |
2013-06-01 |
Task Description
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
|
|
19 | QELServ | Server | Bug Report | Low | Actors should have a limited sight range | Assigned | |
2010-01-09 |
Task Description
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.
|
|
115 | RatSlap | Uncategorised | Planned Feature | Low | Ability to save/load profiles | New | |
2020-02-28 |
Task Description
Would be nice to be able to save and load profiles.
|
|
4 | QELServ | S.Combat | Bug Report | Low | A successful flee during combat prep doesn't flee | New | |
2009-09-21 |
Task Description
( 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.
|
|
20 | QELServ | S.Combat | Bug Report | Medium | Target leaves PK causes server lag | Assigned | |
2010-01-09 |
Task Description
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.
|
|
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).
|
|
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)
|
|
116 | RatSlap | Uncategorised | Planned Feature | Medium | Modes should have simpler names such as A, B, C | New | |
2020-02-28 |
Task Description
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.
|
|
51 | QELServ | S.AI | Bug Report | Medium | Creature spawning intelligent placement | New | |
2010-01-22 |
Task Description
Creature’s can currently spawn anywhere within their given rectangle. This includes levels that aren’t necessarily possible to get to or from (say for example, a table). This means the creatures are currently taking up a useless slot, limiting the number of creatures people can fight, and using up unnecessary thinks, trying to find a way out.
Placement should be more intelligent, perhaps opting for something within a few height levels of norm, or of the spawns center.
|
|
50 | QELServ | Server | Feature Request | Medium | Add ability for equipment to become "degraded" | New | |
2010-01-22 |
Task Description
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.
|
|
107 | RatSlap | Uncategorised | Planned Feature | High | Reset to defaults/factory reset option | Assigned | |
2020-02-28 |
Task Description
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.
|
|
93 | QELBot | Bot | Bug Report | High | Bot crash during "inv" | Assigned | |
2010-11-15 |
Task Description
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 '='")
|
|
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?
|
|
95 | QELBot | B.Database | Bug Report | Critical | Crash/Reconnect loop on empty Inventory | Assigned | |
2010-12-15 |
Task Description
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.
|