Palworld 1.0 was a mountain. Sunreach, the World Tree, 72 Pals (47 new Pals plus 25 variants), a level cap of 80, and sweeping base-building and multiplayer overhauls, all in one release. The official Steam changelog reads like a sequel's feature list.
That is exactly why 1.1 needs a different yardstick. Pocketpair has already told us it will not be another mountain, which means the update should be judged by what it removes, not what it adds: how many times per hour the game interrupts you, how many clicks stand between you and the Pal you are looking for, how often a base does what you meant instead of what you said. A queue is not a continent. In a game this dense, it might matter more.
So this is not a leak, a roadmap, or a prediction. It is a scope board: the 25 most-requested features, ranked by how much friction they remove and how plausibly they fit inside a focused update.
Is Palworld 1.1 confirmed?#
The version number is real enough that Pocketpair's own communications lead has discussed its scope. Everything else about it is not public. What we actually have on the record is narrow: the official 1.0 release changelog, the 1.0.3 patch notes, the official server documentation, and Bucky's scope clarification. The 1.0.3 patch is the best sample of Pocketpair's current cadence: it moved the Aquatic Construction Kit down to level 23 and a single Ancient Technology Point, gave World Tree Holy Water expedition and fishing sources, and fixed issues across multiplayer, Pals, raids, building, and UI. Focused, economy-aware, friction-first.
Because the line between fact and wish blurs every time an update is discussed, this article uses three labels and sticks to them:
- Confirmed covers only official material: the 1.0 changelog, the 1.0.3 notes, the server documentation, and Bucky's scope statement.
- Request is a recurring player ask or our editorial recommendation. It is not announced content.
- Speculation is a large idea that could fit a later expansion or redesign but has no 1.1 confirmation of any kind.
Every one of the 25 items below is a Request or Speculation. If a sentence in this article sounds like an announcement, reread it: it is not one.
How this ranking works#
This is an editorial ranking, not player telemetry and not a poll. Each item is scored 1 to 5 on three axes: Impact (how many core loops the request would improve), Feasibility (how well it fits a focused update rather than a year-long expansion), and Evidence (the strength and recurrence of the documented request or current pain point). The final score is impact x 0.50 + feasibility x 0.30 + evidence x 0.20, rounded to one decimal.
Ties are resolved in order by the direct developer scope boundary, then by repeated independent requests, then by lower implementation scope. That is why, among the three items tied at 3.8, the new continent lands last: it is the literal example Bucky used to describe what 1.1 is not.
The score is a prioritization aid, not a probability of shipping. A 5.0 does not mean Pocketpair will build it, and a 2.6 does not mean they never will. The items also sort into five scope bands, five items each: Small UI, Medium systems, New content, Expansion-scale, and Fundamental redesign. The band tells you what kind of conversation an item belongs to.
Small UI wins#
Interface and rules work on systems that already exist. This band is what a focused update is made of, and it is where the board's only perfect score lives.
#1 Search, filters, and stable sorting across Palbox and Palpedia#
Impact 5, Feasibility 5, Evidence 5. Score 5.0.
The 1.0 update added 72 Pals to a roster that was already hard to browse, and the discovery tools did not grow with it. Locating the one Pal in your boxes with the right passive and work suitability is a paging exercise, and it taxes every loop the game has: breeding, base staffing, party building, condensing.
The smallest credible shape is modest: a text search that matches name, passive skill, and work suitability, a row of filter chips, and sorting that stays stable so the list does not reshuffle under your cursor mid-session. Give Palpedia the same treatment and the whole collection layer starts to feel like it belongs to a game with hundreds of species. Request, and the easiest 5.0 this board will ever hand out.
#3 Map quality of life: minimap, notes, and discovered dungeon or point-of-interest pins#
Impact 4, Feasibility 5, Evidence 5. Score 4.5.
Navigation between fast travel points is compass and memory, and a dungeon found once is a dungeon lost twice. The recurring request is not a new map: it is the map remembering what you already did.
The smallest shape: an optional minimap, free-text notes on the world map, and automatic pins for discovered dungeons and points of interest that record whether you cleared them. No new world data required, just recall of the player's own history. Request.
#5 Diagonal pieces, reliable snapping, and clearer building placement feedback#
Impact 4, Feasibility 4, Evidence 5. Score 4.2.
The 1.0 update overhauled base building broadly, but placement still fails silently: a red ghost with no explanation, snapping that grabs the wrong anchor, and a piece catalog that thinks in right angles. Builders work around it; the game should not require workarounds for its flagship system.
The smallest shape: a 45-degree wall and roof set, deterministic snap priority, and one line of text naming the object that is blocking placement. That last one costs almost nothing and would end thousands of shrug-and-relocate moments. Request.
#7 Bulk management for items, structures, and Pal actions#
Impact 4, Feasibility 4, Evidence 4. Score 4.0.
Almost every management interaction is one click per unit: depositing, deconstructing a row of walls, releasing a box of breeding by-products. The cost is not any single click, it is the hundredth.
The smallest shape: multi-select in containers and build mode, a "deposit all matching" action, queued deconstruction, and batch release with a single confirmation that summarizes exactly what leaves your boxes. That confirmation matters: bulk tools without a summary are how heartbreak happens. Request.
#17 Transmog, separated outfit slots, and more cosmetic rewards#
Impact 3, Feasibility 4, Evidence 4. Score 3.5.
By endgame, your armor stats decide your look, and everyone converges on the same silhouette. The ask is the standard fix: an appearance slot layered over each equipment slot, reusing models the game already ships.
There is a bonus here for Pocketpair: cosmetics are the cheapest possible filler for reward tables, which is a complaint of its own further down this board. One system, two recurring requests answered. Request.
Medium systems#
Real system work, scoped to simulations that already run. This band is where 1.1 could most plausibly earn its version number.
#2 Ranked work priorities with an idle fallback#
Impact 5, Feasibility 4, Evidence 5. Score 4.7.
Base assignment today is proximity and whim: kitchens starve while three Pals fight over one ore node, and "high priority" is something you enforce by picking Pals up and throwing them at the problem. In the documented request sample, one of the clearest base-management pain points is the inability to say what matters most.
The smallest shape: an ordered job list, per base or per Pal, plus one fallback rule for idle hands ("if nothing matches, haul"). We made the full argument in Six Base-Automation Fixes Palworld Players Want; that piece owns the deep automation breakdown, while this board's job is to rank the ask against everything else. It lands second overall, behind only search. Request.
#4 Persistent production queues and explicit storage intent#
Impact 5, Feasibility 3, Evidence 5. Score 4.4.
Stations forget your intent: orders evaporate across sessions and worker swaps, and output floods whichever chest is nearest. The result is a base that has to be re-instructed like a new employee every time you log in.
The smallest shape: production queues that persist through logouts and Pal reassignment, and a per-station output destination. The deep treatment lives in the automation piece linked above; the short version is that persistence is the feature, not the interface. Feasibility takes a hit because save-data and simulation changes are riskier than UI, which is why this sits below the priority system it naturally pairs with. Request.
#6 A smaller expedition station plus an expedition manager#
Impact 4, Feasibility 4, Evidence 5. Score 4.2.
Expeditions stopped being a side system the moment 1.0.3 gave World Tree Holy Water an expedition source: the endgame economy now runs partly through them. But the station's footprint fights compact base layouts, and managing parties means walking to the structure and assembling them by hand, every time.
The smallest shape: a compact station variant, plus a management screen showing active timers, party suggestions based on suitability, and a returns summary. The system already exists; the request is a front door that matches its new importance. Request.
#8 Cooling and storage rules that express player intent#
Impact 4, Feasibility 4, Evidence 4. Score 4.0.
Refrigeration means parking a cooling Pal at a specific box, and storage has no language for intent, so every chest is a junk drawer that you sort by hand. For what the 1.0 systems actually do today, the Palworld 1.0 Base Operations Manual is the reference; this entry is about the intent layer missing on top of them.
The smallest shape: allow and deny filters per container, and cooling promoted to a base-level utility state once its condition is met, instead of a Pal standing guard over one box forever. Request.
#15 Adjustable base radius and Palbox placement or upgrade controls#
Impact 4, Feasibility 3, Evidence 4. Score 3.7.
The circular base radius fights terrain, and Palbox placement is a permanent decision you make before you understand its consequences. Rebuilding a base to move its center is the kind of chore that ends play sessions.
The smallest shape: Palbox relocation within an already-claimed area, and a radius upgrade step tied to base progression. Notably, the official server documentation already exposes base limits and worker limits as configurable settings, so the idea of base parameters as dials is established server-side. A player-facing shape control is still firmly a Request.
New content#
New assets and encounters: heavier than systems work, far lighter than continents. This is the band where "focused update" and "new stuff" can still overlap.
#9 Tower Boss epilogues, repeatable quests, and recruitable variants#
Impact 4, Feasibility 3, Evidence 5. Score 3.9.
Tower arcs end at the health bar. Characters with actual writing and actual fans simply vanish once their fight is cleared, and the towers become monuments to content you already finished. The recurring request is continuation, not expansion.
The smallest shape: short post-clear dialogue scenes, a repeatable challenge version of each fight, and recruitable boss-partner variants as the long-tail chase. It reuses existing arenas, characters, and rigs, which is exactly why it out-ranks flashier content asks. This edges out the World Tree item below on the tie-break: same score, meaningfully lower implementation scope. Request.
#14 Better raid and Tower Boss reward tables with a fast rematch loop#
Impact 4, Feasibility 3, Evidence 4. Score 3.7.
Raid economics are lopsided: the preparation cost is high, the stakes are real (we documented the Bellanoir mistake that can destroy your base), and the reward table too often fails to justify either. An encounter that can level your base should pay like it.
The smallest shape: tuned reward tables and a rematch option that does not require re-farming the summon from scratch. Reward tuning is numbers work; the rematch loop is the real design task, and it is still patch-sized. Request.
#18 More signature moves and a limited, hand-authored variant pass#
Impact 4, Feasibility 2, Evidence 4. Score 3.4.
Too many Pals are interchangeable stat blocks with shared kits. And the appetite for the fix is proven by 1.0 itself: 25 of its 72 added Pals were variants.
The smallest shape: one signature move for each flagship species, plus a small, deliberately hand-authored variant batch rather than a palette-swap flood. Quality over count is the whole request. Feasibility is the constraint: moves need animation, VFX, and balance, which is why this ranks below systems work despite broad support. Request.
#20 Small Pal base activities, toys, and social idle behaviors#
Impact 3, Feasibility 3, Evidence 4. Score 3.2.
Off-duty Pals stand in place. Bases read as factories, never as habitats, and the game's biggest emotional asset, the Pals themselves, goes unused between work orders. The ask is ambient life, not new mechanics.
The smallest shape: a handful of toy structures and social idle animations, wired into the existing sanity system so play is restorative. Small scope, outsized charm per development hour. Request.
#24 Fishing and ocean events with underwater bosses or zones#
Impact 3, Feasibility 2, Evidence 3. Score 2.7.
The ocean is live tuning territory right now: 1.0.3 moved the Aquatic Construction Kit down to level 23 and one Ancient Technology Point, and gave World Tree Holy Water a fishing source. The request extends that direction into events, underwater bosses, and explorable zones.
The honest split: rare fishing events and a single ocean world boss could fit a focused update. True diving zones are expansion work in disguise, which drags the feasibility down. Request at the events end, Speculation at the zones end.
Expansion-scale ideas#
These are the ideas Bucky's statement is actually about. Keeping them on the board is honest, because the requests are real and recurring. Expecting them in 1.1 is not.
#10 New World Tree dungeon branches and a clearer endgame replay loop#
Impact 5, Feasibility 2, Evidence 4. Score 3.9.
The World Tree climb is 1.0's marquee achievement, and once it is done, the endgame replay loop thins fast. The request is more reasons to go back up: new branches, remixed encounters, rotating modifiers.
Even the smallest version, remixed branch wings built from existing encounter pieces, is a serious content lift, which is what feasibility 2 means. This is the strongest candidate on the board for a later content drop, and precisely because it is so strong, it is worth saying clearly: nothing about it is announced. Speculation for 1.1.
#13 New island or continent with fresh resources and story#
Impact 5, Feasibility 1, Evidence 5. Score 3.8.
One of the clearest content asks in the documented sample, and the named example in the scope statement of what 1.1 is not. Evidence 5, feasibility 1: the math writes itself, and the tie-break among the three items at 3.8 goes against it because the developer boundary names it directly.
There is nothing wrong with wanting this. There is something wrong with grading 1.1 against it after Pocketpair said, plainly, that a continent is not the shape of this update. Speculation, and explicitly outside the stated 1.1 scope.
#16 Cross-server Pal trading or persistent progression#
Impact 5, Feasibility 1, Evidence 4. Score 3.6.
Pieces of this already exist: the official 1.0.3 server documentation exposes Global Palbox import and export alongside crossplay platform settings. So the ask sounds like a small step, which is what makes it deceptive.
A trading economy needs persistence infrastructure, duplication protection, and moderation, none of which is patch work. The smallest honest step would be expanding what the Global Palbox can carry between worlds, but the full request is Speculation.
#19 A higher level cap and another technology tier#
Impact 4, Feasibility 2, Evidence 4. Score 3.4.
The cap has been 80 since 1.0, and cap raises are the traditional way games signal a big update. It is also the other literal example in the scope statement ("20 more levels" territory), and for good reason: a new tier means rebalancing everything beneath it, from tech pacing to Pal stats to boss tuning.
The request stays on the board because it appears across several independent wishlist discussions. The score stays modest because both the scope boundary and the hidden rebalancing cost weigh against it. Speculation for 1.1.
#21 Dynamic weather, seasons, and world events#
Impact 4, Feasibility 1, Evidence 4. Score 3.1.
Weather touches farming, temperature gear, Pal behavior, rendering, and every base layout ever built. That is the definition of a system with no small version: there is no minimum credible shape of "seasons" that does not ripple through the whole simulation.
It would transform the world's texture, which is why impact stays high. It is also exactly the kind of similarly massive work the scope statement waves off for 1.1. Speculation.
Fundamental redesigns#
Rebuilds of live systems: the riskiest engineering per unit of visible payoff, and the closest thing to the year-long project Pocketpair says 1.1 will not be.
#11 A full Pal AI and pathfinding pass#
Impact 5, Feasibility 1, Evidence 5. Score 3.8.
One of the highest-impact complaints in the documented sample is Pals that wedge themselves into geometry, abandon tasks mid-animation, and starve next to full feed boxes. Nothing would improve more loops at once than Pals that reliably do what bases need, which is why impact and evidence are both maxed. Reports are mixed, however: some players describe recent improvements to parts of AI and pathfinding. That is an argument for targeting reproducible failure cases, not for promising that every behavior needs a ground-up replacement.
But a wholesale AI rewrite risks every base in every save, and it is the archetype of the massive, year-consuming project the scope statement rules out for this update. The realistic 1.1 shape is incremental, in the 1.0.3 mold, where the patch notes fixed targeted issues across multiplayer, Pals, raids, building, and UI. Notice too that ranks 2 and 4 would quietly remove much of the pain that gets blamed on AI. Request for the increments, Speculation for the full pass.
#12 A complete base logistics layer with belts, pipes, and stock rules#
Impact 5, Feasibility 1, Evidence 5. Score 3.8.
The factory-game dream: conveyor belts, pipes, and stock thresholds turning every base into an optimizable machine. It is a beloved ask and a re-founding of the base simulation, not an addition to it.
Here is the uncomfortable truth for those of us who want it: most of the daily pain belts would solve is already addressed by ranked priorities and persistent queues, at a tenth of the scope. A queue is not a continent, and it is not a conveyor network either. It is just the part you would actually feel by the next patch. Speculation.
#22 A supported PvP mode with guild conflict and reward rules#
Impact 4, Feasibility 1, Evidence 4. Score 3.1.
PvP technically exists: the official server documentation exposes PvP settings and explicitly calls PvP a trial feature not covered by support. The request is to promote that trial into a real mode with guild conflict, reward rules, and actual balance.
That promotion is the expensive part. A supported competitive mode means balance passes across the full Pal roster, netcode hardening, and anti-griefing policy, which is redesign-scale work stapled to a live service commitment. The trial label exists for a reason. Speculation.
#23 A world-customization toolkit for bosses, technology, randomization, and seeds#
Impact 4, Feasibility 1, Evidence 4. Score 3.1.
Replayability tinkerers want to remix the world: shuffled bosses, edited tech trees, shareable seeds. And the seed of it is Confirmed to exist: randomizer settings already appear in the official server documentation.
The smallest honest step, more dials on that existing randomizer surface, would belong two bands up. The full toolkit is a redesign of how worlds are defined and validated, and that is the version people are actually asking for. Speculation at full scope.
#25 Play as a Pal or transform into a Pal with full traversal and combat rules#
Impact 3, Feasibility 1, Evidence 4. Score 2.6.
The most expansive fantasy on the board and the least plausible: playing as a Pal means traversal, combat, camera, and animation rules for every species you can become, which is a second player character multiplied by the whole roster.
It ranks last not because it is a bad idea but because it is a different game's worth of work wearing a wishlist item's clothes. A wonderful dream for a very different update. Speculation.
What Palworld 1.1 should feel like#
Our recommendation is simple: 1.1 should feel like the game finally getting out of your way. You log in and the base runs the way you set it. You find any Pal in seconds. The map remembers where you have been. A raid is worth rematching, and a tower boss has something to say after the fight. None of that needs a continent, and all of it would change every single session.
The 1.0 update proved Pocketpair can build big. The scope statement suggests 1.1 is their chance to prove they can build sharp, and the top of this board is what sharp looks like: five UI wins and five system fixes that together would do more for daily play than any landmass.
So here is the reader prompt. Look at ranks 1 through 6 and ask yourself which one you would trade for a continent. Then tell us what you would move up or down, because this board is an argument, not a verdict, and the best version of it includes your ranking too.
Comments
Loading discussion...