Summary of "Blizzcon 2017 - World of Warcraft Boss Design Workshop"

BlizzCon 2017: World of Warcraft — Boss Design Workshop (Sea Fury)

This panel was a live brainstorming session where Blizzard designers built a new dungeon boss for Battle for Azeroth in real time. The boss under design was the Sea Fury — a massive, tentacled water elemental tied to Stormsong Valley and the Shrine of the Storm.

What the panel covered

Live design: Blizzard designers iterated from concept to mechanical ideas on-stage.
Dungeon setting: Stormsong Valley — a Kul Tiran shipbuilding region with a secretive order of sea priests who bless ships at the Shrine of the Storm.
Boss concept: the Sea Fury — an enormous water elemental with tentacle/cthulhu-like visuals and a potential shadow/corruption twist.

Story and theme

Stormsong Valley is an idyllic coastal zone with a ritualistic order of sea priests; the Shrine of the Storm serves as the dungeon location.
The Sea Fury represents the ocean’s wrath, summoned or empowered by the priests.
Visual cues emphasize tentacles and a growing shadow-corruption that changes the boss’s appearance and mechanics over the fight.
Narrative/visual goals: sell the nautical and ritual themes, make the environment feel dangerous and lived-in, and tell story through space and mechanics (examples: cleansing fountains later in the dungeon).

How Blizzard builds a boss (design pipeline)

Pre-production meeting: pick setting, story hooks, boss list and produce a 2D layout.
Art kickoff: artists and stakeholders “brain dump” to establish purpose and look for each area.
3D blockout: create an early playable space to place creatures and iterate.
Encounter team meeting: flesh out the dungeon ecology and enemy roster.
Paper design: an encounter designer writes a one-page design with mechanics and role responsibilities.
Implementation, playtesting, tuning, community feedback and iteration.

Core gameplay ideas brainstormed for the Sea Fury

Phase structure
- A/B cycle between forms, with the possibility of a final phase C or corruption burn.
Splitting mechanic (adds)
- The elemental can split into multiple smaller elementals.
- Adds could share boss abilities or have lower health and special death effects (explode, splash damage, apply damage to main boss, or reduce corruption).
- Adds can re-form into the main boss if not handled.
Flood / wave mechanics
- Waves that sweep across the platform, pushing players toward edges.
- Players can be knocked off; designers discussed non-lethal recovery (e.g., returning by friendly boat/cannon on a timer).
- Boss could alternate between a large stationary form and mobile wave-like forms that sweep the room.
Mobility options
- Boss could be immobile, scoot around, submerge and re-emerge, or temporarily fill the room with water (forcing swimming mechanics).
Tentacle interactions
- Tentacles could grab or swallow players, create “void” zones, or function as soak/avoid mechanics.
Corruption / shadow theme
- Boss gradually becomes more shadow-corrupted, changing visuals and mechanics (e.g., water → shadow damage, healing reduction).
- Corruption sources could be removable objects (crystals/bracers) players must break — a shell-game style mechanic.
Environmental interactions
- Pools of “clean” water or fountains later in the dungeon to cleanse shadow effects.
- Boats/cannons used as rescue mechanics or for heroic-mode options.
Risk/reward and Mythic+ considerations
- Killing adds may reduce the boss’s effective health or be risky because they explode/splash.
- The number of submerges or split events can be tuned to affect Mythic+ timing and difficulty.

Gameplay balance and role considerations

Dungeon length: boss fights are typically short (aim for ~2–3+ minutes), so avoid raid-style multi-phase complexity.
Rule of three: avoid forcing players to track more than roughly three simultaneous objectives.
Multiple solutions: design for several ways to mitigate mechanics (class utilities to gather adds, purge, CC).
Avoid single-class requirements; make utilities helpful but not mandatory.
Role-specific notes:
- Tank: positioning (tank to wall) to limit spawn angles; may need to soak or handle grab mechanics.
- DPS: manage add priority; choose between tunneling boss or cleaving adds.
- Healer: expect raid-wide or targeted damage and potential DoTs/healing reduction as corruption rises.
Mobility variance: tune mechanics so movement helps but isn’t strictly mandatory for success.

Design constraint: Keep objectives manageable and provide multiple, non-mandatory ways for groups to solve mechanics.

Practical player tips (from the brainstormed mechanics)

Positioning: tank the boss to minimize dangerous spawn directions and angle of wave attacks.
Add handling: decide whether to prioritize, CC, or cleave adds—learn which adds are dangerous to kill or to leave alive.
Learn wave patterns: anticipate waves/submerges to avoid being pushed off the platform.
Non-lethal recovery: don’t panic if knocked off — first-boss mechanics may include cannons or boats that return you to the fight rather than instant wipes.
Use cleansing pools/fountains to remove shadow debuffs and avoid standing in shadow puddles that amplify pushes.
Bring class utility but don’t rely on a single class—coordinate AoE, stuns, and movement cooldowns.
Coordinate burst windows carefully; killing certain adds at once might enable a burn or cause dangerous splash damage.

Design philosophy takeaways

Brainstorms are collaborative and ideation-heavy; many “bad” ideas are used to spark better ones.
Visual and aural personality matters: changing the elemental’s voice/appearance as it corrupts is a strong storytelling tool.
Iteration is continuous: playtests and community feedback refine design long after the brainstorm.

Next steps after the panel

Designers produce a formal paper design with clear mechanics and role responsibilities.
Implementation in-engine, internal testing, tuning, and community playtests follow before final release.