There is indeed a spider hidden under the user interface at the bottom. Due to the changed UI some other spider got moved in 0.10 too, but I've overlooked this one. It's fixed internally now. In general 64 pixels from the top and 128 pixels from the bottom (assuming the internally used 1920x1080 resolution) are reserved for the user interface and should never have a clickable placed inside that area.
I've just tested this. I've ripped out the KFC-minigame code into a standalone Ren'Py-project, copied over the necessary resources, added a precise timer to see how much time is really given to the player to beat the highscore.
The results are boring and exactly what I would expect:
- fast PC from ~2013 (i7 2600K, overclocked to 4,2Ghz) = 30,22 seconds
- slow PC from ~2007 (Athlon 64 X2 4200+, underclocked to slow down more) = 30,40 seconds
Unless there is a flaw in Ren'Pys screen timer code, the game cannot run 'to fast'. It can only run slower on slow machines effectively giving the player slightly more time. In my tests this was between 150-200 ms. This is actually good to somewhat compensate for slow machines. If I'd use a precise timer like
You must be registered to see the links
to measure exactly 30 seconds the game would be harder on a slower machine.
The minigame uses a
You must be registered to see the links
that ticks with a 200 ms interval. Each tick a function is called. It adds 0.2 to a counter until the
30 second time-limit is reached. That counter is used to update the time-bar at the top too.
The KFC-minigame is ~300 lines of code, this is the relevant part, it's very simple:
Python:
# inside screen
timer 0.2 repeat True action Function(pc_kfc_update)
def pc_kfc_update():
store.pc_kfc_second_elapsed += 0.2
if store.pc_kfc_second_elapsed >= store.pc_kfc_timeout:
# 30 seconds have passed
pc_kfc_end()
In other words, everything works as intended. If that highscore is really to hard I will lower it slightly, but it's designed to be very challenging. On that potato 2007 test-PC it took me 5 tries to beat 60 with 64, not because the performance was bad, but I was using a bad cheap mouse on a carpet. Therefore I'm not convinced yet and 60 seems like a good balance, not to easy, not to hard. Give me a good reason to 'nerf' this.
You must be registered to see the links
is the standalone KFC-minigame. It will show the real time after the time-limit for comparison.
If that runs in under 30 seconds there is a problem, slower is fine.