itch.io

The part about having around 250 people join the playtest but receiving only two public feedback posts stood out to me. I suspect this is not necessarily a sign that people were uninterested. Playing something is relatively easy, but writing useful criticism publicly requires much more effort and can also feel uncomfortable.

I am currently preparing a much smaller closed test for a narrative adventure, and this makes me think that relying on voluntary public feedback is probably not enough. My current plan is to combine direct observation with a short private questionnaire and a few follow-up conversations. Were you able to see where players stopped or how far they progressed? If the average session was around twenty minutes for a one-hour build, there may be a specific early point where people lost direction or motivation.

@dropkickgames - Looks really thoughtfull with its unique style. Will give it a try. 

I would be interested to see how you prevent the player from simply trying every possible option. Do incorrect or poorly timed questions affect trust, consume meaningful time, or close certain lines of inquiry? That seems central to whether the system feels like actual deduction rather than systematic trial and error.

Hello,

I am developing Where the Arc Falls, a story-rich point-and-click adventure built around exploration, dialogue, observation, and puzzles that belong naturally to the world around them.

The project began as something I had wanted to make for a long time but did not initially believe I could produce alone. I have a professional software-engineering background, but my previous experience in game development was mostly experimental and small-scale. Over time, improvements in tools, production workflows, and my own understanding of the problem made the project feel less hypothetical and more achievable.

The first chapter is now playable from beginning to end. I am currently stabilizing it for a small closed testing group, with particular attention to save and load behavior, player guidance, pacing, animation, and whether the puzzles communicate their logic without excessive explanation.

I am intentionally keeping most of the story and specific puzzle solutions private at this stage. What I plan to share here is the development process: the design principles behind the game, the systems that support it, the problems that do not work on the first attempt, and what changes once people other than the developer finally play it.

I recently published the first longer article about why I started building the game:

Episode 1: Why I Started Building an Adventure Game

The project page is here:

Where The Arc Falls

One issue I am currently thinking about is how much information an adventure game should give the player before helpful guidance begins to weaken the satisfaction of discovery.

For people who play point-and-click adventures: when you become stuck, what usually makes you continue experimenting, and what makes you decide that the game has simply failed to communicate?

I will continue updating this thread as Chapter 1 moves through testing.
Would really appreciate this community's feedback, thoughts and hoping I could recruit some beta testers with true passion for old-school advneture gaming and great story-telling.