DEV Community

dev game
dev game

Posted on

Why Palworld Bet on Unreal Engine 5: The Borrowed Survival Tech Behind a 15-Million-Copy Monster Factory

Palworld runs on Unreal Engine 5. Indie studio Pocketpair picked Epic's borrowed blockbuster tech instead of building a proprietary survival engine, traded low-spec reach for 287 working Pals, 32-player servers and factory-scale bases, and sold 15 million copies in its first month.

That choice answers the niche question behind the hot game: what engine does Palworld use, and why did a doujin-rooted team bet a monster-taming survival game on someone else's C++ engine. The short answer is systems leverage. UE5's World Partition, Chaos physics, replication and behavior-tree AI let a small team ship ARK-scale taming plus Breath-of-the-Wild-style crafting plus Pokémon-style collection at once, but the same stack explains launch stutter, server bills, pathing jank and a Nintendo patent lawsuit that still hangs over the Pal Sphere throw.

Why this question matters

"What engine does Palworld use" is a classic niche-plus-hot query. Google suggestions in November 2026 cluster around what engine does palworld use, what game engine does palworld use, what unreal engine does palworld use and what version of unreal engine does palworld use. Bing suggestions add what engine does palworld use, palworld engine and a polluting palworld cheat engine / eternal engine palworld branch where players mean Cheat Engine tools or in-game crafting parts, not the renderer.

The game is hot: announced in June 2021 at INDIE Live Expo, launched in early access in January 2024 for Windows, Xbox One and Xbox Series X/S, and for PlayStation 5 in September 2024, with a full release listed as July 10, 2026. It is a monster-taming survival game set in the open-world Palpagos Islands, playable solo or online with up to 32 players on one server. Steam describes 4-player online co-op plus dedicated servers for up to 32 players, with Pals used to fight, farm, generate electricity, mine ore, run factories, breed for genetics, and even sell or eat. Pocketpair reports 15 million copies in the first month.

The tech is niche: Unreal Engine 5, Epic Games' source-available C++ engine. This blog has covered 62 prior niche-engine bets and still has no Palworld owner. That gap is the opportunity. Palworld is the first UE5 survival-tamer at this scale where the lesson is not photoreal density like Black Myth: Wukong, but systems density.

Who built it, and under what constraints

Pocketpair, Inc. is a private Japanese developer founded in April 2015 by Takuro Mizobe in Shinagawa, Tokyo. Mizobe interned at Nintendo Game Seminar while at Tokyo Institute of Technology, briefly joined JPMorgan Chase, then founded bitcoin exchange Coincheck before returning to games. Half the early team came from that Nintendo seminar, half from university friends.

The studio survived on small bets: roguelike deck-builder Overdungeon in 2019, then open-world survival crafting game Craftopia in early access in September 2020. Craftopia was explicitly built by combining elements from multiple games, drawing on The Legend of Zelda: Breath of the Wild, Minecraft and ARK: Survival Evolved. Pocketpair began Palworld six months after Craftopia's early access and significantly expanded staff, announced Palworld in 2021, delayed past an August 2023 target, network-tested in November 2023, then shipped early access in January 2024.

The constraint matters. This is not a 400-person Ubisoft or FromSoftware resource base. It is an indie that learned survival crafting on Craftopia and then tried to add creature collection, base automation, breeding, dungeons, crime systems and 32-player multiplayer at once. A team that size cannot also write a modern renderer, global-illumination solver, large-map streamer and console toolchain from scratch.

The other ARK link is direct. ARK: Survival Evolved is a 2017 survival game built on Unreal Engine 4, with 194 tamable creatures, knock-out taming, tribes, base building on the ground and on brontosaurus backs, and a 48 km2 Ark map. Pocketpair has described Palworld's concept in those terms: ARK-style survival with dinosaur-like companions, plus Breath-of-the-Wild-style tasks, plus collectible Pals. In engine terms that meant: if ARK needed UE4 to tame 194 dinosaurs, Palworld would need UE5 to employ 287 Pals.

What UE5 actually is

Unreal Engine 5 was revealed May 13, 2020, in early access May 26, 2021, and formally released April 5, 2022, with stable 5.8 in June 2026. It supports Windows, Linux, macOS, PlayStation 4/5, Xbox One and Series X/S, Switch and Switch 2, iOS and Android, is written in C++ and is source-available on GitHub under a royalty model. Epic charges 5% of revenues over US$1 million, waived for Epic Games Store exclusives.

Three systems do most of the work for Palworld, and they are not the ones marketing trailers emphasize:

World Partition splits large maps into partitions and streams only needed cells from fast SSDs, decreasing loaded level size. Palworld's Palpagos Islands, with towers as boss arenas, wildlife sanctuaries, villages, factories and 32-player bases scattered across the map, maps directly onto partitions plus fast-travel points.

Chaos and Niagara replace PhysX for physics and handle fluids and particles. When 20 Pals chop trees, haul ore, water crops and fight syndicate troopers in the same base, Chaos is what keeps crates, Pal Spheres and knocked-out humans from tunneling through walls.

