OP 02 November, 2024 - 11:16 AM
(This post was last modified: 02 November, 2024 - 11:18 AM by EkinKoc. Edited 1 time in total.)
I would like to propose an enhancement to the Leechometer Bot's functionality to improve the management of giveaway threads. Currently, after a winner is selected by clicking the "Random Winner" button, threads can remain open, allowing some members to wait for staff to close the thread and farm likes till that time, and promote their services longer.
To address this issue, I suggest implementing an automatic thread closure feature that activates immediately after the "Random Winner" button is pressed. In simple language, the thread will be closed after pressing the "Random Winner" Button. This would streamline the process, ensuring that threads are promptly closed once a winner is determined, thus preventing any potential misuse by users and enhancing the overall integrity of the giveaway system.
Implementing this feature would not only stop those members which are farming likes and promoting their services unfairly due to open-threads but also help staff members distinguish which giveaways are ended and which are not, so that they could put closed threads in the "Ended-Giveaways" Section.
Thank you for considering this suggestion!
To address this issue, I suggest implementing an automatic thread closure feature that activates immediately after the "Random Winner" button is pressed. In simple language, the thread will be closed after pressing the "Random Winner" Button. This would streamline the process, ensuring that threads are promptly closed once a winner is determined, thus preventing any potential misuse by users and enhancing the overall integrity of the giveaway system.
Implementing this feature would not only stop those members which are farming likes and promoting their services unfairly due to open-threads but also help staff members distinguish which giveaways are ended and which are not, so that they could put closed threads in the "Ended-Giveaways" Section.
Thank you for considering this suggestion!
