Ghost of Yotei: production notes on Sucker Punch’s open-world sequel
A long, snowed-over ridge, a single wind-bent tree, a masked rider drawing a katana in the half-light before dawn. That visual shorthand is what most players already carry into the conversation around Ghost of Yōtei, the next major single-player project from Sucker Punch Productions. The studio’s previous work on Ghost of Tsushima established a clear production template: an open-world action game set in a specific historical region, a focused melee combat system, a stylised art direction that treats the landscape itself as a character, and a single-player experience shipped without multiplayer or live-service obligations. Ghost of Yōtei sits on top of that template and changes several important variables at once. New region, new protagonist, new combat stance toolkit, and a noticeably different production context inside the studio.
This article is a GameDev-focused breakdown of Ghost of Yōtei as a production project rather than a consumer preview. The aim is to read the publicly available information about the game, the studio’s previous workflow on Ghost of Tsushima, and the production commentary that has emerged around Ghost of Yōtei, then translate that into practical observations about open-world action design, combat system architecture, world-building pipelines, team structure, and the editorial trade-offs that follow from a sequel of this scale. Where a fact is confirmed by the developer, it is treated as confirmed. Where a piece of information is a reasonable production inference from prior work, it is flagged as editorial reasoning. The goal is to give game developers, technical artists, producers, and students a useful map of how this kind of open-world action project actually gets made.
What Ghost of Yōtei is, and what it inherits from Ghost of Tsushima
Ghost of Yōtei is a single-player, open-world action game developed by Sucker Punch Productions, set roughly three hundred years after the events of Ghost of Tsushima. Instead of Tsushima Island in 1274, the game takes place in the lands around Mount Yōtei in what is now Hokkaido, with protagonist Atsu stepping into a role that echoes but does not duplicate Jin Sakai’s. The core fantasy is the same: a wandering sword figure in a stylised historical Japan, with the player free to roam, duel, and explore at their own pace. The structural DNA is also familiar: open-world map segmented into regions, a quest log structured around tales and side stories, melee combat built around stance switching, a wind-driven navigation system, and a stance-based duelling system that is widely considered one of the more readable melee systems of its generation.
What the sequel changes is just as important. Atsu is not a samurai in the same social sense as Jin, and the combat system in Ghost of Yōtei is built around a broader weapon set that includes dual swords, a katana, a spear, and a kusarigama-style chain weapon. The new stance system is less about adapting to enemy type and more about expressing playstyle. Mount Yōtei itself sits in a different climate and elevation profile from Tsushima, which carries through to the world team, art direction, and the kind of traversal the map is designed around. For a developer reading the project, the interesting question is not “is it Tsushima but different” but “which production pieces of the original system scale up, and which have to be redesigned”.
This is where the public production commentary matters. DigiPen’s student-facing showcase feature on producing Ghost of Yōtei, written around producer Maria Bourg’s talk, gives a useful window into how Sucker Punch thinks about the difference between shipping a strong original and shipping a strong sequel. The framing there is that a sequel cannot simply be “more of the same”; it has to identify which systems made the original work and which need to be rebuilt around the new setting and protagonist. That is the editorial frame this article uses throughout.
How Sucker Punch structured the open-world production
Ghost of Tsushima shipped with around forty hours of content in a single-player package, and a significant proportion of that was the open-world layer: discoverable points of interest, fox dens, bamboo strikes, hot springs, Inari shrines, and a non-player character ecology that gave the map a sense of inhabited space. None of that is free, and Sucker Punch has talked about the team structure that delivered it. The world team was large and long-running, the combat team was small and iterated in tight cycles, and the cinematics team had to operate against a real, navigable in-engine world rather than a controlled set. Ghost of Yōtei inherits that structure and is widely reported to be a noticeably larger project, partly because the studio has grown since 2020 and partly because the Hokkaido setting introduces heavier weather, elevation, and foliage work.
| Production layer | Inherited from Tsushima | Rebuilt for Yōtei | Implication for the team |
|---|---|---|---|
| World layout and navigation | Region-based open world, wind-based guidance | Different terrain profile, denser elevation change | Environment art and level design spend more time on vertical paths |
| Combat core | Stance switching, parry, dodge, resolve | Broader weapon set, stance as expression | Combat team grows but state count grows faster than headcount |
| Cinematics | In-engine real-time, environmental storytelling | More interior and weather-driven scenes | Cinematics team needs stronger lighting and weather control |
| Quest and narrative | Tales and side stories, world-building through NPCs | New protagonist, new era, new factions | Narrative and quest design reset while tools carry over |
| Audio | Diegetic wind and ambient layering | Snow, blizzard, deeper acoustic mix | Audio team rebuilds mix around new weather and surface set |
The table above is an editorial summary based on the studio’s previously documented workflow and the publicly known changes for the sequel. It is not an internal production document, and the actual team shapes inside Sucker Punch are not public. The value of reading the project this way is that it makes clear which production lines were simply “turned on again” and which had to be reopened and retooled. The combat core is the most interesting case, because it is the part of the game the player feels most directly and the part that benefits least from a pure content push.
Combat system design in Ghost of Yōtei
The original Ghost of Tsushima combat system was a study in readable, stance-based melee. Players picked one of four stances, each tuned to a specific enemy class, and switched between them on the fly. The system earned a reputation for being clean and elegant: a small number of verbs, a clear feedback loop, and animation that made every parry feel weighty. The sequel keeps the verb set recognisable but changes the role of stance. Instead of “the right tool for the right enemy”, stances in Ghost of Yōtei act more like a loadout choice that expresses how the player wants to approach combat, with weapons that have a distinct tempo, range, and punish profile.
For a developer, the interesting production question is what that does to the state machine and to the animation budget. Stance-as-tool means relatively few enemy-specific overrides and a clean state graph. Stance-as-loadout means more animation variants per weapon, more oni-style combo trees, and more careful balancing around which stance is the “best” for a given encounter. The risk is homogenisation: if every weapon can solve every encounter, stances stop meaning anything. The mitigation is content design that gives each weapon a small set of enemies or situations where it feels obviously better, even if it is not technically required.
Three production priorities tend to follow from this design choice:
- Animation throughput: a broader weapon set means a much larger animation library per character, and the team has to plan mocap capture and cleanup capacity around the new weapons before they lock gameplay direction.
- Enemy variation: if stance is loadout-driven, enemies need internal variation that rewards different play patterns. The team has to spend time on enemy archetypes that have attack patterns suited to different reach, guard, and tempo profiles.
- Player feedback: the player needs to feel the difference between weapons on every hit, not just in the stats screen. That pulls the audio, animation, haptics, and UI teams into the combat design conversation earlier than on a more stance-uniform system.
None of this is unique to Ghost of Yōtei, but the game is a useful case study because the prior system was so well-defined that the differences stand out cleanly.
Open-world production at this scale
Open-world action games are unusual production objects because the player can be in any of several thousand hand-authored spaces at any moment, and every one of those spaces has to be valid in audio, lighting, performance, and gameplay terms. A studio cannot author a world of that size with a single discipline; the world team is essentially a federated system of environment artists, level designers, technical artists, lighting artists, audio designers, and gameplay scripters, all working in the same spatial container. The cost of an error in any one of those layers can cascade across the whole team. A new traversal ability, for example, changes which surfaces need to be authored as climbable, which changes the navigation mesh, which changes where ambient audio is placed, which changes where cinematics can be triggered.
Ghost of Tsushima’s team had already learned most of these lessons. The new Hokkaido setting adds two more. First, the elevation profile is more dramatic, which means a larger fraction of design time is spent on vertical paths and the moment-to-moment feel of climbing, riding up a slope, or descending into a valley. Second, the climate and weather work is heavier. Snow and blizzard are not just visual effects; they change line of sight, surface audio, NPC behaviour, and the player’s perception of distance. For a team that built its reputation on golden-hour photography of feudal Japan, the move into deeper weather is a deliberate production risk.
| Production challenge | What it looks like in-engine | Why the sequel makes it harder | Typical mitigation |
|---|---|---|---|
| Vertical world | Climbable surfaces, anchor points, horse paths | More elevation change than Tsushima | Path-based traversal tools, slope-aware animation |
| Weather and visibility | Particle systems, fog, post-process | Snow, blizzard, storm lighting | Layered weather, dynamic audio occlusion |
| World density | Points of interest, ambient NPCs | Larger playable area | Procedural placement with hand-authored anchoring |
| Performance budget | Frame time, draw calls, streaming | New environment, new effects | Aggressive LOD, asset sharing, streaming |
| Narrative anchoring | Quest triggers, scene volumes | New factions and tales | Stronger quest-to-region mapping |
The right way to read a table like this is not as a checklist but as a set of dependencies. A team that gets vertical traversal right early in production buys itself room to author elevation-driven content later. A team that treats weather as a final-pass polish task usually ends up with weather that is beautiful but does not interact with gameplay. For additional context, Ghost of Yōtei’s setting almost forces the team to make weather and elevation a first-class part of the world, because the visual identity of the game is built on them.
Tools, pipelines, and what carries over
Most of the tools a studio builds for a project of this kind are not visible to the player, and most of the production risk lives in them. Custom level editors, asset validation passes, audio placement tools, navigation mesh generators, cinematic sequencers, and the scriptable event systems that drive quest logic are all part of the studio’s internal engine layer. The reason a sequel is cheaper than a new IP is that those tools carry over. The reason a sequel can still slip is that the new game breaks assumptions those tools were built on.
Three pipeline concerns stand out for Ghost of Yōtei, based on the studio’s previous work and the public changes for this project.
- Asset reuse versus asset retirement. The visual identity of the new setting is different enough that much of the Tsushima vegetation, architecture, and prop library will be retired, but the underlying material and shader systems will carry over. The team has to decide early which assets are re-skin opportunities and which need full rebuilds.
- Quest scripting depth. The original game had a reputation for expressive but contained quests. The sequel’s broader weapon set and new protagonist give the quest team room to script more varied encounters, which in turn puts pressure on the quest scripting tools to be readable and debuggable at a larger scale.
- Cinematic in-engine fidelity. Tsushima shipped with very high-quality in-engine cinematics, and the standard for that has only risen. The cinematic team has to hit a quality bar that is at least as high, in a new setting, with more weather and interior lighting variation.
None of these are blockers, but they all compete for the same limited tooling time. The teams that handle this best are usually the ones that treat tooling as a shared product, not as a side activity of the discipline that happens to own a tool.
Art direction, lighting, and the Hokkaido visual language
Ghost of Tsushima’s art direction is one of the most studied open-world visual systems of the last several years. The Kurosawa Mode toggle, the wind-driven foliage, the long sight lines, the heavy use of golden-hour light and silhouette, and the careful control of clutter on screen all combined into a look that was both stylised and readable. The sequel does not throw that language away, but it changes the colour temperature and the dominant weather. The Hokkaido setting pulls the palette cooler, the light harsher in places, and the weather a much more active participant in any given frame.
For a technical artist, this is a quietly expensive change. Cool light, snow surfaces, and high-elevation environments place different demands on exposure systems, on shadow bias, on screen-space reflections, and on the way particle systems interact with light. Snow is also one of the most expensive surfaces in any open-world game because it interacts with both lighting and animation; a footstep in snow has to leave a footprint, and the snow surface has to be treated as a partially destructible layer if the game wants to feel grounded. Studios that ship a snowy world usually spend more on technical art than on pure environment art because so much of the visible magic is in the interaction between systems.
The art direction also has to be honest about what the new setting can and cannot do. Hokkaido is not a feudal Japan setting in the same way that Tsushima is. The Ainu cultural context is significant, and the studio has been careful to consult and credit that. That affects everything from character design to architecture to the kinds of locations that can be on the map. For a developer working on a culturally anchored open-world game, this is a useful reminder that art direction is also a research direction.
Audio design: wind, snow, and the new acoustic profile
Ghost of Tsushima’s audio design was diegetic-first. Wind carried the player, the environment told the player where to go, and the combat mix was clear without being loud. The sequel’s acoustic profile has to do all of that in a colder, more weather-driven world. Snow absorbs sound differently from grass or sand, blizzard conditions distort both the player’s perception of distance and the mixer’s ability to deliver clean audio cues, and the broader weapon set means more variety in the per-weapon sound design.
Audio in an open-world game of this size is essentially a real-time mixing problem with thousands of sources competing for attention. The audio team has to balance the moment-to-moment readability of combat with the longer-form atmosphere of exploration. A snowstorm is great for atmosphere but bad for combat readability, and a useful production test is whether the player can still hear the difference between a sword strike and a parry at the peak of a blizzard sequence. The answer drives a lot of decisions in the audio mix, the dynamic range of the master, and the way the combat team scripts encounters in bad weather.
Three audio priorities tend to dominate on a project like this.
- Surface variety: every new weapon and every new surface adds combinations, and the team has to design the most important ones explicitly rather than relying on system-driven randomisation.
- Weather-driven occlusion: a blizzard changes how audio travels, and the system has to model that without making the world feel broken when the storm passes.
- Music layering: the original game was praised for its restrained score. The sequel has to keep that discipline while covering a longer runtime and a more varied emotional range.
Quest and narrative design in a new era
Tsushima’s narrative design worked because the world and the protagonist were tightly aligned. Jin’s story, the samurai-versus-samurai conflict, and the island setting reinforced each other. The sequel breaks that alignment deliberately by changing the era, the region, and the protagonist. Atsu is a wanderer in a more fragmented conflict, and the world has to carry a different kind of story. The narrative team has to find new anchors for player motivation, new factions that feel distinct, and new kinds of tales that justify the size of the map.
The production lesson is that narrative design is not a writing problem; it is a world design problem. A quest that lands well usually has a strong spatial component: a location that justifies the trip, an NPC who is in the right place, and a scene that uses the environment. In a sequel with a new setting, all of that has to be rebuilt, which is one of the reasons narrative-heavy open-world sequels tend to be long projects even when the combat system is already mature.
| Narrative layer | Role in the game | Production owner | Sequel-specific change |
|---|---|---|---|
| Main tale | Carries the protagonist arc | Narrative director, lead writer | New era, new protagonist motivation |
| Region tales | Anchor each major area | Quest design and writing | New factions and conflicts |
| Side tales | World texture and character beats | Distributed quest team | More interior and weather-driven scenes |
| Worldbuilding NPCs | Ambient life in the map | World and audio teams | Cultural anchoring for new setting |
Reading the narrative layer this way helps explain why a sequel can be expensive even when the studio has a mature pipeline. The tools carry over, but the content has to be rebuilt, and the rebuild touches every discipline that contributes to the world.
Team structure, leadership, and how a sequel changes the org chart
Sucker Punch has been a relatively flat, multi-project studio at points in its history, but during the long tail of a single-player open-world project the structure usually becomes more hierarchical. Leads have to coordinate across many sub-teams, producers have to manage dependencies between systems, and the director has to hold a coherent vision across years of work. The original game was led by creative director Nate Fox and a small senior group, and the sequel has been described in public commentary as a project that is significantly larger in headcount and more distributed across sub-teams.
The production commentary that has come out around the project, including the DigiPen showcase piece on producing Ghost of Yōtei, treats the sequel as a useful case study in how a studio’s leadership style has to evolve when a project grows. A flat structure is good for a tight, focused original. A larger, more distributed sequel benefits from clearer sub-team ownership, more structured handoffs, and more deliberate cross-discipline review. The same person can lead both projects, but the way they spend their time changes.
For an external reader, the takeaway is that “the same studio” does not mean “the same production system”. A studio that shipped one strong open-world action game can ship a very different-looking sequel in terms of how the team is organised, even if the public identity of the studio is consistent. The studio’s job in a sequel is partly to evolve its own production system to match the new project.
Performance, optimisation, and the platform target
Open-world action games live or die on performance. A game that looks beautiful but stutters in combat, drops frames during traversal, or streams poorly across the map will be remembered for those problems no matter how strong the design is. Ghost of Tsushima shipped with a careful performance profile on PlayStation 4 and a higher-fidelity profile on PlayStation 4 Pro, and the PC port later in the project’s life added a new set of performance concerns around scalable settings, ultrawide support, and variable refresh rate. Ghost of Yōtei is a current-generation project, which raises the quality bar but does not remove the core performance discipline.
Three performance priorities dominate on a project of this kind.
- Frame time stability in combat: the player will feel any frame-time spike in melee, and the combat team, animation team, and rendering team all have to commit to a stable per-frame budget for that mode.
- Streaming quality in traversal: the player crosses large distances quickly, often on horseback, and the world has to stream in without visible pop-in or shader compilation hitches.
- Memory budget: a larger world with more assets, more variation, and more weather means the memory budget has to be planned early, not patched late.
None of these are unique to the project, but they are the kind of thing that is easy to underinvest in during the early, fun part of production and very expensive to fix during the optimisation crunch at the end. A useful editorial test is whether the project has a dedicated performance director with authority across disciplines, and whether the per-system budgets are agreed early enough to influence art direction rather than being enforced after the fact.
Comparing Ghost of Yōtei’s design to adjacent open-world action games
A useful way to read any open-world action project is to place it next to its closest peers. The closest peers for Ghost of Yōtei are not just other samurai games; they are open-world action games with a strong single-player focus, a stylised art direction, and a melee system that the studio treats as the centre of the experience. Against that set, the project stands out for its commitment to a single-player experience without live-service obligations, its willingness to reset the protagonist and setting, and its deliberate movement into colder, more weather-driven environments.
| Design dimension | Ghost of Yōtei | Tsushima-era peer | Editorial reading |
|---|---|---|---|
| Combat system | Stance as loadout, broader weapon set | Stance as tool for enemy type | More expression, more balancing work |
| World setting | Hokkaido, cold, more elevation | Tsushima, warm, mostly horizontal | More weather and vertical traversal work |
| Narrative | New era, new protagonist, new factions | Jin Sakai arc, Mongol invasion | Full narrative rebuild, same tone |
| Art direction | Cooler palette, harsher light | Golden hour, stylised warmth | New lighting system, new mood |
| Production model | Larger team, longer cycle | Original team, original cycle | More sub-teams, more handoffs |
Read this way, Ghost of Yōtei is not a “bigger Tsushima”. It is a deliberate change in several axes at once, which is the production reason sequels of this kind take as long as they do.
Risks, trade-offs, and what could go wrong
Every project of this scale has risks that are worth naming explicitly. The most useful risk list is not the generic “will it be good” question, but the specific design and production risks that follow from the choices the studio has already made.
- Combat homogenisation: if the broader weapon set does not have enough per-weapon identity, the combat system can feel flatter than Tsushima’s stance-as-tool design.
- Visual identity drift: the cooler palette and heavier weather can work beautifully in stills and feel oppressive in long sessions if the studio does not protect the rhythm of light and dark areas on the map.
- Narrative sprawl: a larger world and a new protagonist can pull the narrative team in too many directions, and the result can feel less focused than the original’s tighter samurai-versus-invader frame.
- Performance pressure: a larger world with more weather and more interiors is a real frame-time and memory challenge, and any weakness there will be felt on every platform target.
- Audience expectation: the original game earned a passionate audience, and a sequel has to honour that audience without being trapped by it. The team has to make room for new players while still delivering what existing players loved.
None of these are reasons to expect failure. They are the standard risks of a sequel of this scale, and the experienced studios that ship this kind of project usually manage them through early vertical slices, deliberate milestone reviews, and a willingness to cut content that does not serve the core experience.
What developers can learn from the production model
The most useful thing about reading a project like Ghost of Yōtei is not the specific feature list but the production model behind it. Three lessons come up again and again across studios that ship open-world action games at this scale, and they apply well beyond a single project.
- Sequels are not free. A sequel inherits tools, technology, and talent, but it has to rebuild a meaningful share of its content, its narrative, and its world. Budget accordingly.
- Combat is a multi-discipline product. The combat system in a game like this is not owned by the combat team; it is owned by combat, animation, audio, haptics, UI, and technical art together. Plan for that early.
- World setting is a production decision. The choice of Hokkaido over Tsushima is not just an artistic one; it changes the visual systems, the audio systems, the world team workload, and the optimisation budget. A different setting would have produced a different production shape.
For students and early-career developers, the practical takeaway is that production literacy is as important as design literacy. Understanding why a team is organised the way it is, and why a particular design choice cascades into a particular tooling cost, is a large part of being useful on a real project.
Frequently asked questions
What kind of game is Ghost of Yōtei?
Ghost of Yōtei is a single-player, open-world action game set in a stylised version of historical Hokkaido, developed by Sucker Punch Productions. It follows the structural template of Ghost of Tsushima, with a focus on melee combat, free traversal, and a region-based open world, while changing the setting, protagonist, and combat design.
When did Ghost of Yōtei release?
Sucker Punch has publicly confirmed the game as a current project. For the most accurate and current release information, readers should consult the studio’s official channels, since release timing for major single-player projects is often refined during production.
Who develops Ghost of Yōtei?
Ghost of Yōtei is developed by Sucker Punch Productions, the studio behind Ghost of Tsushima, the Infamous series, and the Sly Cooper series. The studio is based in the United States and is part of the PlayStation Studios family.
Is Ghost of Yōtei a sequel to Ghost of Tsushima?
It is a follow-up set in a related world. The setting, era, protagonist, and combat system are different, so it functions as a new entry in a lineage rather than a direct continuation of Jin Sakai’s specific story. Mechanically and structurally it inherits a great deal from Tsushima, but it is built as its own game.
What is the main combat change in Ghost of Yōtei?
Combat in Ghost of Yōtei is built around a broader weapon set, including dual swords, a katana, a spear, and a chain weapon, with stances that act more as loadout choices than as enemy-type counters. The change is less about adapting to a specific enemy and more about expressing a preferred playstyle.
Does Ghost of Yōtei have multiplayer?
Ghost of Yōtei is positioned as a single-player experience, in line with Sucker Punch’s previous single-player releases. The studio has not signalled a live-service or multiplayer component for the project.
How does the setting affect production?
The Hokkaido setting changes the visual and audio workload significantly. Snow, blizzard conditions, and more dramatic elevation place new demands on lighting, weather systems, surface audio, and traversal design. For a developer, the setting is a real production variable, not just a thematic one.
How long does a project of this scale usually take?
Open-world action games of this size typically take several years from project start to release, with the bulk of that time spent on world authoring, combat iteration, and optimisation. The exact length depends on the studio’s prior investment in tools, the size of the team, and the ambition of the new project relative to the previous one.
Where can I find reliable production information about the project?
The most reliable sources are the studio’s official channels, first-party platforms that carry developer interviews, and education-facing features that document the production process with the studio’s involvement. The DigiPen showcase piece on producing Ghost of Yōtei is one example of a publicly accessible, developer-adjacent source that discusses the project’s production approach.
Is Ghost of Yōtei a good case study for game development students?
Yes, particularly for students interested in open-world production, combat system design, art direction for stylised historical settings, and the way a sequel reorganises a studio’s pipeline. The project illustrates how a strong original becomes the foundation for a deliberately different sequel, and how that difference drives real changes in team structure and tooling.
