|
118 | RatSlap | Uncategorised | Bug Report | Low | Button5 cannot be assigned to G5 | New | |
2020-02-28 |
Task Description
From GitHub Issue #9 by adrfantini:
I have a very weird behaviour here. After having modified many buttons to
suit my needs, I have the following problem.
I cannot assign many software mouse Buttons to many hardware buttons.
Assigning keys seems to always work tho.
Say I am in this situation:
...
sudo ratslap --p F3
Left Click (But1): Button1
Right Click (But2): Button2
Middle Click (But3): Button3
G4:
G5:
G6:
G7:
G8: ModeSwitch
G9: DPICycle
...
Now let's try to modify it with:
sudo ratslap --modify F3 --G4 Button4
Result:
sudo ratslap --p F3
Left Click (But1): Button1
Right Click (But2): Button2
Middle Click (But3): Button3
G4:
G5:
G6:
G7:
G8: ModeSwitch
G9: DPICycle
Nothing! Let's try assigning keys instead:
sudo ratslap --modify F3 --G4 LeftAlt+K
Left Click (But1): Button1
Right Click (But2): Button2
Middle Click (But3): Button3
G4: LeftAlt + K
G5:
G6:
G7:
G8: ModeSwitch
G9: DPICycle
Works...
In short, I can seem to bind mouse Buttons anymore!
However, some, like sudo ratslap --modify F3 --G7 Button9 work, while others,
like sudo ratslap --modify F3 --G7 Button5 do not.
|
|
119 | RatSlap | Uncategorised | Bug Report | Low | Unrecognised keys/buttons fail silently | New | |
2020-02-28 |
Task Description
QB#118 shows that unrecognised parameters (such as “button5”) fail silently, assigning 000000h instead of reporting an error.
|
|
127 | RatSlap | Uncategorised | Planned Feature | Low | musl build for lean standalone | Assigned | |
2020-02-28 |
Task Description
We should have a musl build for a lean standalone binary version.
|
|
74 | QELBot | WebAdmin | Bug Report | Low | WebAdmin to support discount configuration | New | |
2010-11-15 |
Task Description
Trac Ticket #39 - Originally reported by: Krayon
The WebAdmin interface should support configuring discounts for players and guilds.
|
|
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.
|
|
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 ).
|
|
78 | QELBot | WebAdmin | Planned Feature | Low | Improve WebAdmin field data validation | New | |
2010-11-15 |
Task Description
Trac Ticket #49 - Originally reported by: Krayon
WebAdmin fields should perform (better) data validation, such as alpha/alphanumeric/numeric etc.
|
|
80 | QELBot | WebAdmin | Feature Request | Low | Make bot able to determine if item is stackable | New | |
2010-11-15 |
Task Description
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.
|
|
86 | QELBot | WebAdmin | Planned Feature | Low | WebAdmin to keep access logs | New | |
2010-11-15 |
Task Description
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.
|
|
89 | QELBot | WebAdmin | Planned Feature | Low | WebAdmin to have current inventory list | Assigned | |
2010-11-15 |
Task Description
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”.
|
|
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 ).
|
|
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.
|
|
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.
|
|
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)
|
|
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.
|
|
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).
|
|
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.
|
|
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?
|
|
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.
|
|
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.
|