All Projects

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.

Currently, when the user issues a tell/ask command, the bot doesn’t parse out any punctuation IMMEDIATELY following the nick. This should be done for characters that are illegal for IRC nicks ( TODO: verify this list ).

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)

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.

QB#118 shows that unrecognised parameters (such as “button5”) fail silently,
assigning 000000h instead of reporting an error.

QELServ needs to be the BEST ... just BEST ... ever!

Summary says it all :)

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.

The built dist package is named “ratslap-0.2.0.tar.gz” regardless of architecture.

Would be nice to be able to save and load profiles.

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.

We should have a musl build for a lean standalone binary version.

Trac Ticket #39 - Originally reported by: Krayon

The WebAdmin interface should support configuring discounts for players and guilds.

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.

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

Trac Ticket #40 - Originally reported by: Krayon

WebAdmin should support configuring of responses.

Trac Ticket #41 - Originally reported by: Krayon

WebAdmin should support the viewing of transaction history.

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

Trac Ticket #49 - Originally reported by: Krayon

WebAdmin fields should perform (better) data validation, such as alpha/alphanumeric/numeric etc.

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.

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