Requests authority · Ver.1.09
Villager Requests Guide
Villager Requests are repeatable delivery tasks. Bulletin-board Requests become available around Year 1 Spring 8 in current progression evidence, and villagers can also offer Requests during conversation. Complete one by delivering the specified item directly to its requester; completion raises Friendship and normally pays money, but an early board completion does not immediately create a replacement.
Spring 8
Unlock reference
2 sources
Board + conversation
¥1,000
Current reward baseline
100
Completed for As You Wish
Answer first
Finish before the posting window ends, return to the actual requester, and use Deliver / 納品. Do not rush solely to force a board refresh: the completed posting remains until its original deadline.
Quick facts
The Request system at a glance
Only values supported by the current shared data are presented as facts; unresolved mechanics stay visible.
| Question | Current answer |
|---|---|
| Bulletin-board unlock | Around Year 1 Spring 8; exact story flag is unresolved |
| Other source | Villager conversation |
| Main objective | Deliver the requested item to the requester |
| Reward | ¥1,000 baseline + Friendship increase; universality and numeric delta unresolved |
| Posted deadline | Use the deadline shown in-game; one universal duration is not verified |
| Early completion refresh | No; the posting remains until the original deadline |
| Achievement | 100 completed ordinary Requests |
How to Unlock Requests
Spring 8 is the current date reference, not a substitute for the story flag
Rokkaku's early Request introduction is reported around Year 1 Spring 8. The repository's story records describe the early Request window but do not expose a dedicated unlock-condition ID.
Current trigger evidence
Use the early Year 1 story progression and check the board around Spring 8. Calendar dates in the walkthrough are references, not a guarantee that every save fires on the same morning.
Direct conversations
Conversation Requests are modeled as a separate source and can appear around the same early progression. No exact probability or daily guarantee is published.
Navigation
The canonical board location is Village (village). Use the Map & Key Locations guide for the route; no coordinates are invented here.
Bulletin Board vs Conversation Requests
Two sources, one ordinary Request system
Keep the acquisition source on the record. Do not turn conversation Requests into an assumed daily roll or treat the board as a one-request-per-villager list.
Bulletin board
Posted Request
The board presents a Request at the canonical Village location. A posted Request has a finite posting period and remains visible after early completion until that period ends.
Slot count: unknown · acceptance requirement: unknown
Conversation
Direct villager offer
A villager may offer a Request during conversation. It is a separate source on the same repeatable system; the repository does not expose requester weights, trigger chance or an every-villager guarantee.
Trigger chance: unknown · requester weights: unknown
How to Complete a Request
Deliver the exact item to the exact requester
A Request is an item-specific delivery interaction unless a canonical template says otherwise. Category similarity is not a substitution rule.
01
Obtain
Get the specified item through its current source route. Do not replace it with another fish, flower or material from the same broad class.
02
Return
Go back to the villager who issued the Request. Talking to a different villager or to the board is not an established hand-in route.
03
Deliver
Keep the requested item selected and choose Deliver / 納品. Normal talk alone does not transfer the item.
Inventory and matching limits
The current data does not prove whether turn-in reads only the player inventory, a linked Storage Box or all storage. Quality and brand matching are also unresolved for ordinary Requests. Do not promise storage-linked delivery or branded-item acceptance.
If a seasonal source closes, existing stock may still satisfy an item-specific Request; the repository does not support a blanket claim that season change cancels a valid item.
Request Deadlines & Board Refresh
Complete before the posted deadline
The current shared dataset keeps exact per-record deadlines and refresh time unresolved. Do not turn a general guide estimate into a universal timer.
Lifecycle
posted
Posted
The board or conversation presents the Request.
accepted
Accepted / active
The active state is shown conceptually; an explicit board acceptance requirement is unresolved.
completed
Delivered / completed
The specified item is delivered to the actual requester through the delivery action.
expired
Expired
The posting period ends; the current data does not document a penalty.
The refresh rule
Completing a posted Request does not immediately replace it with a new one. The original posting period must end before the board can refresh. Exact midnight, next-morning, board-interaction or next-valid-day behavior is not confirmed.
Read the in-game deadline and prioritize a safe delivery before it expires.
Board slots
Unknown
Exact expiry timer
Unknown per Request/template
Expiry penalty
Not documented
What Items Can Villagers Request?
Use repository source classes, not a fake exhaustive quest list
The current game-derived records do not expose a complete fixed random pool. These categories are the repository's source taxonomy, not a claim that every listed item is eligible in every save or for every villager.
crops
Crops
73 source record IDs are available for reconciliation.
Request eligibility: unresolved
fruit
Fruit
4 source record IDs are available for reconciliation.
Request eligibility: unresolved
paddy-tea-mushrooms
Paddy, Tea & Mushrooms
6 source record IDs are available for reconciliation.
Request eligibility: unresolved
flowers
Flowers
23 source record IDs are available for reconciliation.
Request eligibility: unresolved
fish
Fish
41 source record IDs are available for reconciliation.
Request eligibility: unresolved
forage-materials
Forage & Materials
53 source record IDs are available for reconciliation.
Request eligibility: unresolved
hunting-materials
Hunting Materials
The current source confirms the category boundary, but not an item-level ordinary-Request pool.
Request eligibility: unresolved
livestock-products
Livestock Products
The current source confirms the category boundary, but not an item-level ordinary-Request pool.
Request eligibility: unresolved
processed-goods
Processed Goods
20 source record IDs are available for reconciliation.
Request eligibility: unresolved
Observed examples
Egg / タマゴ and Clay / 粘土 are repository-observed examples from different sources. They are not a complete pool, and their requester, quantity and individual deadline remain null in the current records.
Request Quantities
Do not generalize one category's quantity to another
Exact quantities belong to a generated Request record or a canonical template. The current ordinary-Request records expose null quantities, so this page does not publish category-wide numbers.
| Observed record | Item ID | Quantity | Requester |
|---|---|---|---|
| Egg / タマゴ | egg | Unknown | Unknown |
| Clay / 粘土 | clay | Unknown | Unknown |
The item pages and Chief Delivery examples must not be copied into normal Request quantities. If a future request template exposes a rule, add that template and derive the reverse lookup from it.
Request Rewards
Money, Friendship and the lifetime completion counter
The shared Request mechanic reports the normal reward baseline. It does not expose an exact Friendship point value or prove that every random template has identical money.
Money baseline
¥1,000
Friendship
Increases
Counter
+1 on completed ordinary Request
Requests & Friendship
The Friendship system owns the relationship state. A completed Request affects the requester specifically; it is not a generic increase applied to every villager. The numeric Friendship delta is unknown.
Requests are not weekly gifts
Request completion raises Friendship, but it does not count as one of the normal two weekly gifts. It must not increment the shared normalGiftsThisWeek state, and it is separate from Meal Invitations.
Meal Invitations & Sleepovers →What Changed in Ver.1.08?
The live baseline is Ver.1.09; preserve the Japanese scope boundary
Ver.1.08 changed request/helping generation behavior around Seeds that were not yet sold and Livestock that was not yet unlocked. The current repository does not expose the generator branch needed to classify the wording more narrowly.
Official wording
The patch wording is お手伝いの依頼. It is retained as evidence, not silently translated into a new English task category.
Current availability sources
Seed eligibility must reuse Shop Inventory Unlocks, and animal-product eligibility must reuse Livestock Unlocks. A player owning an item is not the same as its source being unlocked.
What remains unknown
The exact scope—normal Requests, Helping Requests or both—is null in the current game-derived model. The page therefore does not publish pre-patch impossible-item advice or an invented filter.
Requester Set
Stable character IDs, unresolved individual eligibility
The requester roster is derived from the shared Friendship / NPC gift character entities. The current repository does not prove that every roster member can issue every normal Request or that weights are equal.
rin
Rin
Normal pool eligibility: unknown
komako
Komako
Normal pool eligibility: unknown
shiroji
Shiroji
Normal pool eligibility: unknown
kisuke
Kisuke
Normal pool eligibility: unknown
yuta
Yuta
Normal pool eligibility: unknown
sazanka
Sazanka
Normal pool eligibility: unknown
rokkaku
Rokkaku
Normal pool eligibility: unknown
yo
Yō
Normal pool eligibility: unknown
hasumi
Hasumi
Normal pool eligibility: unknown
sumire
Sumire
Normal pool eligibility: unknown
tobari
Tobari
Normal pool eligibility: unknown
konno
Konno
Normal pool eligibility: unknown
chinana
Chinana
Normal pool eligibility: unknown
nago
Nago
Normal pool eligibility: unknown
Nago and Chinana are kept in the roster as repository-derived character IDs; no early-pool timing or presence schedule is invented. Temporary story unavailability and requester weighting remain unresolved.
Requests vs Helping Tickets
Four task kinds must stay separate
The 100-Request condition is a normal completed-Request counter, not a global quest counter.
| System | Repeatable? | Main completion | Counts toward 100? |
|---|---|---|---|
| Ordinary villager Request | Yes / dynamic | Deliver item to requester | Yes, on completion |
| Helping Event | No or separate | Progression objective / unlock | No |
| Chief Delivery | No or separate | Fixed catalog group | No |
| Story Delivery | No or separate | Story event | No |
| Friendship Event | No or separate | Relationship event | No |
Helping Events
One-time progression chains such as Shiroji, Sumire, Kisuke and other Spring tasks. Use the dedicated 12-event guide for their rewards and dependencies.
Chief Deliveries
The fixed Village Chief catalog has 8 categories and 32 groups. It is not a normal villager Request and does not increment the Request counter.
Story / Friendship
Story deliveries and Friendship Events are their own task kinds. Fox Shrine offerings are also not Requests.
How to Prepare for Requests
Keep flexible supplies, not a fabricated universal stockpile
Prepare around confirmed source systems and the requests you actually see. Category frequency, selection weights and a universal must-keep list are not documented.
Check the source first
Use Crops, Fishing, Gathering, Hunting, Livestock and Processing guides to verify how to obtain the exact requested item.
Protect unique inputs
Keep rare fish, hunting drops, branded products and progression-gated goods separate until you know the active Request and its deadline.
Plan by deadline
Complete before expiry, but do not spend a unique item solely to force a new board listing: early completion has no immediate refresh advantage.
100-Request Achievement
As You Wish / 庶幾 means 100 completed ordinary Requests
Grant 100 ordinary villager requests. Do not automatically add Helping Tickets or Chief Delivery groups.
100
completed ordinary villager Requests
The completion counter is villagerRequestsCompleted. It advances on a delivered normal Request, not on acceptance.
What does not count?
- ×accepted Request
- ×expired Request
- ×Helping Event
- ×Chief Delivery
- ×Story Delivery
- ×Friendship Event
The shared Milestone Awards condition also points to ordinary Request completions. It is a separate in-game progress/reward record that happens to share the 100 threshold with the platform Achievement.
Postgame & Village in the Sunshine
The system is ongoing, but mode-specific pool details remain open
Current completion and postgame records support continued Request progress after the ending while keeping the platform-mode condition separate.
After the ending
Requests are marked ongoing in the postgame feature model, and the completion roadmap marks the track available postgame. Exact board refresh and requester behavior after clear are not isolated.
Village in the Sunshine
The mechanic is modeled for Shade and Sunshine. Do not transfer the Shade-only As You Wish platform condition into a claim that Sunshine has identical achievement behavior.
Missable window
An individual posted Request can expire or refresh, so it can be missed in the current window. No permanent unique Request reward loss is established by the current data.
Common Problems
Fast fixes for Request confusion
I completed a Request but no new one appeared
That is expected for a board posting. It remains until the original deadline/posting period ends; the exact refresh moment is unknown.
I have the item but cannot turn it in
Return to the actual requester, keep the exact item selected and choose Deliver / 納品. Ordinary talk alone is not hand-in.
The Request asks for something I cannot obtain
Check the live Ver.1.09 shop and livestock availability records. Ver.1.08 changed unavailable Seed/Livestock selection behavior, but the exact normal-vs-Helping scope is unresolved.
My Helping Ticket did not increase Request progress
Helping Events and ordinary Requests use separate task kinds and counters. Complete 100 normal Requests for As You Wish.
I am trying to save it for next season
Do not assume the deadline pauses for festivals or season changes. The calendar interaction is unresolved; use existing stock when you have it and finish before expiry.
A branded item has a different name
Ordinary Request quality and brand matching are not proven. Do not assume a renamed branded item automatically succeeds or fails.
FAQ
Villager Request answers
When do Requests unlock?
The current walkthrough evidence places bulletin-board Requests around Year 1 Spring 8. The exact story flag is not isolated in the repository, so Spring 8 is a progression reference rather than a universal hard lock.
Where is the Request bulletin board?
The board belongs to the canonical Village location record. Use the Map & Key Locations guide for navigation; this page does not invent coordinates or a separate board facility ID.
Can villagers give Requests directly?
Yes. Conversation is a separate Request source, but the repository does not expose an exact trigger probability or promise that every daily conversation produces one.
How do you complete a Request?
Obtain the specified item, return to the actual requesting villager while that item is selected, and choose the canonical Deliver / 納品 action. Ordinary conversation alone is not hand-in.
How long do Requests last?
A posted Request remains until its deadline or posting period expires. The current canonical records do not verify one duration for every Request, so use the deadline shown in-game.
When does the Request board refresh?
A posted Request remains through its posting period. Completing it early does not immediately create a replacement; the board can refresh after the original deadline expires. The exact time of day is unresolved.
How much money does a Request give?
The current shared Request record reports ¥1,000 as the normal reward baseline. Universality across every generated template is not proven, so this page does not promise that every Request pays exactly that amount.
Do Requests raise Friendship?
Yes, completion raises the requesting villager's Friendship. The numeric delta is not exposed, and a Request completion is not one of the normal two weekly gifts.
What items can villagers request?
Repository source classes cover crops, fruit, paddy/tea/mushrooms, flowers, fish, forage/materials, hunting materials, livestock products and processed goods. The full generated pool is not a fixed published checklist.
Can Requests ask for Year 2 crops?
Progression and season can still make an item inconvenient. Ver.1.08 changed unavailable Seed/Livestock selection behavior, but the exact generator scope is still being reconciled from the Japanese patch wording.
Can Requests ask for livestock products I have not unlocked?
Do not use the pre-Ver.1.08 impossible-item behavior as current. Check the shared Livestock Unlocks and Shop Inventory records; the current repository does not expose a separate Request eligibility list.
What changed in Ver.1.08?
The official wording uses お手伝いの依頼 and refers to Seeds not yet sold and Livestock not yet unlocked. The repository preserves that wording and leaves whether it covers normal Requests, Helping Requests or both as null rather than overclaiming.
Are Helping Tickets the same as Requests?
No. Helping Events are one-time progression chains with system unlocks. They do not increment the ordinary Request counter unless game-derived data proves otherwise.
Do Helping Events count toward 100 Requests?
No in the current shared condition. The 100 target is for completed ordinary villager Requests; Helping Events and Chief Deliveries are separate task kinds.
How do you get the 100-Request Achievement?
Complete 100 ordinary villager Requests. The shared achievement record is As You Wish / 庶幾, and the counter is completions—not acceptances, expirations or other deliveries.
Do expired Requests lower Friendship?
No penalty is asserted. Expiration ends the posting window and does not increment the completed counter; the current data leaves any additional penalty unknown.
Are Requests available after the ending?
The postgame model marks Relationships and Requests as ongoing, and the completion roadmap marks the Request track as postgame-available. Exact postgame board and requester behavior remains unresolved.
Do Requests work in Village in the Sunshine?
The Request mechanic is modeled for both Shade and Sunshine, while the standard-mode platform Achievement is tracked separately. Pool parity and mode-specific rewards are unresolved.
Continue with the owning guide
Requests owns the ordinary repeatable system. Use the linked authorities for source availability, relationship state, one-time Helping progression, Milestone Awards and platform completion.
Data note
What is deliberately unresolved
Unknown values remain null in the shared model instead of being filled from category examples, equal-chance assumptions or old-version behavior.
The current repository confirms 8 Chief Delivery categories and 32 fixed groups, but those fixed catalog quantities are not normal Request quantities. Use Chief Deliveries for that separate system. Use Resources & Item Uses to see where an eligible item also feeds buildings, processing or progression.
Need to find a requester before delivery? Use the Villager Schedules & Locations lookup; Requests still owns deadlines, delivery and rewards.
Written by: Village in the Shade Guide Editorial Team
Last updated: August 27, 2026
Sources: Official publisher and storefront pages, released-game research and linked source notes.