Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Auto Shutdown Option #630

Open
braandoned opened this issue Nov 28, 2024 · 3 comments
Open

Feature Request: Auto Shutdown Option #630

braandoned opened this issue Nov 28, 2024 · 3 comments
Labels
Enhancement New feature or request Feedback Wanted Extra feedback is needed

Comments

@braandoned
Copy link

I’d like to request a feature for the Twitch Drops Miner. Could you add a toggle in the settings for an auto shutdown option? The idea is to close or shut down the app automatically if the console outputs:

No active campaigns to mine drops for. Waiting for an active campaign...

This would help conserve resources, especially since I have the app set to autostart with my PC. Currently, the app can remain idle for hours when there’s nothing to mine, which isn’t ideal.

To avoid immediate shutdown upon opening the app when there’s no campaign, a timeout feature would be helpful. For example, an option to auto shutdown after 10 minutes of inactivity would strike a good balance.

Thank you for considering this!

@DevilXD DevilXD added the Enhancement New feature or request label Nov 29, 2024
@DevilXD
Copy link
Owner

DevilXD commented Nov 29, 2024

Hello,

Currently, the app can remain idle for hours when there’s nothing to mine, which isn’t ideal.

Why not ideal though? There's nothing happening in the idle state, besides the maintenance task counting down on it's timer. CPU usage should remain very close to none. And memory usage is low enough, that it doesn't matter for definite most of today's PCs and laptops.

To avoid immediate shutdown upon opening the app when there’s no campaign, a timeout feature would be helpful. For example, an option to auto shutdown after 10 minutes of inactivity would strike a good balance.

This makes no sense, as it'd always activate after 10 minutes, because the maintenance task is the only thing governing when the miner will attempt mining again, and it's triggered once every hour. This is because Twitch has disabled the "UPCOMING" campaigns from showing up with their status, so the miner can no longer predict campaign start times beforehand, so reloads are almost always close to one hour apart.

Overall, I see not much need for a feature like this. I can see an argument for the 100-200 MB of memory the miner takes when running, and an under-average machine having 1-2 GB of memory, and that being a problem, but even then, CPU usage is almost none during idle state, and the extra memory usage doesn't feel like would be worth my time implementing all the logic needed for this.

Even so, I'm leaving this open for discussion, in case other people would somehow find this a feature they'd find a use for.

@DevilXD DevilXD added the Feedback Wanted Extra feedback is needed label Nov 29, 2024
@Minty-stack
Copy link

Just my two cents of feedback, but I see no issue with the miner running constantly. On my PC it runs for weeks at a time - basically any time the PC is on, and I launch it right after rebooting for updates and such. The memory/resource footprint is so small it's unnoticeable to me, so even if such option was implemented I'd never use it personally.

@issue-reporter
Copy link

I don't see the need for this kind of feature.

The entire point behind this program (for me) is to set it and forget it. If I have to keep tabs on drops and constantly run it to mine things, it defeats the entire purpose. Closing the program manually if you're resource starved isn't a big deal. Time and effort put elsewhere would be more valuable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request Feedback Wanted Extra feedback is needed
Projects
None yet
Development

No branches or pull requests

4 participants