Skip to content

Market & visitors

Fallen customers do not need more benches.

Evidence checked November 3, 2026 · PC Demo

The short answer

Visitors lying on the ground are not necessarily asleep or short of seating. In the October 26 developer reply, they are spirits who have tripped, connected to a small interaction/minigame; extra benches are not required to solve that symptom. Transparent or missing visitors are a different issue and should lead you to the entrance checks.

Checked November 3, 2026. PC Demo visitor reports and developer explanations from October, checked November 3. Exact minigame inputs, reward probabilities and a complete event walkthrough are not established by these sources. These are sourced instructions and decisions, not our own gameplay test.

On this page

Recognize the visitor scene

Animal-like spirit visitors among lantern-lit Oboro no Ichi stalls, with a visitor speech bubble.
Official Steam image · TheLaba. Visitor scene for context; this does not establish a particular Demo interaction or reward.Image source ↗Open full image ↗

Read the visitor before rebuilding the market

Visitor symptomWhat the evidence supportsNext step
Fallen or apparently sleepingThe developer identifies tripping and a small interaction, rather than a shortage of benches.Inspect that visitor and follow the interaction shown in your build.
Transparent, with a shadow still visibleAn older Demo gate-mask problem is documented.Check gate direction and the version boundary.
No apparent arrivalGate adjacency, direction and surrounding space are established checks.Check the entrance layout before treating it as an interaction problem.
Stalls have no matching resourceSelecting a product is not production.Trace the producer-to-stall chain.

These branches solve different tasks. More seating, more production and rotating the gate are not interchangeable remedies.

What to do with a fallen spirit

Look at the fallen visitor and the interaction offered by your installed Demo. The developer’s clarification tells you what kind of event to look for; it does not provide a verified sequence of buttons or timing windows.

An October player report also described helping fallen visitors and receiving something in return. Keep that as a player observation, rather than a guaranteed reward for every fall. If your version offers no usable prompt, record the build and the scene instead of adding rows of benches to force a result.

Benches already appear along road edges according to the earlier developer reply. That decorative/layout explanation is separate from the tripping event.

Little drops and clickable visitors

October 2 players described clickable guests, small leaves or boxes, and a little box giving a production or money-related buff. The developer acknowledged these interactions and said they would be explained more clearly in the full game.

  • Check what your version actually lets you select, and read any resulting message or indicator.
  • Keep a visitor interaction separate from changing a stall’s product or assigning a production building.
  • Do not plan a resource chain around an assumed buff rate, duration or guaranteed drop.
  • If a reward seems absent, compare the exact event and build with the cited reports; the sources do not establish a deterministic reward table.

A reported temporary benefit is not evidence that a stalled production setup can operate without the matching producer.

What the full-game explanation does—and does not—promise

The developer said the full game would better explain interactions, with more events and activities discussed as part of the broader market experience. Those statements are not a complete Demo tutorial or proof that every planned event is already available.

If you encounter Demo Locked, use the feature-boundary guide. It distinguishes a deliberately unavailable feature from a bug. The current material does not justify an all-minigames guide, a best-buff strategy or an unlock checklist.

You have chosen the right kind of check

A fallen spirit leads to its interaction, a transparent visitor to the gate/version check, and an empty stall to production. You can explain what was actually observed without promising an unverified reward.

Sources & version