[Suggestion] Check first badge page before CheckOccupationStatus()
brunoherrera 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
- This is not a duplicate of an existing issue
- 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
Since ASF can't run while other games/software from steam is/are running, you will need to close such games/software to be able to check the "first badge page", which makes it so if you don't have any steam trading cards to farm, you closed all of that pointlessly.
Solution
make the "Checking first badge page..." earlier, and only after you check first badge page do the rest of the steps to either pause because steam games/apps are running etc etc
Why currently available solutions are not sufficient?
no solution, becasue the steps are in the current order, you must close everything for then to be dissapointed and annoyed that you closed everything with no purpose because there was nothing to farm anyways
Can you help us with this enhancement idea?
No, I don't have time, skills or willings for any of that
Additional info
No response
ASF starts its cards farming module when it did everything before to ensure that doing so makes any sense at all. If the account is occupied, then it doesn't make sense to start farming, as it'd result in the module shutting down soon enough without making use of what it discovered.
I don't see any use-case that would vouch for your scenario. If you're currently playing a game, then it doesn't matter whether you have 0 or 10 games left to farm, since that doesn't affect your willingness to play the game, and if you're not currently playing a game, then you shouldn't have it launched at all, since if you want some empty irrelevant hours recorded then ASF already has mechanisms for that such as GamesPlayedWhileIdle.
What exactly is your scenario? Did I miss anything?
Did I miss anything?
it seems you didn't read fully, the scenario is, I don't think about farming every single time immediately after activating or aquiring a game or app, so days or weeks might pass before I want to know if they actually have trading cards drops;
to check we have 2 options,
- manually go to the profile on steam and check the badge page AND THEN run ASF after closing everything (if I do have drops remaining),
- or I can save a few clicks and open ASF from start menu pin.
But, the problem is ASF do the "checking first badge page" after CheckOccupationStatus(), which makes you so you must close everything regardless of if you actually have trading cards to farm or not
If you do have trading cards to farm, great, but if you don't you closed everything pointlessly, which is f# annoying
It seems you didn't read fully, I asked why the number of card drops would affect you closing currently played game. The expectation is to run ASF 24/7, since it doesn't occupy the account if there isn't anything to drop, and you can always launch a game whether or not it's farming, as ASF will patiently wait for you to finish before it'll check again if it has something to do.
You're asking me to degrade program's performance for your own use case, so either you have a reason for that (valid use case I can recognize), or it's not going to happen, simple as that. Right now you brought upon yourself some new irrational condition which annoys you, so I'm asking what's the reason for that.
ASF starts its cards farming module when it did everything before to ensure that doing so makes any sense at all. If the account is occupied, then it doesn't make sense to start farming,
it doesn't make sense to check first badge page AFTER CheckOccupationStatus()
it doesn't make sense to check first badge page AFTER CheckOccupationStatus()
Of course it does, we're avoiding extreme network overhead if we can determine that checking first page makes no sense at all, since the account is occupied and we can't farm anything at all anyway, regardless of whether we have or don't have anything to farm.
I'm not here to argue and prove you how existing program functionality makes sense though - you're asking me for a very specific downgrade of program's performance, do you have a reason for that or no?
we're avoiding extreme network overhead
was it that hard to start from there?
we're avoiding extreme network overhead
was it that hard to start from there?