Open Lk991 opened 11 months ago
Do you have some suggestions about how to reproduce the delay?
E.g.
I've heard about similar issue a while ago here: #2 but we could not figure out what caused it. I could rewrite the logic that calculates time left before sales start which could fix this.
I've updated the time calculation to be more accurate. Can you test if you're able to reproduce the bug?
Sure, I now just tried two different events where the sale begins in about an hour, one of them had the correct time countdown whilst the other was 30s delayed.
edit: tried the delayed event now again a couple minutes later and the timer wasnt delayed, so this problem doesnt always appear for some reason.
I attempted to reproduce this with many events and browsers, but everything seems to be working fine (a classic "works on my machine" situation).
I want to verify that you are running the updated version? the version number is displayed in the top right corner and it should be 4.2.0
.
Also the "Time until sales start..." message should appear slightly different in the new version:
If the issue persists, could you provide information about your browser, etc., so I can better attempt to reproduce the issue?
Just tried the bot on an event I wanted to go to, the waiting timer is working correctly, but it failed to reserve a ticket for me in time so I didnt get one. Started the bot about 20 sec before the sales began so somehow the bot isnt fast enough
Actually at the moment it's not about the timer nor how fast the bot is. Kide.app made just today new api changes to prevent ticket botting and thus made bots stop working.
I'm looking into what's different but at the moment probably no bot is working.
The bot is working again, latest version is 4.3.0. However, it's possible that Kide.app makes changes to their api again which could result to similar situation. Of course the sooner I'm notified of issues, the faster I'll be able to resolve them.
This isnt an issue report, but Im wondering if you could make it so that you can enter some sort of key word for what ticket to prioritize getting, theres a popular event releasing its ticket soon coming up and I know from last year that they have about 5 different tickets to choose from but you can only get one ticket. I remember the bot I used last year had a keyword input that you could use.
I don't own this repo, but your feature suggestion about adding a keyword input for prioritizing ticket types sounds really useful. Given the open-source nature of this project, maybe you could consider contributing this feature yourself? @AleksiVirkkala would likely appreciate the help. Alternatively, you might also want to look into forking the repository and adding this feature to your own project as it is open-source.
Im nowhere near good enough at coding to be able to do it myself sorry.
Also the bot has stopped working again it says all variants are sold out even tho they arent.
Kide.app keeps making small changes to their API that are pretty much impossible to take into account automatically. This means that it will take some time for me to get information that the bot is not working and then create fix. You can help by notifying me as soon as you notice the bot is not working.
@Lk991 I like your feature idea and I'd like to implement it. I'll definitely keep it in my mind but unfortunately at the moment there's enough work trying to fix the changes that Kide.app keeps makin.
Hi! Bot is not working atm. Can you try to fix it?
Sorry for taking this long. The bot should be up and running again
Just tried this on a event I wanted to go to, and when the tickets released on kide the bot still counted down from about 30s. However my friend who also used the bot, didnt have this problem.