What’s on your mind?

AI-generated answers may be inaccurate

Bible Puzzle

  • Web Development
  • Vue
  • TypeScript
  • Puzzle game
  • Collaborative project

Bible Puzzle was a short trial Jin Shisan and I made a week before the Oldtown Puzzle event. Jin Shisan wrote the story and worked on the puzzles; I handled programming and led the gameplay planning. We built it over one night and the following day. The trail runs through a newspaper, a web address, a prayer, a torn QR code, a letter, and a video.

An explorer named Aoyegande has disappeared, leaving notes about authority and wisdom. His rather grand-sounding name was a joke about our overnight development session.

A page from Bible Puzzle

The newspaper

The opening puzzle starts before the website. A hint in the newspaper, a reversed English weekday in its date, and the letters on a pictured typewriter point to a URL. Finding that address is how players enter the web portion of the game.

The newspaper used as the opening puzzle

The first page presents a prayer with an answer hidden in its text. Next comes a torn QR code. Players reconstruct and scan it to reach the explorer's letter. Overlapping bracelets in the picture hint that the fragments may overlap too.

The torn QR-code puzzle

The letter contains a passage of “beast speech,” decoded with an external translator. Its instructions send players back to the original answer field. The final clue is Morse code in a video; submitting the decoded message reveals the ending and a verification code.

Reading, assembling, scanning, and listening each play a part. The website carries the story between these activities and checks the answers.

Implementation

I wrote the pages in Vue 3 and TypeScript, with separate puzzle modules connected by Vue Router. Local storage preserves progress, and vue3-player-video handles the embedded video.

The video package lacked TypeScript declarations, so I added a module declaration. Vue Router's HTML5 History mode also needed a Vercel rewrite: opening a puzzle URL directly had to return index.html rather than a 404.

{
  "rewrites": [{ "source": "/:path*", "destination": "/index.html" }]
}

Development notes, story discussion, and solutions