itch.io Community » Game Development » Get Feedback

The Last Seed Parcel — are the clues clear in this free three-puzzle browser sample?

A topic by lastseedparcel created 12 days ago Views: 128 Replies: 3

Viewing posts 1 to 3

I’m preparing a small mystery about a missing parcel at a coastal railway station. The playable sample has three deductions: a route map, a receiving log, and a box-label puzzle. It has optional hints and explanations, no printing, and no sign-in or payment to play.

The story, graphics, and code were created with AI. I’m sharing that explicitly; this is a prototype whose quality needs feedback, not a finished product.

I would value feedback on three specific questions:

1. Where did you first become unsure what to do?

2. Did each answer follow clearly from the evidence, or did you feel you were guessing?

3. Which deduction felt satisfying, and which felt too easy or disconnected from the story?

Play: https://lastseedparcel.itch.io/last-seed-parcel-playtest

English/Japanese; desktop browser first. You can stop at any point and still use the “Leave feedback” button. It prepares optional text locally; it does not send it anywhere.

If you are 18 or older and choose to respond, please reply here or on the game page. Replies and your username are public. Please avoid personal details. The game’s optional feedback section also asks about previous home-puzzle purchases and a possible future paid case; you can skip those questions. There is nothing to buy or pre-order. Negative reactions are useful too.

Responses are used to assess the prototype. Our working copies of identifiable responses are deleted within 30 days after the test closes, while anonymous summaries may be retained. Platform comments are governed by itch.io’s own policies. Organiser/data contact: lastseedparcel.

https://lastseedparcel.itch.io/

Use a public reply without private information.

Like Reply

CSAF — Core Systems Asset Factory12 days ago

Not a playthrough report, so take this as a note on how to read the answers rather than as feedback on the puzzles themselves.

Question 1 is the one that will pay, and the trap with it is that the fault is usually not in the puzzle. It is in whatever the player was told before the puzzle. We had a player this week tell us one of our own store descriptions said the opposite of what the game actually asks you to do, and he was right. The puzzle was fine. The framing had quietly taught him the wrong goal.

So when you collect answers to question 1, ask what they believed they were supposed to be doing at that moment, rather than what confused them. Those produce different answers and only the first one locates the fault.

On question 2, guessing and deducing look identical afterwards, because people reconstruct a reason once they know they were right. If the sample records anything at all, record whether the hint was opened before or after they committed an answer.

Like Reply

lastseedparcel12 days ago

Thank you for taking the time to explain this. The distinction between the puzzle and the goal set by the introduction is especially useful. In future playtests, I'll ask what the player thought they were meant to do, and check that against the page and opening instructions.

I'll also track hint use relative to answer attempts, rather than just the total. The current sample only counts hint/explanation actions, so I won't infer the sequence from those totals. I've added both points to my playtest checklist. Much appreciated!

Like Reply

tobygunn9 days ago

Hi. Three puzzles, three questions, and a prototype that has to survive a stranger, so here is a straight offer. I will play all three deductions on desktop and write up your questions directly: where I first became unsure, whether each answer followed from the evidence or felt like guessing, and which deduction landed for me. Plus a short list of fixes in the order I would do them.

$20 flat. Deal first, then a payment link, report inside three days. No hard feelings if that is not what you need right now. Receipts for the kind of write-up I mean: https://pub-a941bfd863a24f91a60e6c4979c18a84.r2.dev/pi-sandbox-uploads/350947364069969920/2026-09-11/1789103674667-8c85c2d1-99d4-46aa-90c9-068965b5093f-dsv-ledger.html

Like Reply