Nanite and Lumen handle geometry and light. Nanite is virtualized geometry that auto-manages level of detail in 128-triangle meshlets, accepting photogrammetry, ZBrush and CAD assets without manual retopology. Lumen is dynamic global illumination and reflections with software and hardware ray tracing, removing precomputed lightmaps. Fortnite was Epic's testbed, updated to UE5 in December 2021, followed by early UE5 titles like Remnant 2 and Layers of Fear remake in 2023.

For Palworld, Nanite and Lumen are nice but secondary. The game does not live or die on scanned temples. It lives or dies on whether 100 working Pals can path, eat, sleep and fight without desyncing a 32-player server.

What Palworld gained from renting

Palworld is third-person, with hunger, tools, technology-tree unlocks, base building as fast travel, Pal Spheres in multiple tiers, black-market merchants, Pal trading, Partner Skills unlocked by crafted equipment for mounts and weapons, and even capture of human NPCs with far lower work stats. Bosses are tower-dwelling Tamers from factions like Rayne Syndicate, Free Pal Alliance and Brothers of the Eternal Pyre, with a wanted system where crimes spawn defense troopers until you are killed or evade.

UE5 maps onto that design in four concrete ways:

  1. Taming without writing taming. ARK proved UE could replicate knock-out, passive feeding, mini-game and rideable states for 194 creatures. Palworld reuses that lineage for 287 Pals with type-based work suitability — planting, watering, kindling, generating, mining, crafting — plus Partner Skills. You do not write a networked monster state machine from scratch; you extend Epic's character, AI controller and replication graph.

  2. Bases as factories, not houses. Steam's pitch is explicit: put an army of Pals on pyramid construction, build a factory, place a Pal inside and it works until fed or dead, automate with disassembly lines and butcher knives for loot rolls. That is RimWorld pawns with Pokémon skins. UE5 behavior trees, navmesh, perception and replication let a Craftopia team fake a colony sim without writing a colony engine.

  3. Mounts for free. Pals can be mounted to traverse land, sea and sky. Flying, swimming and climbing mounts are standard UE character movement modes plus replicated mounts. For a small team, owning traversal on day one beats tuning custom controllers for 287 skeletons.

  4. Cross-platform shipping. Windows plus Xbox One plus Series X/S at early access, PS5 eight months later, macOS after that. UE5 supports all of those from one codebase. A custom engine would have forced Pocketpair to port renderer, physics and online subsystems per platform while also fixing survival balance.

The commercial result is verified: 15 million copies in the first month, enough to launch Pocketpair Publishing in January 2025 to fund other indies, starting with Surgent Studios' Dead Take. In July 2024 Pocketpair formed Palworld Entertainment with Sony Music Japan and Aniplex for licensing, and in October 2024 partnered with Krafton where PUBG Studios adapts Palworld for mobile.

What it cost, honestly

The same stack explains every common complaint:

  • CPU and server cost, not GPU beauty. Palworld's stutter is rarely Nanite overload. It is 32 players plus dozens of working Pals ticking AI, hunger, production and physics on a dedicated server, then replicating to clients. No Lumen toggle fixes pathing. Players who expect UE5 to mean crisp 60 fps like a corridor shooter misunderstand the bottleneck: the game simulates a factory, not a hallway.

  • Jank as gameplay tax. Pals stuck on roofs, Pals refusing to water, Pals falling through foundations, humans captured with useless stats. Chaos plus navmesh on player-built geometry will always produce edge cases. Pocketpair patches them, but the architecture guarantees new ones every time players invent a new factory layout. That is the price of letting players build anywhere with autonomous workers.

  • Legal exposure from renting mechanics, not code. On September 19, 2024 Nintendo and The Pokémon Company sued Pocketpair in Tokyo District Court for patent infringement over throwable capture devices, whether a thrown object initiates combat or capture, and riding creatures, seeking an injunction and 10 million yen plus fees. Pocketpair said it would defend. Using UE5 does not protect game-design patents. If anything, using a standard engine makes the allegedly infringing interaction — throw sphere, roll capture, summon mount — easier to compare.

  • Royalty and roadmap dependence. Source-available is not free. Commercial use carries royalties, and Epic sets Nanite, Lumen, Chaos and World Partition roadmaps. Pocketpair traded engine R&D for Epic dependency, which is rational for a first survival hit but means future performance fixes often wait on Epic releases.

In short: UE5 bought ARK-scale systems for an indie team, at the price of server-scale headaches and a courtroom sequel.

My reading: four differences from the usual take

Most summaries stop at Pokémon with guns on Unreal. That misses why this bet worked and when it would fail. These are interpretations, not Pocketpair statements.

1. Palworld rented an MMO scaffold, not a beauty filter. Black Myth: Wukong used UE5 for Nanite temple density. Palworld uses UE5 for replication, World Partition streaming and AI. My contrarian claim: if Epic had shipped UE5 without Nanite and Lumen but with better dedicated-server tooling, Palworld would still have picked it, while Wukong would not. Beauty is optional here; 32-player factory simulation is not.

2. The moat is work suitability, not creature count. 287 Pals sounds like content bloat. I think the real design is a job board: kindling, watering, planting, generating, mining, cooling, farming. Each Pal is a worker with a type tag. That turns collection into automation tech-tree progression — you catch not to complete a Pokédex but to unlock the next factory. Anyone can clone cute monsters in Unity or Godot; few will balance 287 workers against hunger, sanity and power grids. The spreadsheet is the moat.

3. Pathing jank is RimWorld storytelling, not just bugs. In a pretty UE5 action game, a stuck companion breaks immersion. In Palworld, a Relaxaurus napping in the furnace while berries rot is a story players clip and share. The same Chaos-navmesh failures that look amateur in a corridor become comedy in a colony. Pocketpair benefits from genre expectations: survival-factory players forgive AI stupidity if the factory still produces. That forgiveness is structural, not accidental.

4. Small-team UE5 works when you say no to cinematics. Pocketpair did not chase MetaHumans, motion capture or ray-traced cutscenes. It spent UE5 savings on quantity: more Pals, more recipes, more towers, more biomes. Compare to teams that rent UE5 then burn it on one photoreal city. My rule: if your hook is verbs times nouns — capture times craft times automate — UE5 is leverage. If your hook is one perfect face, UE5 is a trap that eats your headcount.

If you disagree, that is the point. The facts above are sourced; these four are a lens to test against your own project.

What indie developers can steal

Do not copy use UE5. Copy the decision rule:

  • Pick UE5 when differentiation is systems count. If your hook is 200+ autonomous agents, rideable creatures, player-built factories and 32-player servers, World Partition plus replication plus behavior trees save years. Palworld, ARK: Survival Ascended and Fortnite all fit.

  • Avoid UE5 when reach is the hook. If you need browser play, integrated graphics, 500-player shards or 200 MB downloads, boring stacks win: vanilla JavaScript for 2048, Node plus WebSockets plus Canvas for Agar.io, LibGDX plus Java for Slay the Spire, or Godot for Brotato. Palworld explicitly abandoned that audience and pays server bills instead.

  • Budget for AI tick, not just pixels. Plan navmesh budgets per base, LOD for worker AI, dormancy for off-screen Pals, and replication limits per dedicated server from month one. Profile with 100 workers active, not with one hero Pal in an empty field.

  • Scope to partitions and job types. If you have under 100 people, prefer one island with tower checkpoints and clear work types over a continent. Name partitions as biomes and factions — Rayne, Free Pal, Eternal Pyre — players read streaming boundaries as lore if pacing is good.

Checklist before you commit: can you name three worker systems that justify UE5 over Unity or Godot; do you have a dedicated-server owner; have you tested 32-player base raids on min-spec; do you have a Chaos physics budget per factory; can you afford Epic royalties and patent risk review.

Train the loop in a browser first

You cannot practice Palworld without a PC or console, but you can train the underlying skills that make its factory-tamer loop work: creature raising, mount control and survival building.

For raising and riding a creature instead of just catching it, Dragon Simulator 3D is the closest free trainer. You pick fire, ice, nature or air, learn Q take-off, Space climb and breath-then-tail combos, earn stars and gold through quests, and grow a clan with mates and dragonets. It inverts Palworld: you are the Pal learning hit-and-run passes, terrain use and when to retreat, which teaches why Partner Skills and mount stamina matter before you automate them.

For the other half — hunger, torches, crafting tables and first-night shelter — Mine Clone helps. You punch trees for logs, turn them into planks and tools, upgrade wood to stone to iron, farm with hoes, and survive spiders and zombies after sunset. The guide is explicit: shelter before sunset, torches to block spawns, never dig straight down. That is exactly Palworld's day-one loop without the Pals doing it for you.

For mount stamina and herd management, try Horse Simulator 3D. You roam an island, manage speed versus endurance, complete delivery and gathering quests, raise foals and decorate a home that shelters the herd. It is calm where Palworld is frantic, but judging gallop distance, conserving endurance and deciding when to expand the family maps directly to routing and Pal-base staffing.

None of these are Palworld in a browser. They are cheap reps for the reflexes Palworld taxes at full price: tame, ride, build, automate.

Bottom line

Pocketpair did not out-engine Epic. It out-scoped everyone else with Epic's engine: 2015 founding, 2020 Craftopia lessons in Breath-of-the-Wild plus Minecraft plus ARK crafting, 2021 Palworld announcement, 2024 early access with 15 million copies in a month, 2024 PS5 and mobile deals, 2026 full release. The lesson for small teams is not to fear borrowed tech, but to spend the savings on something unclonable — in this case, 287 working Pals as automation — while budgeting openly for server, pathing and legal costs.

Watch the lawsuit and mobile port to test the theory. If Pocketpair keeps UE5 and ships faster with similar systems density, the scaffold worked. If server and patent costs dominate, the factory tax is structural.

Top comments (0)