Borderlands 4 development context, engine choice, and what the franchise’s next entry means for the production pipeline
A new mainline Borderlands entry always forces a recurring question inside the looter shooter genre: how does a studio preserve the cel-shaded art, randomized loot, and cooperative shooting loop that defined the series while rebuilding the underlying engine, world structure, and platform footprint for a new hardware generation. Borderlands 4 sits inside that tradition. The release marks Gearbox’s first fully Unreal Engine 5-driven mainline Borderlands entry and the first designed around a true open-world structure rather than the segmented hub maps of Borderlands 3, so the production decisions behind it touch level design, streaming, combat pacing, and live operations in ways the previous games did not have to address at the same scale.
This article treats Borderlands 4 as a production and technology topic. It does not try to be a player guide, a review, or a rumor roundup. The goal is to give developers, technical artists, and producers a working understanding of the engine shift, the open-world streaming model, the platform and certification footprint, the procedural loot pipeline, the co-op and networking model, and the post-launch structure that the franchise’s 2025 entry has been described as carrying. Where the article discusses specific facts about the game, it limits itself to claims that are confirmed by primary sources or by the verified reporting referenced at the end. Where the discussion is editorial reasoning about how those decisions typically play out in production, it labels that reasoning as such so it can be distinguished from verified information.
Readers who want a broad breakdown of the franchise’s history before reading the production analysis can use the Borderlands 4 Wikipedia entry as a cross-reference, since it consolidates the release window, publisher, and platform information in one place. For studio-level context on how a mid-sized team approaches an engine migration of this scope, the Verge’s report on the 2025 launch and the production pivot describes the development situation in concrete terms and is worth reading before drawing conclusions about scope, budget, or risk.
What changed for Borderlands 4 at the engine layer
The most consequential technology decision behind Borderlands 4 is the move to Unreal Engine 5 as the foundation for the full game, including the cel-shaded renderer, the streaming world, and the cooperative netcode. Previous Borderlands titles were built on a heavily modified version of Unreal Engine 3, which the team at Gearbox carried forward through three mainline releases and several spin-offs. That decision bought the studio a great deal of art and tooling continuity. It also meant that the renderer, the animation system, the audio mixer, and the streaming infrastructure were all working against assumptions from a 2006-era engine.
Switching to Unreal Engine 5 gives Borderlands 4 access to a modern renderer, a more flexible animation graph, a newer audio engine, and a world-partitioning toolset that did not exist when the franchise’s previous entries were designed. The trade-off is that the cel-shaded look, the heavy use of outline passes, the exaggerated silhouette language, and the asset-dense combat arenas that the series is known for all have to be re-implemented on top of a renderer with a different default set of assumptions. The stylized pipeline that the art team developed for Borderlands 3 was designed for forward rendering, per-object outline passes, and a relatively small set of decals layered on top of baked lighting. On Unreal Engine 5, the team has to decide how much of the silhouette language moves to a post-process material, how much stays in the geometry and outline pass, and how the Nanite and Lumen systems are used without flattening the look.
From a production standpoint, that kind of migration is rarely a one-to-one port. It is closer to a re-authoring pass, in which the art team rebuilds the asset set so that the new renderer treats the materials the way the team intends. Borderlands 4 therefore carries both a content cost (rebuilding the surface library, the weapons, the characters, the vehicles, and the environment kits) and a tooling cost (rewriting the outline pass, the cel-shading material graph, the decal layering system, and the asset validation passes). For a studio of Gearbox’s size, that is a multi-year effort that overlaps with design, content production, and platform certification rather than a clean sequential pipeline.
Open-world streaming replaces segmented hub maps
The second structural change for Borderlands 4 is the move from the segmented hub-map structure that the series has used since 2009 to a continuous open-world region. In previous games, the player traveled between discrete zones connected by loading screens or fast travel. Each zone was a self-contained level with its own streaming budget, its own enemy population, and its own loot tables. The result was a level that was easy to reason about for both performance and content production, but that also asked the player to accept visible seams between areas.
An open-world Borderlands introduces a different set of streaming and visibility problems. The team has to define a world partition that lets the engine keep memory and draw cost predictable as the player moves across the map, while still allowing the studio to author discrete combat encounters, towns, dungeons, and boss arenas inside that partition. In practice that means a layered streaming setup: a low-resolution far terrain that keeps the silhouette readable at long distance, a mid-range level of detail for the playable region, and high-resolution streamed chunks for the immediate play area. The encounter authoring system has to be reworked so that encounters can be triggered by region or by quest state rather than by map load.
| Subsystem | Borderlands 3 approach | Borderlands 4 approach | Production consequence |
|---|---|---|---|
| World layout | Segmented hub maps connected by fast travel | Continuous open-world region with interior zones | Encounter authoring moves to region and quest triggers |
| Streaming | Per-map level streaming | World partition with layered LODs | Memory budget becomes continuous instead of per-zone |
| Cel shading | Per-object outline pass on UE3 | Post-process material plus geometry passes on UE5 | Stylized pipeline rebuilt and re-validated |
| Loot distribution | Per-zone loot tables | World-wide loot pools with regional weighting | Loot economy needs live balance tools, not just tuning data |
| Co-op | Instance-based drop-in sessions | Continuous open-world sessions with instanced interiors | Netcode handles large player counts across a single map |
The table is a production summary, not a design statement. It compares the structural decisions that the team has described in public development material and in pre-release coverage with the structures used in the previous entry. The point is not to claim that any of these decisions are correct on their own, but to make the cost of each transition visible. Every row in the table represents a subsystem that has to be rebuilt, re-tested, and re-certified for a new platform generation, and that effort is what determines the production schedule of an open-world game as much as the content itself does.
Procedural loot and the live balance problem
The Borderlands franchise has always treated loot as a first-class system rather than as a reward layered on top of combat. Borderlands 4 inherits that tradition and extends it in a direction that has consequences for the live operations side of the studio. With a continuous open world, the loot system has to scale across a much larger area and across a wider range of enemy archetypes than in the previous games, and the same item parts that defined Borderlands 3 now have to be combined in larger numbers without producing duplicate-feeling drops.
The general approach the franchise has used is a parts-based generator: each weapon is assembled from a body, a barrel, a grip, a magazine, and a manufacturer-defined accessory, with the parts contributing stats, visual elements, and sometimes unique behavior. For Borderlands 4, the team has been described as keeping that architecture and extending it with regional weighting, which means that the same enemy archetype in a desert region can drop a different weighting of parts than the same archetype in a frozen region. From a balance standpoint, that gives the live team a way to redirect the loot economy without rewriting items, but it also means that any change to a regional weight has to be tested against the rest of the world so that it does not break the global economy.
For a production team, the operational consequence is that the loot designer is no longer the only person who can adjust the loot economy. Tuning a regional weight is a data change that can be deployed without a content build, so the live operations team can run a hotfix in the middle of a season without forcing a patch. The trade-off is that the design team has to maintain a balance model that is expressive enough to allow those tuning passes but constrained enough that a regional change cannot quietly invalidate a build the team has already shipped. That balance model is one of the most underappreciated assets a long-running looter shooter carries, and it is one of the reasons Borderlands 4 can be supported across multiple seasons without a complete item rewrite every quarter.
Co-op, networking, and session model
For additional context, Borderlands has always been a cooperative franchise at its core, and Borderlands 4 has to support drop-in co-op across a continuous open world on current-generation consoles and PC. The session model that the previous games used was an instance-based one: the host’s world was a single instance that other players joined, with a maximum of three other players plus the host. That model scaled reasonably well for a segmented hub map, because the engine could treat the entire session as a single level with a known memory budget.
An open-world Borderlands changes the assumptions. The session now has to remain coherent as the players drive across a large map, fast travel between regions, and enter instanced interiors such as dungeons, vaults, and boss arenas. The networking layer has to handle player teleports caused by fast travel, transitions into and out of instanced zones, and the synchronization of loot drops in a context where two players may be looking at the same chest in two different parts of the map. None of these problems are unique to Borderlands 4, but the combination of an open world, drop-in co-op, and a randomized loot system is unusual enough that the networking model is one of the systems the team has to validate earliest in production.
- Authority model: the host remains the authority for loot rolls and quest state to keep deterministic outcomes, with the client presenting visual and audio feedback for rolls it did not author.
- Latency tolerance: drop-in co-op has to tolerate the connection quality of console players on wireless networks, so the client-side prediction and reconciliation has to be more forgiving than the typical competitive shooter.
- Session persistence: a co-op session has to survive a player disconnect and a reconnect, and a session migration has to move the host without losing quest state or loot state.
- Region streaming: when one player enters a dungeon and the rest stay outside, the dungeon has to stream in and out for each player independently, while the rest of the world continues to simulate.
Each of these points is a known production problem in the genre, and the team has publicly discussed supporting drop-in co-op across the open world. The exact implementation detail of the netcode is not something the studio has published in granular form, and the article deliberately does not guess at the specific replication graph or transport layer the team is using. What can be said is that the production team has to design for these four conditions from the start of the project, because retrofitting co-op onto a single-player streaming system late in production is one of the most expensive mistakes a project of this scale can make.
Platform footprint and certification
Borderlands 4 is shipping on PC and on the current generation of consoles, with the cross-generation support model of the previous entries left behind. That single decision has consequences across rendering, input, and certification. The previous generation of consoles was the floor for the franchise’s last release, and the team had to support a wide range of hardware memory budgets and CPU profiles. On a current-generation-only target, the floor for memory, CPU, and storage is higher, and the team can spend those resources on streaming, draw distance, and content density rather than on the lowest common denominator.
Certification on each platform has its own requirements around suspension, resume, controller disconnection, save data integrity, trophy and achievement integration, and network behavior. The team has to test each of those conditions against a continuous open world, which is harder than testing them against a segmented hub map because the system has more state to save and restore. A typical certification pass for an open-world game covers fast travel during a save, mid-cutscene suspension, mid-combat suspension, network loss during a save, and restore from a partial save. Each of those conditions has to be reproducible on every platform, which is one of the reasons the certification budget for an open-world game of this scale is significantly larger than for the previous entries.
| Platform | Memory target | Certification focus | Operational risk |
|---|---|---|---|
| PC (Steam, storefronts) | Driven by recommended spec rather than a fixed target | Driver variability, anti-cheat integration, DLC delivery, store page metadata | Driver regressions and storefront certification rules change independently of the game build |
| PlayStation 5 | Shared memory budget tuned for the open-world streaming plan | Save integrity, trophy triggers, suspend and resume, controller haptics | Firmware updates can change streaming or input timing in ways that require patches |
| Xbox Series X / S | Two memory profiles require per-profile streaming tuning | Smart Delivery, suspend and resume, accessibility features, network behavior | The lower-memory profile is the binding constraint for streaming and asset resolution |
| Cross-platform play | Not part of the base certification pass | Privacy, voice chat, account linking, parental controls | Cross-platform play policies can change after launch, requiring client updates |
None of the columns in this table should be read as an authoritative statement about the exact memory footprint or certification schedule of the game. They describe the categories of decisions a production team has to make when an open-world looter shooter ships on three current-generation targets plus PC, and they are the kinds of decisions that typically determine the post-launch patch cadence of a long-running live game. The operational risk column is the one that matters most for a live game, because the studio can ship a working day-one build and still spend the first three months of the live cycle addressing platform-specific issues that the certification process does not catch.
Stylized rendering and the cel-shaded art pipeline
The visual identity of Borderlands has always been a stylized one. The franchise uses exaggerated silhouettes, heavy outlines, hand-drawn-feeling texture work, and a saturated color palette that is closer to a graphic novel than to a photorealistic shooter. That look is not free. It is the result of a specific material pipeline, a specific lighting pipeline, and a specific set of post-process passes, all of which have to be rebuilt on a new renderer.
On the previous engine, the team implemented the cel shading as a per-object outline pass combined with a hand-authored diffuse ramp. The outline pass used a depth-driven edge detection, and the diffuse ramp was a low-resolution texture sampled by a per-material function. On Unreal Engine 5, the team can use Nanite for the heavy static geometry, Lumen for the global illumination, and a post-process material for the outline and the diffuse ramp. The result is a different authoring workflow, a different validation workflow, and a different performance profile for the same visual effect.
The production consequence is that the art team has to rebuild the surface library, the weapon material set, the character material set, and the environment material set so that they all work with the new pipeline. That is a large amount of work, but it is also an opportunity. The new material graph is more flexible than the old one, so the team can introduce visual variation that was not possible on the previous engine, including more nuanced material zones on a single weapon, more dynamic wear patterns, and more granular control over how a surface catches light. None of those features are guaranteed in the final product, but they are the kind of improvements that a renderer migration makes possible when the art team is given the time to use them.
Performance budget, frame pacing, and platform targets
An For additional context, open-world Borderlands is a more demanding game than the previous entries, and the team has to manage that demand against a frame budget on every platform. The typical approach for a current-generation open-world game is to target a 60 fps mode and a 30 fps mode on consoles, with a higher frame target on PC depending on the hardware. The exact target for Borderlands 4 is a question the studio has to answer during the optimization phase of production, and the article deliberately does not assert a number that has not been publicly confirmed.
What can be said without overspecifying is the shape of the optimization work. The team has to measure the cost of the streaming, the cost of the cel-shaded post-process, the cost of the enemy AI simulation, the cost of the loot generator, and the cost of the networking layer independently, and then has to measure them together under the worst-case conditions of a four-player co-op session in a dense area. The optimization pass typically runs in three waves: a per-system pass that brings each subsystem into its own budget, a cross-system pass that finds the interaction effects, and a platform-specific pass that tunes each build for its target hardware.
- CPU budget: split between the streaming thread, the game thread, the AI thread, and the networking thread, with a measured worst case for each.
- GPU budget: dominated by the cel-shaded pass, the lighting, the particle effects, and the post-process stack, with a measured worst case for dense combat.
- Memory budget: split between the world partition, the streaming chunks, the asset cache, the audio cache, and the loot database, with a measured worst case for fast travel.
- Storage budget: the day-one build plus the planned post-launch content has to fit on the target storage media, which on consoles is a binding constraint.
The optimization pass is one of the parts of production that a player will never see directly, and it is one of the parts that most determines whether a launch build feels stable. A team that runs the cross-system pass before the platform-specific pass will ship a build that feels uneven, because the worst-case interactions will only show up in the worst-case scenarios. A team that runs the platform-specific pass first will ship a build that feels over-tuned on a single platform but is not ready for the others. The production discipline is to run all three passes in the right order, and that discipline is one of the things that distinguishes a stable open-world launch from a launch that has to spend its first month chasing platform-specific crashes.
Live operations, seasons, and post-launch structure
Borderlands 4 is positioned as a long-running live game, with a seasonal content cadence and a series of post-launch updates. The exact shape of that cadence is determined by the live operations team, but the production infrastructure has to be in place from the start. The team has to ship a build that can be patched without forcing a full client update, a build that can carry new content without breaking the existing save data, and a build that can run a season pass without a content patch that breaks the loot economy.
The infrastructure for a live game of this scale is significant. The team needs a content delivery pipeline that can ship new missions, new weapons, new areas, and new vault hunters without requiring a full client patch, a balance pipeline that can change the loot economy without breaking the existing items, a certification pipeline that can ship platform-specific patches without re-running the full certification pass, and a telemetry pipeline that can measure the player behavior across the new content. None of that is visible to the player, and all of it has to be in place before the first season starts.
From a business standpoint, the live operations layer is what justifies the production cost of an open-world Borderlands. A single-player game of this scale has to recover its production cost at launch. A live game can spread that cost over multiple seasons and multiple years, but only if the live operations layer is built well enough that the players keep coming back. The Borderlands franchise has historically had a strong live operations record, and the production decisions for Borderlands 4 are the ones that determine whether that record continues.
Accessibility, localization, and the wider production footprint
An open-world Borderlands on three current-generation platforms and PC has a localization and accessibility footprint that is significantly larger than the previous entries. The localization work is the easier part to estimate: each line of dialogue, each mission description, each item description, each UI string, and each piece of environmental signage has to be translated, and the translation has to be reviewed for the same content. For a game with the dialogue volume of a Borderlands entry, that is a multi-month effort that starts well before the content is locked.
The accessibility work is the harder part to estimate, because the requirements vary by platform and by jurisdiction. The team has to support configurable input, configurable difficulty, configurable subtitles, configurable color and contrast settings, configurable audio mixing, and configurable motion settings. Each of those settings has to be implemented in the input layer, the rendering layer, the audio layer, and the UI layer, and each of those implementations has to be tested against the same content. The cost of that work scales with the number of platforms and with the number of content updates, so the live operations layer has to maintain the accessibility settings across the seasonal updates as well.
For a production team, the operational lesson is that accessibility and localization are not a phase that happens at the end of production. They are a set of decisions that have to be made at the design phase, because retrofitting an accessibility setting onto a system that was not designed for it is more expensive than building it in. The same is true for localization, because a string that is hard-coded into a material is harder to localize than a string that is read from a data table.
What Borderlands 4 tells us about the franchise’s direction
Taken together, the production decisions behind Borderlands 4 are a statement about the direction of the franchise. The engine migration, the open-world structure, the seasonal live operations, and the platform footprint all point in the same direction: the studio is treating Borderlands as a long-running live game on current-generation hardware, and the production decisions are being made to support that model rather than to support a one-time single-player release.
For developers, the most useful takeaway is that the engine migration and the open-world structure are not independent decisions. They are two parts of a single plan to rebuild the franchise’s technical foundation so that the studio can support a long-running live game without being limited by the previous engine. The cel-shaded look, the loot system, the co-op model, and the seasonal content cadence are all being rebuilt on top of that foundation, and the production cost of the rebuild is what determines the post-launch support window.
For players, the takeaway is that the experience of the game at launch is the start of a longer arc, not the end of one. The first season of content, the first balance patch, and the first post-launch update are all part of the same production cycle, and the decisions that determine them are being made during the development of the base game. The base game has to be good enough to carry the live operations layer, and the live operations layer has to be good enough to carry the post-launch arc.
For studios considering a similar migration, the most useful takeaway is the cost of doing the rebuild. The engine migration is not a one-time cost that is paid once and then forgotten. It is a multi-year effort that overlaps with content production, platform certification, live operations, and post-launch support, and the team has to plan for all of those at the same time. The studios that handle the migration well are the ones that treat it as a structural change rather than a technical one, and the studios that handle it poorly are the ones that treat it as a render upgrade rather than a rebuild.
Frequently asked questions
What engine is Borderlands 4 built on?
Borderlands 4 is built on Unreal Engine 5, which is a structural change from the heavily modified Unreal Engine 3 codebase that the previous mainline entries were built on. The migration gives the studio a modern renderer, a more flexible animation graph, and a world-partitioning toolset, but it also requires the cel-shaded pipeline, the outline passes, the loot generator, the co-op netcode, and the asset library to be rebuilt for the new engine.
Is Borderlands 4 an open-world game?
Borderlands 4 is the first mainline entry in the franchise designed around a continuous open-world region rather than the segmented hub maps that the previous games used. The transition changes the streaming model, the encounter authoring system, the co-op session model, and the loot distribution, and it is one of the structural decisions that drives the production schedule.
Which platforms is Borderlands 4 on?
Borderlands 4 is shipping on PC and on the current generation of consoles, with the cross-generation support model of the previous entries left behind. The current-generation-only target gives the studio a higher floor for memory, CPU, and storage, and it removes the lowest-common-denominator constraints that shaped the previous entries.
Does Borderlands 4 support drop-in co-op?
Drop-in co-op is a core part of the franchise, and Borderlands 4 has been described as supporting co-op across the open world. The networking layer has to handle player teleports from fast travel, transitions into and out of instanced interiors, and the synchronization of loot drops across a single map, and those conditions are part of the certification and platform test plan.
How is loot generated in Borderlands 4?
The loot system is built around a parts-based generator that the franchise has used for several entries, with the addition of regional weighting in Borderlands 4. Each weapon is assembled from a body, a barrel, a grip, a magazine, and a manufacturer-defined accessory, and the parts contribute stats, visual elements, and sometimes unique behavior. Regional weighting lets the live team direct the loot economy without rewriting items, but it also requires a balance model that constrains the impact of any single tuning pass.
What is the visual style of Borderlands 4?
The franchise uses a stylized cel-shaded look with exaggerated silhouettes, heavy outlines, hand-drawn-feeling texture work, and a saturated color palette. On Unreal Engine 5, the cel shading is implemented as a post-process material plus per-object geometry passes, and the art team has rebuilt the surface library, the weapon material set, the character material set, and the environment material set to work with the new pipeline.
Will Borderlands 4 have seasonal content after launch?
Borderlands 4 is positioned as a long-running live game with a seasonal content cadence, and the production infrastructure is built to support that model. The content delivery pipeline, the balance pipeline, the certification pipeline, and the telemetry pipeline are all in place before the first season starts, and the team has to maintain them across the post-launch arc.
How does Borderlands 4 handle platform certification?
Certification on each platform covers suspension, resume, controller disconnection, save data integrity, trophy and achievement integration, and network behavior. For an open-world game, the certification pass also has to cover fast travel during a save, mid-cutscene suspension, mid-combat suspension, network loss during a save, and restore from a partial save, and each of those conditions has to be reproducible on every platform.
What are the main production risks for Borderlands 4?
The main production risks are the engine migration cost, the open-world streaming cost, the co-op netcode cost, the platform certification cost, and the live operations cost. Each of those risks is structural rather than incidental, and each of them is part of the same production plan rather than a separate concern.
Where can I find a broader background on the franchise?
For a consolidated overview of the release, the publisher, and the platform information, the Borderlands 4 Wikipedia entry is a useful cross-reference, and the Verge’s 2025 launch report provides a development-side perspective that complements the production analysis above. For readers who want to dig into the studio’s broader service work, the app game development team guide and the iOS game development guide cover adjacent production topics from a different angle.
Leave a Reply