# Potential bug in Game Shell's keypad

**URL:** <https://forum.clockworkpi.com/t/potential-bug-in-game-shells-keypad/401>\
**Category:** GameShell\
**Tags:** bug\
**Created:** [June 29, 2018, 7:53pm UTC](https://forum.clockworkpi.com/t/potential-bug-in-game-shells-keypad/401 "2018-06-29T19:53:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![aewens](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/aewens/32/39_2.png) [@aewens](https://forum.clockworkpi.com/u/aewens)\
**Post date:** [June 29, 2018, 7:53pm UTC](https://forum.clockworkpi.com/t/potential-bug-in-game-shells-keypad/401/1 "2018-06-29T19:53:51Z")

</div>

@yong, @hal

While speaking with @Rinzler_Shi in the Discord chat, he noticed a delay in the response for the keypad’s buttons. Upon reviewing the code for the keypad, @Godzil noticed that in the loop, it uses `delay(1000)`, which is in milliseconds (i.e. the Game Shell is only accepting on button press every second), that would be the source of the lag.

An issue for it has been opened in on the GitHub page:

> <https://github.com/clockworkpi/Keypad/issues/1>

---

<div class="post-metadata">

**Author:** ![1n9i9c7om](https://yyz1.discourse-cdn.com/flex029/user_avatar/forum.clockworkpi.com/1n9i9c7om/32/1545_2.png) [@1n9i9c7om](https://forum.clockworkpi.com/u/1n9i9c7om)\
**Post date:** [February 4, 2019, 7:44pm UTC](https://forum.clockworkpi.com/t/potential-bug-in-game-shells-keypad/401/2 "2019-02-04T19:44:59Z")

</div>

Does modifying the delay fix the issue? I just got my GameShell and put everything together, but that lag is really annoying imo.

Edit: I’ve simply tested uploading a modified firmware to the keypad. I’m going to test it later because I’m still busy setting everything up. Would be awesome if it works 🙂