惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

D
DataBreaches.Net
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Google DeepMind News
Google DeepMind News
博客园 - 聂微东
Microsoft Azure Blog
Microsoft Azure Blog
V
Visual Studio Blog
IT之家
IT之家
博客园 - 【当耐特】
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
B
Blog
爱范儿
爱范儿
阮一峰的网络日志
阮一峰的网络日志
云风的 BLOG
云风的 BLOG
Vercel News
Vercel News
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
H
Hackread – Cybersecurity News, Data Breaches, AI and More
H
Help Net Security
J
Java Code Geeks
aimingoo的专栏
aimingoo的专栏
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
B
Blog RSS Feed
Blog — PlanetScale
Blog — PlanetScale
S
SegmentFault 最新的问题
Apple Machine Learning Research
Apple Machine Learning Research

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Summer Solstice Is Tangled: The Final Knot
Sandyard Learning · 2026-06-19 · via DEV Community

This is a submission for the June Solstice Game Jam

A game about untangling distinctions, and a story about how the same process created the game itself.

Where Am I Right Now?

This is my submission for the Summer Solstice Game Jam.

I'm not a professional game developer, and before this challenge I had never completed a real game project. I only had some basic programming knowledge and a curiosity about building things.

What surprised me most was not the game itself.

It was the realization that the process of creating the game became the same game I was trying to build.

The game is about untangling knots.

Looking back, the journey that created the game followed exactly the same structure.


Quick Jump

  1. What Was Really Built
  2. About the Game
  3. Video Demo
  4. Source Code
  5. How I Built a Game While Playing the Same Game
  6. Best Ode to Alan Turing
  7. Conclusion

What Was Really Built

In short:

A conversation.

The most interesting thing I built was not the code.

It was the journey of ideas that unfolded through a conversation with AI while designing the game.

The Summer Solstice theme immediately suggested several distinctions:

  • Longest day vs. shortest day
  • Light vs. darkness
  • Balance vs. imbalance

I became interested in the idea that these distinctions themselves might be knots.

Instead of directly explaining my idea, I started a conversation with AI and gradually explored it through questions.

The game evolved from that exploration.

At first, I thought I was creating a game about untangling knots.

Eventually, I realized that the conversation itself was untangling knots.


About the Game

Genre

A philosophical puzzle-adventure with narrative exploration elements.

Description

The Final Knot is an atmospheric philosophical puzzle-adventure game where the player explores a world trapped on an eternal Summer Solstice.

Frozen shadows have accumulated into vast cosmic knots, and each knot represents a distinction such as light and darkness, action and silence, or balance and imbalance.

Through observation, experimentation, and reflection, players gradually realize that the game is less about fixing a broken world and more about understanding the assumptions used to perceive it.

As the journey progresses, puzzles become questions, answers become patterns, and every untangled knot reveals another waiting beneath it.

The game concludes with a final knot that cannot be solved within the game itself.

A game where every puzzle untangles a concept, and every answer reveals another knot.

README

README Link Here

Video Demo

Video Demo Link Here


Source Code

GitHub Repository Link Here


How I Built a Game While Playing the Same Game

The first version was simply a puzzle game generated through AI-assisted development.

Then I suggested a small change:

Add a player action called Silence.

That single idea changed everything.

The discussion shifted from game mechanics to the meaning behind those mechanics.

We began questioning assumptions that were originally built into the game itself.

The conversation gradually moved from:

  • Commanding → Questioning
  • Fixing the world → Understanding the world
  • Achievements → Reflection
  • Action → Attention

The game became less about solving problems and more about examining how we define problems in the first place.

Some of the most interesting discussions emerged around concepts such as:

  • Balance and imbalance
  • Equality and difference
  • Distinction and comparison
  • Human and AI
  • Fear and reluctance

The game grew directly from these conversations.
Every new question revealed another conceptual knot to untangle.

Looking back, the development process followed the same structure as the game itself.

The game was about untangling.
The design process was untangling.


Best Ode to Alan Turing

I submitted this project for the Best Ode to Alan Turing category.

Many of the conversations eventually arrived at questions closely connected to ideas explored by Alan Turing:

  • What distinguishes humans from machines?
  • What role does comparison play in intelligence?
  • Can understanding exist without creating distinctions?
  • How do we recognize patterns?

The game does not attempt to answer these questions.

Instead, it invites players to explore them.

One of the final narrative elements in the game is a fictional conversation between Alan Turing and an advanced AI discussing patterns, distinctions, identity, and understanding.

Just before the player reaches the Final Knot, the conversation ends with a simple realization:

"The next knot."


Conclusion

During this project, I noticed something interesting.

Distinction and comparison appear everywhere.

Humans rely on them.
AI relies on them.
Science relies on them.
Games rely on them.

We understand things by separating them from what they are not.

Yet every distinction creates another knot.
Every answer creates another question.
Every solution reveals another possibility.

The game eventually suggests that the Final Knot should be taken with you rather than solved.

Perhaps that is true beyond the game as well.

This project also changed how I think about prompt engineering. I expected prompt engineering to be about writing better instructions. Instead, it became a process of asking better questions.

The final line of the game says:

Untangling never ends.

At first I thought that line described the player.
Now I think it also describes creativity itself.
Perhaps creativity is not the act of finding answers.
Perhaps it is the act of finding better knots.
And perhaps that is simply the way of everything.