-
Notifications
You must be signed in to change notification settings - Fork 104
Autocop not starting and displaying "running in [incorrect time] after drop" #134
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
Comments
Hello, I encounter the same problem, too, is there any fix to add to the code? |
Mine worked fine last drop. Have you tried recreating it with current in-stock items? Do you have your configuration set to continue refreshing until the product is found? Just some troubleshooting to start with :) |
Thanks for the reply mapooo,
The configuration is ok, refreshing until the product is found.
But at the sum that exceeds the 11 exit of the drop, I add 1 day 1 hour and
1 min and restart the countdown.
I have to run RUN ALL by hand.
Il giorno lun 3 set 2018 alle ore 16:02 mapooo <[email protected]>
ha scritto:
… Mine worked fine last drop. Have you tried recreating it with current
in-stock items? Do you have your configuration set to continue refreshing
until the product is found? Just some troubleshooting to start with :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#134 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ao4nbBFWrhi_0jE5hdQ8KHc1ginsgdfqks5uXTaGgaJpZM4UfBNW>
.
|
Does it still do this if you try it right now? |
I have reinstalled it locally to optimize autofill of the supreme page, if you have modified something at the file level tell me if I have to reinstall the plug in of gogle chrome? |
I haven't had to do anything for it to work. You haven't answered my query. If you try using the timer now on any in stock item is it working? |
Hello Mapooo, for the products already present in stock the timer starts
correctly, doing everything you ask.
The problem occurs at the time of the new drop, always start at 11 but if
the drop still has not come out at 11, the timer loses the refresh by
adding 1g-1h-1m-1s going negative
Il giorno mar 4 set 2018 alle ore 01:19 mapooo <[email protected]>
ha scritto:
… I haven't had to do anything for it to work. You haven't answered my
query. If you try using the timer now on any in stock item is it working?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#134 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ao4nbIy5QK9IVCTaIy7OAH7oUn-lIHPPks5uXbjmgaJpZM4UfBNW>
.
|
Hi,
I've been having this problem for two weeks in a row now. Autocop doesn't start at the drop time (I set it to 11:00:01) unless manually run (which isn't an option for me). After 11:00 it says autocop starting in -the correct amount of time +1 day. This seems like a fairly simple bug but it caused me to lose out on a £65 sale earlier and it'd be great if you could reply / give support. Thanks if you can help!
The text was updated successfully, but these errors were encountered: