NOTES FROM THE ISLANDS
Update context, player questions and fresh reasons to head back into Palpagos.
108 original briefs and stories
Community
Pocketpair's 2026 global poll placed Sekhmet, Solenne and Chillet first through third in the Pal category; Zoe, Auri and Saya led the character category. Popularity results do not establish a combat ranking.
Read field notes ↗Player guides
Pocketpair announced Palworld: Side by Side for winter 2026. The name and promotional artwork are confirmed; detailed companion mechanics and a complete feature list need a later official announcement.
Read field notes ↗Updates
Version 1.0.4 added two linked sub-missions and changed fishing, combat, base behavior and other systems. Its Steam mod-removal fix does not certify that an individual mod works on that revision.
Read field notes ↗Base building
When remote production stops, inspect simulation behavior, worker access, food and storage before blaming a single setting. Local play and dedicated-server behavior need separate reproduction evidence.
Read field notes ↗Resources
Compare fifteen ordinary level-70, four boss and six level-80 drop rows: five level-80 Electric carriers plus Helzephyr Lux’s Dark crystal, with configured spawn tiers, conditional Alpha forms and eligible party quantity bonuses.
Read field notes ↗Base building
Compare all thirteen work suitabilities for six advanced human workers, their mixed grade-22 visitor pool, capture correction and separate native Work Speed modifier stages.
Read field notes ↗Player guides
Separate confirmed patch fixes from player reports that still need reproduction. A useful issue record includes the game build, platform, mods, reproduction steps and the outcome on a clean save.
Read field notes ↗Player guides
A feature wishlist is an editorial assessment of benefit and implementation scope. Keep proposed changes separate from confirmed development plans and make the assessment criteria visible.
Read field notes ↗Player guides
Endgame choices include World Tree progression, Pal upgrades, breeding, raids and rematches. Choose a concrete goal and identify its shared resource requirements before starting several expensive projects at once.
Read field notes ↗Resources
Giving sanctuary patrol drones AI Core rewards is a community proposal. Keep the proposed reward separate from verified live drops and explain how it could alter the choice between stealth and combat.
Read field notes ↗Community
The four-region world idea is a community interpretation of the map and story. A matching prediction does not confirm the remaining geography; record what future official evidence would test it.
Read field notes ↗Card game
Separate a restock already in transit from a later print run still being planned. Confirm the product, edition markings, region and timing before using either announcement to make a purchase decision.
Read field notes ↗Community
Public exchanges between developers can invite speculation without announcing a crossover. Keep the original posts, their dates and the absence or presence of a formal product announcement visible.
Read field notes ↗Combat
Track Panthalus's summon items, access route and encounter rules separately from ordinary legendary hunts. Verify any special capture condition before applying a general damage or sphere plan.
Read field notes ↗Player guides
Combine ore-weight effects only after checking their rank, activation and stacking rules. Gear unlocks and variant identity matter when testing whether a mining party can carry the planned material load.
Read field notes ↗Player guides
Choose experience settings around the pace of exploration, equipment unlocks and your group. The configuration exposes an experience multiplier; a recommended preset is an editorial preference rather than an official difficulty mode.
Read field notes ↗Resources
Check how the Heavily Armored passive interacts with a self-explosion skill before planning repeat use. Separate the skill's damage, survival condition and recovery time in the build explanation.
Read field notes ↗Pal upgrades
Compare passive effects by their actual stat change, conditions and acquisition route. A four-slot damage plan must also account for survivability, skill use and the cost of replacing an existing passive.
Read field notes ↗Player guides
Dense placement techniques must preserve access and operation. Test harvesting, transport, collision and worker pathing after stacking facilities instead of treating a successful placement preview as proof of a working base.
Read field notes ↗Card game
Evaluate a reprint by player access, store supply and support for organized play. Those priorities form an editorial argument; they do not prove a publisher's future production plan.
Read field notes ↗Franchise
Compare the announced spin-offs by their official store descriptions and release status. A farming game and a romance-focused game answer different player interests; neither is a mode inside the main Palworld save.
Read field notes ↗Franchise
The announced mobile projects have different publishers and designs. Compare official descriptions and release status without presenting either project as a mobile login to the existing Palworld world.
Read field notes ↗World setup
Work priorities, storage, Palbox management, construction and arena controls are distinct improvement requests. Present them as proposals unless an official update commits to a specific behavior.
Read field notes ↗Player guides
Compare an Alpha and a normal Pal with the same species, level and upgrades. Extra health and a larger target can pull the decision in different directions, so encounter shape matters alongside the stat screen.
Read field notes ↗Player guides
Separate arena entry, opponent requirements, reward payouts and shop purchases. Compare rewards against repeatable match time and verify the relevant bracket before saving for a particular item.
Read field notes ↗Progression
A single-fight leveling claim depends on stacked experience effects and the precise encounter reward. Reproduce the setup with starting levels, settings and buffs recorded before treating it as a general leveling method.
Read field notes ↗Player guides
A visual size glitch is a dated bug report rather than a supported customization feature. Record the platform, game build, reproduction conditions and whether other players observed the same result.
Read field notes ↗Base building
Stealth tools and chest behavior can change the risk of an enemy-base route. Treat a despawn exploit as patch-sensitive and distinguish it from the intended stealth mechanic.
Read field notes ↗Progression
The official 1.0.3 update moved the Aquatic Construction Kit from level 66 to 23 and reduced its Ancient Technology Point requirement from four to one. Exact recipe quantities require dated data records.
Read field notes ↗Player guides
Official 1.0.3 notes confirm cheaper progression and oil infrastructure, but do not specify every quantity. Exact before-and-after costs require two dated data snapshots rather than inference from the announcement.
Read field notes ↗Player guides
Use the fixed 120-second character preservation effect and distinguish the Recycler’s separate one-water fuel input, 1.5× work rate and paused working counter.
Read field notes ↗Base building
The 1.0 release revised building, ranching, breeding and base operation. Review each system against your existing layout before moving workers or rebuilding production lines.
Read field notes ↗Fishing
Choose fishing spots by their Pal and item pools, then match rod, bait and party support to the goal. The official 1.0.4 update changed fishing difficulty and rewards, so older rates need rechecking.
Read field notes ↗Updates
Version 1.0.3 lowered selected technology gates, adjusted Holy Water and oil infrastructure, and repaired several systems. Use its dated notes alongside the matching extracted data rather than calling the snapshot current.
Read field notes ↗Player guides
Group achievements by systems that can progress together, then track the remaining counters separately. Keep the platform's current achievement list as the denominator and identify requirements that depend on story or endgame access.
Read field notes ↗Player guides
A boss encounter, a database entry and an obtainable Pal are different things. Check capture eligibility, egg rewards, breeding rules and other acquisition channels before assuming a catalog record belongs in a player roster.
Read field notes ↗Combat
Keep cosmetic rewards tied to the exact tower or raid variant that awards them. A normal clear, Hard Mode clear and Ultra raid can have different requirements and reward records.
Read field notes ↗Player guides
Track bounty locations, token payouts and shop unlocks as one route. Check target difficulty and the current reward table before committing tokens to a permanent upgrade.
Read field notes ↗Modding
Prepare Hard Mode rematches around their unlocks, timer, encounter mechanics and reward variant. Use the normal encounter as background rather than assuming its damage and pacing carry over.
Read field notes ↗Player guides
Track slab fragments, the summon, the battle phases and the reward egg as separate steps toward owning Blazamut Ryu. A summoned raid boss and the Pal hatched from its reward have different acquisition rules.
Read field notes ↗Player guides
Farm all 16 recorded slab-fragment sources, compare the Feybreak complete-slab shortcut, prepare the standard raid and reserve meteorite materials for the saddle.
Read field notes ↗Player guides
Use a treasure map's tier and eligible sources to plan a farming circuit. Include travel to the generated objective and the actual reward pool when comparing maps with other loot activities.
Read field notes ↗Franchise
Treat Palworld Online as a separate announced mobile project. Verify its publisher, promised systems, supported regions and release window from first-party announcements rather than borrowing facts from another adaptation.
Read field notes ↗Base building
Diagnose automation friction as task choice, storage, production control or pathing. Community suggestions about these systems are design proposals until the game implements them.
Read field notes ↗Combat
Order raid attempts by preparation requirements, encounter mechanics and reward value. A raid boss's displayed level does not make it equivalent to a wild Alpha of the same level.
Read field notes ↗Resources
An Ancient Hatchery is a capital investment in breeding throughput. Compare its construction cost and operating requirements with how many eggs you intend to process, rather than assuming faster incubation always pays back.
Read field notes ↗Base building
A reported oil-production showcase needs its world settings, elapsed time, worker setup and initial inventory before its output can be compared with another base. Treat the headline as a report until reproduced.
Read field notes ↗Player guides
Check Alpha Sekhmet's work effect against the facility it actually supports. Record a controlled production test before converting a reported speed increase into a promise about all mining work.
Read field notes ↗Card game
Reported resale listings are dated asking prices, not a verified market-wide transaction average. Compare official restock news with regional availability before treating scarcity claims as a reason to buy.
Read field notes ↗Player guides
Returning players should recheck capture gear, partner skills, upgrades and base systems after the 1.0 overhaul. Familiar names can retain their identity while their practical role changes.
Read field notes ↗Pal upgrades
Separate individual stat improvement from passives, skills, condensation, Souls and Awakening. Work on the weakest relevant layer first instead of replacing a favorite species solely because one roll is poor.
Read field notes ↗Progression
Compare expeditions using their duration, strength threshold and reward distribution. Expected rewards per hour are a model, not a guarantee for an individual expedition.
Read field notes ↗Resources
Expand Wing Cell consumption into crude-oil and power demand. Production estimates need the extractor, worker, research and world-setting assumptions so travel costs remain comparable.
Read field notes ↗Updates
Version 1.0.2 focused on crashes, multiplayer, missions, controls, graphics and performance. A published fix is evidence of the intended change; successful behavior on a specific installation still needs retesting.
Read field notes ↗World setup
Community comparisons with ARK focus on automation, creature roles and adjustable survival demands. They describe the sampled discussion, not a representative survey of either game's entire player base.
Read field notes ↗World setup
A dated Steam concurrency series can show the scale and duration of a player rebound. It cannot establish why every player returned or measure the population on other platforms.
Read field notes ↗Resources
Build Paldium supply around recurring sphere and ingot consumption. Compare a crusher production line with mining, recycling and expedition rewards, including the work and transport needed to sustain each source.
Read field notes ↗Player guides
Build eligible egg-collection, breeding and selling setups using the native Alpha/extra sequence, highest-only basecamp breeding bonus and seller-party Money-sale rules.
Read field notes ↗Resources
Expand an AI Core into its ingredient chain before choosing a craft. Compare the total resource commitment across weapons, equipment and base structures so one unlock does not strand the next project.
Read field notes ↗Player guides
Dynamoff combines an Electric identity with travel and base uses in the acquired game records. Keep the community reaction separate from those measurable roles when deciding whether it fills a slot in your run.
Read field notes ↗Resources
Ancient Civilization Cores and ordinary Ancient Civilization Parts are different ingredients. Compare eligible raids, expeditions and other verified reward channels using completion time and access requirements.
Read field notes ↗Capture
A rounded percentage display is weaker evidence than the internal eligibility rule. Separate low displayed odds from explicit capture immunity, and check the sphere, target and game settings before drawing a conclusion.
Read field notes ↗World setup
Pocketpair reported more than 850,000 concurrent Steam players after the 1.0 release. This is a platform-specific concurrency milestone, not a count of monthly players or total game sales.
Read field notes ↗Player guides
Evaluate Air Dash Boots by movement control and the upgrade cost for the terrain you cross. Separate ordinary movement behavior from timing techniques that may change between patches.
Read field notes ↗Resources
Plan a relic circuit around verified World Tree sources and travel time. Attribute a creator's route and keep their reported run results separate from an independently measured rate.
Read field notes ↗Base building
Plan access and worker movement before increasing building density. Placement tricks can save space, but a layout still needs reachable food, beds, storage and workstations to be useful.
Read field notes ↗Pal upgrades
Choose defensive passives for the damage pattern and role of the Pal. Compare conditions and tradeoffs with the offensive slot they replace, and check patch notes for passive fixes.
Read field notes ↗Player guides
Preview condensation progress before confirming a transfer. Count the contribution of upgraded donors and any surplus carefully so an improved replacement Pal does not waste prior investment.
Read field notes ↗Resources
Compare field collection with the Ancient Material Synthesizer once it becomes available. Include its unlock, construction, staffing and power needs when deciding whether an automated ore source solves your current bottleneck.
Read field notes ↗Player guides
Prioritize a working food loop, basic production, manageable travel and useful captures. Follow technology prerequisites alongside character level so new regions do not outrun the equipment your base can supply.
Read field notes ↗Resources
Evaluate a Lyleen breeding and disassembly loop as a renewable technology-manual source. Count cakes, hatch time and the relevant drop record before comparing it with exploration rewards.
Read field notes ↗Player guides
Read launch reactions as dated community evidence. Compare repeated concerns with official changes and distinguish a reported problem from an issue reproduced on a known game build.
Read field notes ↗Community
A survey mention can show that a publisher asked about a game; it does not establish a collaboration. Treat the circulated screenshot and commentary as separate evidence from a signed announcement.
Read field notes ↗Equipment
Fixed shrine and mission rewards can offer an alternative to repeated random drops. Confirm each reward, unlock condition and location before planning the route, then include the materials needed to craft it.
Read field notes ↗Player guides
Looted spheres can precede their crafting unlocks. A useful route still needs access requirements, regional enemy risk, repeatability and a clear distinction between intended progression and a sequence break.
Read field notes ↗Pal upgrades
Herbil's partner effect and gear requirements define its recovery role. Check the trigger, heal scaling and cooldown in the dated records before relying on it for a dangerous encounter.
Read field notes ↗Progression
Protect travel, base and specialist Pals before using expedition auto-assignment. Check the exclusion control in your game revision and confirm the chosen roster before starting the expedition.
Read field notes ↗Equipment
Build a schematic route around the actual reward pool. Record treasure-map sources, chest eligibility and crafting requirements so a rare schematic can become usable equipment rather than an isolated drop.
Read field notes ↗Progression
Combine accessible experience activities with verified party and base buffs. Compare combat, capture and crafting loops at the stage where your account can sustain them.
Read field notes ↗Player guides
Choose the correct reusable lockpick tier, retry failed attempts without tool consumption, and distinguish Mimog’s five rank-dependent cooldowns.
Read field notes ↗Player guides
Egg collection effects and the breeding result are separate parts of an Alpha project. Check each partner skill's activation conditions and tested game version before assuming a pickup party guarantees a result.
Read field notes ↗Progression
Level a raid roster in batches with a repeatable experience source. Include time spent swapping Pals, feeding buffs and finishing partial levels when comparing the throughput of two methods.
Read field notes ↗Player guides
Between the opening base and endgame, connect technology, gear, partner-skill unlocks and Pal upgrades. Solve the system blocking progress before farming levels that the rest of the save cannot support.
Read field notes ↗Modding
Pocketpair advises backing up saves, removing old mod files and loaders, verifying Steam files and checking an unmodded launch before reinstalling compatible mods one at a time.
Read field notes ↗Progression
Connect each 1.0 addition to a player task: reaching a new area, improving a Pal, building a team or supplying a base. Use official notes for system changes and dated game records for exact values.
Read field notes ↗Player guides
Choose between continuing and restarting after protecting the existing world. Check the official migration notes, reset behavior, mod dependencies and the amount of new progression you want to experience in sequence.
Read field notes ↗Player guides
The official 1.0 release introduced Sunreach, the World Tree, Awakening, Mutation and extensive system changes. Use the release announcement to distinguish shipped changes from expectations about later updates.
Read field notes ↗Updates
The official release raised the level cap to 80 and added 72 species and variants alongside new areas and progression systems. Later hotfixes need their own dates and cannot be folded silently into the release baseline.
Read field notes ↗Updates
The 1.0.1 hotfix addressed save-loss risk and several platform-specific faults. Keep each fix's affected platform clear and protect saves before testing a previously failing scenario.
Read field notes ↗Progression
A fishing acquisition route can bypass the need to defeat a high-level wild target. Check the spot's pool, rod requirements and escape risk, then compare the obtained Pal's actual work roles with the base you have.
Read field notes ↗Base building
Keep a raid experiment separate from production infrastructure. Check the raid area, deployed roster and escape plan before using a slab; destructive attacks make the arena choice part of preparation.
Read field notes ↗Resources
Choose between manual collection, Pal drops, purchases, ranching and production. Compare each source at the stage when it becomes available, including transport and food costs.
Read field notes ↗Equipment
Use the exact loot pool and item identifier to plan schematic farming. Fixed rewards, chest variants, fishing, expeditions and recycling are separate channels and cannot be summarized as one universal chest chance.
Read field notes ↗Resources
Assign permanent ranch workers to recurring demand and rotate temporary ingredients. Compare grazing output with purchase and combat sources before spending a scarce base slot on every possible material.
Read field notes ↗Resources
Surfent's watering and ranching roles can compete for its time. Restrict the worker to the job your base needs and verify whether the observed leather behavior involves a normal or Alpha variant.
Read field notes ↗Breeding
Distinguish a passive that can be installed at the surgery table from one that still requires another acquisition method. Include unlocks, implant access and fees when comparing surgery with breeding.
Read field notes ↗Player guides
The Terraria collaboration has its own encounters, rewards and equipment path. Confirm which content carried into your game revision before using an older dungeon farming route.
Read field notes ↗Player guides
A console enrolled in a preview branch can show a different build from the public release. Verify enrollment and protect save data before changing the branch or reinstalling the game.
Read field notes ↗Player guides
Start with the official rules and available products, then move from a trial deck to a card search and deck plan. Keep regional product dates and card legality separate from the video game's data version.
Read field notes ↗Player guides
Plan mushroom gathering from verified field nodes and Pal drops, then compare those routes with your recipe demand. Keep item identity and regional access clear so similar mushroom names do not merge into one source.
Read field notes ↗Base building
Match workers to the jobs your base needs, using suitability, movement, food and work restrictions together. A high level in one job can be wasted if the Pal continually chooses another task.
Read field notes ↗Breeding
Start a breeding route from Pals you can actually obtain and the worker role you need next. Calculate intermediate parents and cake demand before treating the final species as an early upgrade.
Read field notes ↗Capture
Compare merchant inventories and access requirements before planning a capture. Verify which inventory persists after recruitment and distinguish a vendor's shop role from its potential base work.
Read field notes ↗Player guides
Choose accessories for the task and check the actual schematic source. Separate the cost of opening accessory slots from the cost of acquiring and crafting the items that occupy them.
Read field notes ↗Player guides
Power and cooldown provide a starting comparison for skill fruits. Targeting, animation, elemental fit, statuses and the enemy's movement can change practical performance, so a numerical index needs an explained purpose.
Read field notes ↗Player guides
Compare Pals by an explicit combat role and a stated method. Base stats, available skills, partner effects and encounter requirements describe different strengths and should not be hidden behind a universal ranking.
Read field notes ↗Base building
Evaluate base sites by buildable space, resources, access, threats and the intended production role. Coordinates identify a site; they do not prove that every server permits the same layout.
Read field notes ↗Updates
The official 1.0.5 hotfix addresses texture resolution and map filter persistence. It is the newest numbered release found in the publisher announcement feed retrieved on October 23, 2026.
Read field notes ↗