'Take this L' Command #75
Labels
No labels
bug
config update
documentation
duplicate
enhancement
in dev
input needed
new feature
not in draft
refactor
waiting on docs update
wont-do
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Sirdog/EnduraBot#75
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Purpose
To quick give somebody the L command for punishment
Implementation
The command should by default give somebody the L role for 24hours and automatically remove it should they still have it 24 hours later. Should the role have already been removed then nothing should occur.
Whether it should notify them the L has been removed is up to you (the developer).
Preferably the command should allow the user to optionally change the length of L punishment using hours as the units
eg:
/takeL Fleff 48would punish Fleff for 48 hours with the L role.eg:
/takeL Fleffwould punish Fleff for 24 hours with the L role.I'm of the opinion that the person should be pinged whenever the command is ran but indifferent whether the user should be notified when it is auto removed.
Implementation (Extra)
It would be great if a user was in the working corner VC it auto-disconnected them so the mute and stream ban would apply when the command is given.
Why?
This is quicker to run than using the
/editrolecommand and would also introduce a system for automatically removing the role.The only barrier here is that, in order for automatic revocation of the role to work, I either need to start storing persistent data in a DB, or, the bot simply needs to not reboot for that period of time, otherwise it won't remember to remove the role.
The daily bible quote does not run into this issue because the time the quote is sent is predetermined on startup; it isn't looping a 24-hour period.
I am uncertain if I wish to start the process of storing persistent data for this command, which is mostly a QoL thing. Not that I don't love you Fleff 🥹
I'l think on it some more, because getting into persistent data storage would open other potential uses for EnduraBot (logging message deletion and edits, my beloved), but I've gotta weigh whether or not a feature I could make will be used.
Aside from automatic removal, everything else is entirely doable. Though the big selling point for this command, I assume, is EnduraBot doing the heavy lifting to remove it later.
Made significant progress on this. Just gotta iron out some edge-case handling and getting the automatic role revocation to work.
Feature in
devby #119 and will be pushed to the server inv2.4. @MrFleff