Read the board as proposals with uncertainty
The reference ranks twenty-five requests with a weighted editorial score: impact50%, feasibility30%, evidence20%. Those inputs are judgments, not development estimates supplied by Pocketpair and not probabilities of release. The five bands separate UI work, system work, new content, expansion-scale ideas and fundamental redesigns.
Use an independently worded request ledger
The appended table preserves the factual source order and score while restating each request. A high position means the source author prioritizes it. Zero entries are treated here as confirmed 1.1 features.
What would count as confirmation
Require a dated Pocketpair announcement that names the feature and its release scope. The October winter-update teaser establishes an update context, not this twenty-five-item roadmap. Large ideas such as a continent, cross-server persistence or full base logistics remain proposals regardless of how often they appear in a thread.
Make a smaller request testable
Turn a broad wish into an observable task: find a named Pal in under ten seconds, preserve a queue through reload, or show why placement is rejected. Describe the benefit without pretending to know the implementation cost. Revisit the board after official notes are published instead of carrying a speculative label forward as fact.
Twenty-five proposals, with their original evidence labels
Requests are independently restated. Rank, scope band and score are attributed editorial inputs from the source, not Pocketpair commitments or release probabilities.
| Source rank | Restated request | Source scope band | Source score | Source evidence label |
|---|---|---|---|---|
| 01 | Find Pals with stable search, filters and ordering | Small UI | 5.0 | Request |
| 02 | Persist ranked worker jobs with a fallback | Medium systems | 4.7 | Request |
| 03 | Add useful map notes and discovered-point tools | Small UI | 4.5 | Request |
| 04 | Preserve production queues and storage intent | Medium systems | 4.4 | Request |
| 05 | Improve diagonals, snapping and rejected-placement feedback | Small UI | 4.2 | Request |
| 06 | Manage expeditions with less floor space | Medium systems | 4.2 | Request |
| 07 | Apply bulk actions to common management tasks | Small UI | 4.0 | Request |
| 08 | Make cooling and storage priorities explicit | Medium systems | 4.0 | Request |
| 09 | Add reusable post-tower objectives and character follow-ups | New content | 3.9 | Request |
| 10 | Vary the repeatable World Tree endgame | Expansion-scale | 3.9 | Request |
| 11 | Improve Pal navigation and decision-making | Fundamental redesign | 3.8 | Request |
| 12 | Design a richer base logistics system | Fundamental redesign | 3.8 | Request |
| 13 | Expand geography and its resources | Expansion-scale | 3.8 | Speculation |
| 14 | Make boss rewards and rematches more repeatable | New content | 3.7 | Request |
| 15 | Offer clearer base-radius and Palbox controls | Medium systems | 3.7 | Request |
| 16 | Explore cross-server trade or persistent progression | Expansion-scale | 3.6 | Speculation |
| 17 | Separate appearance choices from equipment power | Small UI | 3.5 | Request |
| 18 | Add carefully differentiated moves and variants | New content | 3.4 | Request |
| 19 | Extend the level and technology progression | Expansion-scale | 3.4 | Speculation |
| 20 | Give base Pals more small social activities | New content | 3.2 | Request |
| 21 | Explore changing weather, seasons and events | Expansion-scale | 3.1 | Speculation |
| 22 | Define a supported competitive guild/PvP loop | Fundamental redesign | 3.1 | Speculation |
| 23 | Expose structured world-customization tools | Fundamental redesign | 3.1 | Speculation |
| 24 | Expand fishing and underwater encounters | New content | 2.7 | Speculation |
| 25 | Explore direct playable-Pal transformation | Fundamental redesign | 2.6 | Speculation |