The bots will get love and attention after the next big update. I just can't give them priority at the moment. First implementation which might actually be in the next version is trusting bot keyholders to give them more control.

I have just tested the ticker generating page and it worked fine on my Mac in Chrome, and Safari. It worked fine in Chrome on my Android device too.

I've no plans on adding the option to take photos of combinations. I've covered the reasons why several times. If you're using a 4 digit combination then there's lots of advice and tips here and on Discord that will help you forget, the best advice is to use an 8 digit combination in the app and come up with a pattern to extract a 4 digit combination from it i.e. the 1st, 3rd, 5th, and 7th digit, or 2nd, 8th, 4th, and then 6th etc. whatever pattern you choose be sure to write down the pattern (not the digits) so that you know what digits from the 8 digit combination you used once you're ready to unlock.

It's hard to say what happened from that post alone but bots do add time throughout the lock and also unlock. If they unlocked you then you should see an update in that same list that says unlocked.

It could also be related to the issue where the fixed lock expired when you opened the app before the last update had time to trigger and increase it.

I've created a simple python script which generates random variable lock card set ups, saves them to a datafile and gives you the option to search that data for locks that meet the desired duration you're after. To get the best results it's good to generate a good number of locks, but they don't need to be generated all in one go (regularly with small numbers is best). Generating a 1,000 locks in one go can take a little while.

The examples.py file that comes with the script shows how to call the different function/commands that are available. And here's a simple example without all of the comments that will generate 10 locks, and then search those 10 locks for one that lasts between 4 and 10 hours. That's a duration of 7 hours but with a variation of 3 hours either side. You may not get any matches the first time you run it, but each time you generate new locks you're adding to the existing locks that you created previously which is improving the chance of finding that perfect lock.

import ChastiKey as ck

chastikey = ck.ChastiKey()
chastikey.GenerateLocks(number_of_locks=10)
chastikey.SearchLocks(regularity=1, duration=7, variation=3, number_of_locks=1)

This was something I created while travelling when I couldn't really work on the main ChastiKey app.

https://github.com/KevinCrossDCL/ChastiKey/tree/master/python/ChastiKey

I let you pick a card right away and not have to wait out the interval so that you can see what it was about right away. And see the card picking side right away. If you installed the app for the first time and created a lock and had to come back tomorrow to have your first go, you would most likely delete it and move on to something else.

The app uses the minimum number of reds as the minimum time that needs to have passed before finding a green so if you want to do a minimum of 3 days on a lock where you pick daily then make sure the minimum reds is 3. Don't also set the maximum reds as 3 because then that treats the minimum reds/time needed to pass as 1 day.

This is explained in the help files.

This will also change in a future version because some want the rule seperated from the reds in to a new option, but for now that's how you do it

There's one thing having an option to start a lock without greens but having it default to this definitely isn't something that would or should be introduced.

Too many people will miss the option and will end up in locks which take forever to end