Enhancement idea: More GamesPlayedWhileIdle (but still 32 at a time)
LeaLangley opened this issue · comments
Checklist
- I read and understood ASF's Contributing guidelines
- I also read Setting-up and FAQ, I don't need help, this is an enhancement idea
- My idea doesn't duplicate existing ASF functionality described on the wiki
- I believe that my idea falls into ASF's scope and should be offered as part of ASF built-in functionality
- My idea doesn't violate the Steam Subscriber Agreement
- My idea doesn't violate the Steam Online Conduct
- This is not ASF-ui suggestion
Enhancement purpose
The purpose of this enhancement is to extend the functionality of GamesPlayedWhileIdle
by allowing users to add a larger number of games to the list. However, the system will still adhere to the existing limit of farming hours for only 32 games at a time, facilitated by a filtering mechanism through FarmingOrders
. This enhancement seeks to grant users the ability to customize a broader selection of games without exceeding the inherent limit, providing a more tailored and versatile idle farming experience.
Solution
The proposed solution involves enhancing the GamesPlayedWhileIdle
feature to accept an expanded list of games. Despite this enlargement, the system will intelligently apply a filter through FarmingOrders
to ensure that only 32 games are actively farmed at any given time. This way, users can curate a more extensive collection of games for potential idle hours while still adhering to the technical constraints of the system.
Why currently available solutions are not sufficient?
The existing constraint, allowing only 32 games to be added to the list, is overly restrictive for users with broader interests in games.
Can you help us with this enhancement idea?
Somehow, I can test and offer feedback, but can't code
Additional info
Something else: Acknowledging the current limitation of farming only 32 games at a time in GamesPlayedWhileIdle
, despite the potential for a larger list, I've considered a toggle feature. This toggle would involve adding all games to the GamesPlayedWhileIdle
list on the account, utilizing the FarmingOrders
filter. It's important to note that, even with a larger list, only 32 games would be farmed at any given time, aligning with the existing constraint. While I recognize that this might be overwhelming for some accounts, it's a concept that has been on my mind for a while.
I have mixed feelings about this enhancement idea. On one hand I don't see a reason to reject this as it's withint ASF scope and the added functionality doesn't hurt anything or anybody. But on other hand I don't like customization of games played while idle OR any automation above what ASF offers already in regards to that option, as it's expected to be simple and used as-is, and if somebody needs custom logic he should write his own custom plugin instead.
Will give myself some time to think it further, but if we agree to that the only sensible way is to accept more games, and if > 32
, then sort them according to FarmingOrders
and display a warning for 99.9% of people running into this that amount of games is still limited to 32, and we'll use first 32 according to specified orders.
But I still don't like it and don't know if I want it into ASF, we'll see.
Hey, thank you very much for hearing me out.
The idea has been on my mind for some time. I've also looked into ASF plugin coding or similar. I don't want to go too much into my private stuff, but my ADHD makes it very difficult to learn at times, and I never could figure it out.
In case it gets rejected, and if it's not too much of a deal, maybe some more experienced plugin dev could help me out? Just giving me some bare-bones code that I could learn from, how it would work, and lead me in the right direction.
On one hand I don't see a reason to reject this as it's withint ASF scope and the added functionality doesn't hurt anything or anybody.
I don't agree. GamesPlayedWhileIdle always were kinda out of scope of ASF, and were added only because it was easy to do. And this suggestion will require complex logic, that will also introduce additional burden for support, and don't have anything that will improve main ASF functionality - that is, farming cards. I would say PR like this can be taken into consideration, but don't waste your time to implement it yourself.
In case it gets rejected, and if it's not too much of a deal, maybe some more experienced plugin dev could help me out? Just giving me some bare-bones code that I could learn from, how it would work, and lead me in the right direction.
ASF repo already includes plugin example, and there is also https://github.com/JustArchiNET/ASF-PluginTemplate to make start easier. Apart from this you can as well look at my github profile - I have many open-source ASF plugins there, you can use them as examples too. If you have some questions about plugin development - I recommend joining ASF discord, people there are always ready to help.
Yeah, on a second thought, this is not ASF's purpose. We already allow plugins and other tools to implement their own logic in regards to what ASF should play, and we make it easy since they don't need to implement low-level logic themselves. It's entirely out of the scope to add additional complex logic to games played while idle, which is an extra feature for easily setting some static amount of games as hours boosting while ASF has nothing to do - there is no intention here to extend it beyond its basic functionality, as that's not what ASF was built for.
I recommend custom plugin where you can provide your own games on whatever rules you want. For some unknown to me reason, everybody asks for hours boosting using complex rules, yet nobody wants to make a plugin for them.