A request list is not the update plan
The source is an August 2026 response to a public scope discussion. Its proposed priorities are editorial. The later locally captured October official announcement names a winter update and does not enumerate these requested features, so none below should be represented as scheduled.
Prioritize repeated interruptions
| Proposed area | User outcome to test |
|---|---|
| Work priorities | The assigned worker remains useful after a long session and reload |
| Palbox tools | A particular Pal can be found quickly with stable search/filter/sort |
| Storage | One explicit action consolidates stock without defeating chest intent |
| Furniture movement | A small layout adjustment does not require a full rebuild |
| Beds and medicine | Rest and treatment work without repeated manual escort |
| Building controls | Clear snap/diagonal/paint feedback supports the intended placement |
| Travel | Common routes use fewer menus without removing exploration |
| Arena | A repeatable challenge has a reason to revisit it |
Separate a quality-of-life change from a redesign
Persistent assignments and a reliable cursor are focused outcomes. A complete logistics simulation, new continent or twenty more levels is a much larger system or content commitment. Scope estimates here express uncertainty, not access to Pocketpair’s engineering plan.
Submit one reproducible request
Describe the task, current number of repeated actions, desired result and one small acceptance test. For example, preserve a chosen worker assignment through save/reload with an explicit fallback when its queue ends. Avoid presenting the reference’s ranking or comment count as a representative community vote.