The most popular open-source and self-hosted ticket management bot for Discord - a free alternative to the premium and white-label plans of other popular ticketing bots.
If member A transfers a ticket to B, the in-memory counter is not updated so the ticket contributes to the original creator's limits.
Although this could be a good idea to prevent spam/abuse, it wasn't intentional and is a problem because closing the ticket doesn't decrement the counter correctly, so the issue persists until the bot is restarted to re-sync with the database.
Expected Behavior
/transfer member: B should also transfer the limits to B
Is there an existing issue for this?
Current Behavior
If member A transfers a ticket to B, the in-memory counter is not updated so the ticket contributes to the original creator's limits. Although this could be a good idea to prevent spam/abuse, it wasn't intentional and is a problem because closing the ticket doesn't decrement the counter correctly, so the issue persists until the bot is restarted to re-sync with the database.
Expected Behavior
/transfer member: Bshould also transfer the limits to BSteps To Reproduce
No response
Environment
Anything else?
No response