NATTSKIFTNATTSKIFTGAMES

Hunch support

The fastest way to get help is email. It goes straight to the person who made the game.

Email support

Replies usually take a day or two, not an hour - one person answers these. Write to hunch@pacificfrontdesk.com and include your device, your iOS version, and the puzzle number shown as DAY next to HUNCH at the top of the board.

Common questions

Streaks are kept on your device. Deleting the app, resetting the phone, or moving to a new one without a backup clears it, and it cannot be restored - there is no account and no server holding a copy. Signing in to Game Center keeps your longest streak on the leaderboard even when the local one resets.

Open the store from the bag icon at the top of the board and tap Restore purchase. The unlock is tied to your Apple account, so sign in with the same one you bought it with.

Refunds are handled by Apple, not by the studio. Go to reportaproblem.apple.com and sign in with your Apple account.

Leaderboards need Game Center. Open the Settings app, tap Game Center, and check that you are signed in. Scores can take a minute to appear. The puzzle itself works fully offline and never needs a connection.

Open Settings in the app and turn on Patterns as well as colour. Every colour then gets its own fill, so the board can be read without relying on hue.

Yes, with the full game - it unlocks every puzzle back to the first. Archive puzzles are recorded separately and never affect your streak.

Email hunch@pacificfrontdesk.com with the subject 'Hunch bug'. Say what you did, what you expected, and what happened instead, and include the DAY number from the top of the board. A screenshot or screen recording doubles the odds of a fast fix.

How to write a bug report that gets fixed

Three things make a bug fixable: what you did, what you expected, and what happened instead. Write those three lines and you are ahead of most professional QA.

Add your device model and iOS version — Settings, General, About — and a screenshot or screen recording if the bug is visible. A recording of a crash is worth five paragraphs describing one.

One report per email, please. Two bugs in one email means the second one gets lost, and it deserves better.