Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

I disabled and enabled all my extensions (and had control the entire time) and then I tried a few other things to narrow down the issue... [I'm a professional game tester by trade. Worked for Activision, etc.]

It appears when I click out of the game, perhaps to scroll down and read the instructions, view the screenshots, open the game info, highlight words, etc, and THEN try and click back into the game, the keyboard doesn't follow the mouse focus back into the game. So pressing the arrow keys scrolls the browser window and pressing Tab switches the focus out of the game to the first few links on the page, according to tab-order.

It's not an extension issue at all, it's a focus issue. I'll try it in Edge and Brave now... Oh, it appears they have the same exact issue.

BUG REPORT:

Description - Game Input fails after game loses focus for the first time.

Severity - High [Game breaking, requiring a page refresh to fix]

STEPS TO REPRODUCE:

  1. Open the page on itch.io.
  2. Click "Run Game".
  3. Notice the game starts as normal with the intro/attract mode animation.
  4. Scroll down and click on a screenshot or choose the "More information" link.
  5. Close any open images and scroll back up to the game, clicking the game area to attempt to make it active.
  6. Notice that pressing keys such as [Enter], [arrows], or [TAB] no longer work to skip animations, move characters, or open menus.
  7. Notice the game can no longer be played at all until the page is refreshed and "Run Game" is chosen again.
(+1)

Thanks for the report. I was able to reproduce the bug. I have an idea what may be causing it, but I'm not sure it will be easy to fix. I may try to address it someday, but it's not a priority for an immediate fix. While annoying, this bug is easy to work around. I've added a warning to the game's description. The game is also available here and here, and these versions are not affected by this bug (AFAIK).

(+1)

The issue should be fixed now.