|
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).
|
|
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).
|
|
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)
|
|
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 ;)
|
|
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.
|
|
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).
|
|
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?
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
110 | RatSlap | Uncategorised | Bug Report | Low | Document basic usage | Assigned | |
2016-11-08 |
Task Description
From https://github.com/krayon/ratslap/issues/2 :
https://github.com/jpotier wrote:
I may be tired, but I don't get how to set say key 1 to my button G4.
Actually, apart from calling
./ratslap -p f3-5
I don't understand how you actually set a modified mode. Should I edit the
source code and recompile?
https://github.com/thomasluquet wrote:
Same thing, for me, the documentation it is not really clear for me...
BTW, i try to make a draw of the mouse and the buttons, is it ok ? (i can
send you the .odg if you want)
|
|
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.
|
|
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.
|
|
112 | RatSlap | Uncategorised | Planned Feature | Low | Distribution package should contain arch | New | |
2020-02-28 |
Task Description
The built dist package is named “ratslap-0.2.0.tar.gz” regardless of architecture.
|
|
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.
|
|
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.
|
|
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.
|