Pinball Xperience
Dwight Sullivan

Dwight Sullivan

Current position
Senior Game Developer | Lead Software Engineer | Pinball Programmer | Rules Designer | Stern Pinball

Biography

DWIGHT SULLIVAN

From Terminator 2 to Dungeons & Dragons, from Williams to Stern, Dwight Sullivan has accompanied almost every major evolution of modern pinball software

Dwight Sullivan belongs to that category of creators whose influence is measured less by the shape of a playfield than by what the machine becomes once the ball is launched. Joining Williams in 1989, he would go on to span the DMD era, WPC, Pinball 2000, Stern’s first modern period, SPIKE 2, and finally the arrival of connected play and persistent progression. Terminator 2: Judgment Day, The Getaway: High Speed II, Star Trek: The Next Generation, Road Show, WHO dunnit, Junk Yard, Revenge from Mars, Playboy, Pirates of the Caribbean, Game of Thrones, Ghostbusters, Star Wars, Teenage Mutant Ninja Turtles, The Mandalorian, Venom, and Dungeons & Dragons: The Tyrant’s Eye trace an exceptionally long career during which the programmer’s role gradually moved closer to that of a game designer. For Sullivan, software does not merely execute what the playfield asks. It organizes progression, determines the contextual value of shots, distributes resources, structures modes, connects theme to rules, and decides what the player will want to attempt after completing the previous objective.

Identity

Name

Dwight Sullivan

Nationality

American

Profession

Senior Game Developer | Lead Software Engineer | Pinball Programmer | Rules Designer

Education

Electronics Engineering Technology, DeVry Institute of Technology

Professional debut

Williams Electronic Games, 1989

First machine

Riverboat Gambler

Williams period

1989-1999

First period at Stern

1999-2009

WMS Gaming

2009-2014

Return to Stern

2014

Main manufacturers

Williams | Bally / Midway | Stern Pinball

Other industries

Gaming | Slot Software

Pinball Expo Hall of Fame

2017

Major collaborations

Steve Ritchie | Barry Oursler | Pat Lawlor | George Gomez | Dennis Nordman | John Borg | Brian Eddy

Major contemporary project

Dungeons & Dragons: The Tyrant’s Eye

Core disciplines

Software Engineering | Rules Design | Game Development

1989 | An arrival at Williams that was never planned

Dwight Sullivan completed his education in electronics and applied computing at a time when working in pinball was not yet a professional objective. His arrival at Williams came through a chain of circumstances that led him to present a portfolio combining programming, electronics, and graphic creation to a company looking for new profiles capable of working on real-time systems. He joined Williams in November 1989 and immediately discovered an environment where the programmer could never remain separated from the physical machine. Pinball does not forgive abstraction. The code receives information from switches triggered by a real ball, controls coils that move mechanisms, and activates lighting, sound, and scoring inside an environment where an unexpected event can occur at any moment. Sullivan therefore learned the profession directly through the material itself, inside a team that was about to lead pinball into one of the most important periods in its history.

1990 | Riverboat Gambler | Learning how to make the machine live

Riverboat Gambler became one of his first major professional projects. The game still belonged to the generation immediately preceding the creative explosion of Williams’ large DMD machines, but it gave Sullivan the fundamental education of the system: tracking the state of the playfield, coordinating mechanisms, processing events, and maintaining coherent logic while several elements could be triggered simultaneously. This first experience is essential to understanding the rest of his career because Sullivan would later build increasingly complex architectures without ever losing that relationship with physical mechanics. In his work, a ruleset does not begin as a theoretical succession of modes. It must function around an object that rebounds, accelerates, gets trapped, returns too quickly, or forces the player to improvise.

1991 | Terminator 2: Judgment Day | A change of scale

Terminator 2 represents the first major turning point in his career. Sullivan took over the software for Steve Ritchie’s project as Williams entered the large-DMD era. The playfield relied on rapid circulation, an iconic mechanical cannon, and a license whose audiovisual potential greatly exceeded what earlier generations had been able to deliver. The programmer now had to coordinate animation, sound, scoring, video modes, progression, and mechanical events with a level of precision that profoundly changed the role itself. Pinball could explain its objectives more clearly, react through richer staging, and give different identities to sequences that were still built around the same switches. Terminator 2 placed Sullivan at the center of this transformation and began a collaboration with Steve Ritchie that would span several decades.

1992 | The Getaway: High Speed II | Giving structure to speed

The Getaway directly extended the work begun with Ritchie. The playfield carried forward the DNA of High Speed and pushed it toward even more spectacular circulation, dominated by orbits, the Supercharger, and a constant sense of velocity. Sullivan had to structure that physical energy so the game would not become a simple succession of fast trajectories. The rules assign different states to the same major areas, evolve values, organize progression, and give the player reasons to pursue certain shots at particular moments. This articulation between physical speed and software hierarchy would become one of the great strengths of the Ritchie-Sullivan collaborations: the playfield retains its kinetic identity while the software continuously alters the strategic meaning of its trajectories.

1993 | Star Trek: The Next Generation | Software enters the design itself

Star Trek: The Next Generation expanded Sullivan’s role further. His involvement went beyond programming and directly touched the conception of a machine whose license, missions, characters, cannons, and progression demanded a remarkably extensive architecture for the period. The game could not simply use Star Trek as audiovisual decoration. The rules had to respect the logic of the universe, organize confrontations, distribute missions, and integrate the crew’s reactions without losing the readability required by a fast and demanding playfield. Sullivan’s work already reveals what would become a constant throughout his career: when an intellectual property carries a strong internal identity, the code must understand how that universe works. The theme cannot merely appear on the display. It must determine what the machine asks the player to do.

Star Trek | When the license begins dictating the machine’s behavior

This approach to intellectual property would become increasingly important in later projects. WHO dunnit would turn investigation into a game structure, 24 was intended to use the television series’ temporal pressure as a central engine, The Mandalorian would make Beskar and equipment into genuine resources, Venom would alter the experience according to the selected host, and Dungeons & Dragons would integrate classes, inventory, experience, and campaign progression into the ruleset. Star Trek belongs among the first examples where Sullivan truly had to translate a fictional universe into behavior. Selecting a mission, triggering a character, or resolving a sequence could not be interchangeable. Each element had to occupy a coherent place in the progression and produce a response that belonged to Star Trek as much as it belonged to pinball.

1994 | Road Show | Changing language with Pat Lawlor

Road Show forced Sullivan to work according to a physical logic very different from Steve Ritchie’s. Pat Lawlor builds playfields where distinct areas, ball stops, mechanical characters, and shifts in rhythm play a much larger role. The software must therefore accept pauses, staging, and the need to give value to interactions that do not belong to the same kinetic register as The Getaway or Star Trek. This ability to adapt would follow Sullivan throughout his career. He would work with Steve Ritchie, Pat Lawlor, Barry Oursler, George Gomez, Dennis Nordman, John Borg, and Brian Eddy without attempting to impose an identical structure on all their playfields. The physical game imposes its behavior first, and the software must understand that behavior before constructing its own architecture.

1995 | WHO dunnit | The programmer claims a larger part of the design

WHO dunnit represents a decisive moment because Sullivan now wanted to participate more directly in creating the game itself. With Barry Oursler, he developed a machine built around a murder investigation in which suspects, clues, locations, and relationships needed to form a flexible enough system for several cases to exist without feeling like arbitrary randomization. The project required the team to think about the characters before even defining certain gameplay events, because each suspect had to fit into different combinations without destroying the coherence of the whole. Software therefore stopped being only the tool that validated objectives. It became the engine of a variable narrative structure in which the current state of the game determined what the machine could reveal next.

WHO dunnit | The reward must understand the state of the game

WHO dunnit’s Mystery Target illustrates Sullivan’s view of code particularly well. An interesting reward does not necessarily have to be completely random. The software can observe what the player has already accomplished, analyze the current state of the game, and select a response appropriate to that moment. The physical switch remains identical, but its result changes because the machine now has enough context to decide what makes sense. This logic would become increasingly important as hardware evolved. The more state a machine can remember, the more Sullivan uses that information to transform the value of the actions that follow.

Barry Oursler | A genuine two-voice construction

The collaboration with Barry Oursler also helps clarify Sullivan’s exact place within the design process. Oursler works more directly with the playfield, trajectories, and mechanisms, while Sullivan develops a substantial part of the concept, rules, and invisible structure. The two dimensions are never independent. A physical destination matters only if the code understands what it represents, and a rule cannot be evaluated without knowing how the ball actually reaches that destination. WHO dunnit therefore materializes a working model that suits Sullivan especially well: the playfield designer and the ruleset developer simultaneously build two architectures that ultimately have to function as one.

1996 | Junk Yard | Giving meaning to the absurd

Junk Yard continues this desire to use software as a tool for coherence. The playfield presents a deliberately strange succession of objects and situations, yet the game must still make the player feel that these elements belong to a unified journey. Sullivan contributes to the concept, design, and software, using progression to connect these disparate objects around a logic of escape and construction. The approach demonstrates that thematic integration does not depend on a major license. Even an intentionally eccentric universe becomes stronger when the code transforms its objects into stages, its interactions into resources, and its rewards into parts of an understandable progression.

The second economy | Score is no longer the player’s only form of wealth

One idea gradually becomes recurrent in Sullivan’s work: creating another form of value alongside score. The player accumulates elements that are not immediately converted into points but instead modify future potential. On Playboy, this logic appears through the Rabbit Heads. Years later it returns in more ambitious forms with Beskar in The Mandalorian, upgrades and progression in Venom, then experience, equipment, and inventory in Dungeons & Dragons. This second economy profoundly changes the perception of a game. The player is no longer simply trying to increase a number. The player is constructing a state capable of opening new possibilities.

1998 | The Champion Pub | When code must understand an unusual mechanism

The Champion Pub places Sullivan in front of a playfield whose identity depends on highly specific mechanisms. The punching bag, jump rope, and fighting sequences require software to manage behaviors that cannot simply be treated as ordinary targets or ramps. Each special device has to be understood, controlled, and integrated into the rules so that the player feels as though they are confronting an opponent rather than activating a succession of coils. This type of project is a reminder that pinball programming remains deeply connected to engineering. Beneath the staging, the code must know the exact state of the mechanisms, anticipate their transitions, and preserve immediate responsiveness while the ball continues moving.

1999 | Revenge from Mars | Video enters the physical space of the game

Revenge from Mars forced Williams’ teams to reinvent their development methods once again. Pinball 2000 attempted to make video and playfield coexist by reflecting imagery into the glass so that digital characters and objects seemed to inhabit the same space as the ball. Sullivan worked within a software team much larger than on his early games. The program had to synchronize physical events with a continuous visual layer, manage more content, and accept that presentation itself had become part of the playfield. The creative gain was enormous, but so was the development complexity. A modification that might once have involved only a few people could now affect several disciplines and dependencies at once.

1999 | The closure of Williams ends a first decade

When Williams closed its pinball division in 1999, Sullivan left after almost exactly ten years. That first period had taken him through the complete evolution of modern Williams pinball, from architectures preceding the large DMD to Pinball 2000. He joined Stern only weeks later and entered a very different industrial context. Teams were smaller, budgets less comfortable, and each person often had to cover a broader range of responsibilities. The technology changed, but Sullivan retained the same priority: build a progression clear enough that the player always understands why the next shot is worth attempting.

2000 | Sharkey’s Shootout | Taking part in Stern’s rebuilding

Sharkey’s Shootout belongs among Sullivan’s first Stern projects after Williams left pinball. He was now working for a company that had practically become the sole American manufacturer producing new pinball machines on a regular basis. The contrast with Pinball 2000 was immense. Williams had just invested heavily in a radical new platform, while Stern’s priority was to maintain a viable industrial model around traditional pinball. Sullivan adapted his work to that reality and reunited with John Borg, another creator whose playfields would repeatedly ask him to develop rules capable of organizing fast and sometimes particularly demanding trajectories.

2002 | Playboy | The game developer takes responsibility for a global architecture

Playboy brought Sullivan back alongside George Gomez in a configuration where concept, design, and software strongly intersected. The game allows the idea of the second economy to become more visible, with certain resources existing alongside score and contributing to overall progression. Sullivan does not multiply systems merely to increase density. The objective is to create several timescales within a single game. A shot can award points immediately while also advancing a resource whose true value will only become clear several minutes later. This separation between instant gratification and medium-term construction would become one of the major tools of his contemporary rulesets.

The intermediate player | The center of gravity of his philosophy

Sullivan does not build his games exclusively from the perspective of a competitor capable of exploiting every multiplier. He gives central importance to the intermediate player, someone who already controls the ball and has begun to understand objectives but does not necessarily know every interaction within the scoring system. This position profoundly influences how he organizes complexity. A machine must offer an understandable first layer, provide a reward quickly, show that a more important objective exists, and then allow the player to discover deeper interactions. A wizard mode may remain distant, but its existence feeds curiosity. Rules density has value only when it opens doors rather than turning the first few games into an examination.

2003-2006 | Terminator 3, The Sopranos, World Poker Tour, Pirates of the Caribbean | The ruleset becomes a discipline of its own

Sullivan’s Stern years saw him contribute to several very different projects that gradually reinforced the role of the rules designer. Terminator 3 reconnected him with the T2 universe and Steve Ritchie, The Sopranos placed him in a team where George Gomez and Lyman Sheats were already deeply involved, World Poker Tour expanded the complexity of the game systems further, and Pirates of the Caribbean paired Dennis Nordman’s physical game design with Sullivan’s central involvement in rules and software. That last collaboration demonstrates especially well the distinction between two forms of design: the playfield defines destinations, mechanisms, and circulation, while the ruleset determines what those destinations are worth, when they become relevant, and how they contribute to the overall progression.

Pirates of the Caribbean | The playfield is no longer enough to describe game design

On Pirates, the film universe provides an enormous number of characters and situations, but the software must organize them to prevent the machine from becoming a simple collection of references. Physical objectives must correspond to thematic events, characters must enter the progression coherently, and rewards must form a hierarchy that the player can understand. Sullivan’s work demonstrates that modern game design can no longer be reduced to drawing the playfield. A substantial part of the experience now lies in the sequence of states, how they overlap, when a feature becomes available, and what a familiar shot becomes worth according to everything that has been prepared beforehand.

2009 | 24 | An interrupted vision

24 was intended to give Sullivan especially fertile ground for experimenting with a structure built around time and the pressure that defines the television series. The project was disrupted by a difficult economic period at Stern and by his departure from the company before the game reached its final form. Some of his ideas were passed on to the team that continued development, but several directions changed after he left. The machine therefore occupies a particular place in his career: his name remains connected to the software, but the finished game should not be read as the complete expression of his original vision.

2009-2014 | WMS Gaming | Leaving pinball without leaving game software

Sullivan then returned to the WMS universe and worked on gaming systems. He temporarily left pinball but remained immersed in game programming, reward structures, state management, and audiovisual presentation. This period coincided with Stern gradually transforming its internal organization and preparing a generation of products in which screens, connectivity, and updates would take on a growing role. When he returned to the manufacturer in 2014, the technological environment was no longer the one he had left five years earlier.

2014 | Return to Stern | A second career begins

Sullivan’s return to Stern opened a period that would ultimately become as important as his years at Williams. He came back as Senior Game Developer inside a company now capable of supporting more extensive rulesets, larger software teams, and above all development that could continue long after commercial release. A machine was no longer frozen the day it left the factory. Its code could be expanded, rebalanced, and completed after thousands of real-world games. For a creator who views rules as a living architecture, this possibility profoundly changes the development process.

2015 | Game of Thrones | Several strategies for the same playfield

Game of Thrones reunited Sullivan with Steve Ritchie and placed him at the head of a ruleset where the initial choice of House influences how the game can be approached. The player no longer necessarily enters a path identical to that of the previous player. Advantages, alliances, multipliers, and general progression create several strategic routes across the same physical architecture. The logic fits Sullivan’s philosophy perfectly: the geometry of the playfield remains stable, while the software can alter how that geometry is interpreted. Shots are not merely destinations. They become tools whose usefulness depends on the state chosen and constructed by the player.

2016 | Ghostbusters | Choice exists before the first real shot

Ghostbusters pushes this logic into the Skill Shot itself. The player can determine the reward being pursued before the plunge and change the context in which the ball will enter play. The value of an action is therefore no longer determined exclusively after it has been performed. Sullivan introduces strategy in advance, giving the player a reason to prepare the ball before it truly begins circulating across the playfield. The ruleset then multiplies layers, modes, multiballs, and interactions, but this detail summarizes his approach well: every moment can become a decision as long as the machine provides enough information for that choice to carry meaning.

2017 | Star Wars | Moving value instead of moving the playfield

Star Wars represents one of the strongest expressions of the Ritchie-Sullivan collaboration. The player selects a character, develops progression, and can move multipliers among several major trajectories on the playfield. Interest therefore does not come solely from the intrinsic difficulty of the shots. The player decides where value should be concentrated. An orbit can become temporarily essential and then lose importance when a multiplier moves elsewhere. The playfield does not physically change, but its strategic topography is continuously redrawn by the software.

2017 | Pinball Expo Hall of Fame

Dwight Sullivan’s induction into the Pinball Expo Hall of Fame recognized nearly three decades of work at that point. The distinction acknowledged both the longevity of his career and the changing perception of the programmer’s profession. For years, the playfield designer naturally occupied most of the public attention. Sullivan’s machines demonstrate that a modern pinball machine contains at least two architectures: the one visible in ramps, loops, targets, and mechanisms, and the one discovered through states, values, rules, resources, and progression. Sullivan belongs among those who made this second architecture impossible to dismiss as merely technical.

Core rules | Build the backbone first

Sullivan’s method begins with a simple idea: a ruleset needs a central route before it accumulates details. The whitewood is made playable as early as possible, specific mechanisms are integrated, then the core rules organize the journey from the Start button to the major endgame stages. Multiballs, modes, Mystery, wizard modes, and other layers then enrich this backbone. This hierarchy prevents a project from becoming a catalog of features without direction. A machine may offer enormous content, but the player must always be able to understand what is being built and what the next step will unlock.

The whitewood | The code must learn the ball

Sullivan places great importance on the moment when the whitewood becomes genuinely playable. Before certain rules are fixed, the team must observe the ball, understand returns, identify natural shots, locate areas where control is gained or lost, and measure how mechanisms alter circulation. This approach directly aligns with the distinction between PX LAYOUT™ and PX BALL KINETICS™. The first describes how the player addresses the playfield, while the second describes how the ball behaves after the shot. Software then exploits both realities. It can encourage a trajectory, assign risk or value to it, but it cannot erase what that trajectory physically produces.

2019 | The Munsters | Adjusting density to the machine

The Munsters brought Sullivan back together with John Borg on a game whose scale needed to remain compatible with a lighter theme and an architecture less focused on the massive accumulation of systems found in Game of Thrones. The project is a reminder that a Sullivan ruleset does not necessarily mean maximum density. His approach is instead to adjust depth to the playfield and license. A machine can offer a more direct progression without becoming shallow if the objectives connect correctly and if the player quickly understands what can be pursued.

2020 | Teenage Mutant Ninja Turtles | Organizing a machine that rarely gives the player time to breathe

Teenage Mutant Ninja Turtles reunited John Borg on game design with Sullivan on game development on a particularly demanding playfield. Shots are short, returns can be sharp, and directional changes rapid, creating nervous PX BALL KINETICS™ where survival itself becomes part of the challenge. Sullivan must provide enough progression for the player not to experience only the physical difficulty. Turtle selection, episodes, training, multiballs, and parallel objectives create a structure that gives meaning to the brutality of the playfield without trying to artificially soften it.

Brian Eddy | A new major collaboration

The Mandalorian opened an important period with Brian Eddy on game design and Sullivan on game development. The partnership would continue through Venom and Dungeons & Dragons: The Tyrant’s Eye. Eddy builds playfields whose major destinations are generally identifiable from the first games. Sullivan can then use that readability as a foundation for much more complex systems of resources, progression, cooperation, and persistence. The relationship echoes, in contemporary form, the idea that a playfield can remain immediately understandable while supporting a second architecture whose depth continues far beyond the initial reading.

2021 | The Mandalorian | Beskar becomes a genuine resource

The Mandalorian turns several elements of the license into gameplay systems. Missions, Encounters, Bounty Hunts, and multiballs feed a progression in which Beskar represents a resource distinct from score. The player can use it to obtain upgrades and expand future possibilities. The second economy Sullivan had already explored during his earlier Stern period takes a much more integrated form here. The theme no longer merely explains why the player receives a reward. The internal logic of the universe, equipment, resources, and character growth, becomes part of the rules themselves.

Impossible Play | Software changes the player’s relationship with the flippers

Impossible Play explores another boundary. The code no longer changes only scoring or objectives. It imposes restrictions on the use of the flippers themselves. Holding a flipper too long can deplete a reserve and force the player to release the button before recovering full control. The physical interface of pinball, normally treated as immutable, becomes a variable within the ruleset. Sullivan demonstrates that modern software can now intervene directly in the most basic relationship between the player, the button, and the ball.

Cooperative Play | Several players can finally share a state

The Mandalorian also develops cooperative play in which several participants do more than alternate scores. Progression, certain resources, and several objectives can be built around a shared effort. Traditional pinball multiplayer is based on the juxtaposition of individual games. Each player takes a ball, waits for the next turn, and retains an independent score. Sullivan contributes here to an evolution in which software can transform several players into a team acting upon a common progression. The idea becomes even more natural when Dungeons & Dragons places it inside a universe built around collective adventure.

2023 | Venom | Choosing a host partially reprograms the machine

Venom breaks with the model in which every player necessarily moves through the same structure. The selected host influences abilities, advantages, and the way certain parts of the ruleset are approached. The machine keeps the same playfield, but its interpretation shifts. A decision made before the game truly develops changes priorities and creates several ways to read the same architecture. Sullivan uses the character as a game-design parameter rather than a simple avatar. The theme therefore does not stop at missions. It penetrates the fundamental rules.

Venom | The game is no longer the only unit of progression

The true break comes from persistence. A connected player can preserve progress and continue it during a later session. Game over no longer necessarily means that the entire construction must restart. This profoundly changes the temporal structure of pinball. For decades, the game itself has been the fundamental unit of experience: three balls, a score, an ending, then another attempt. Venom allows the ruleset to move beyond that boundary. The machine remembers what has been accomplished and can resume a progression whose scale now extends beyond a single session.

Speed Run | A campaign can become an instrument of mastery

Venom’s persistent progression does not replace traditional challenge. Once the final objective has been reached, Speed Run transforms the same structure into an optimization field. The player is no longer simply trying to reach the end. The objective becomes reducing the time required to get there. Sullivan therefore builds two successive readings of the same system: the first encourages discovery and allows gradual progress, while the second turns that knowledge into a mastery challenge. Persistence that first makes the content more accessible later becomes the foundation of an objective aimed at players capable of pushing much deeper into the ruleset.

Mayhem Multiball | Deliberately refusing the reward

Mayhem Multiball returns to a central principle in Sullivan’s thinking: the best moment to collect a reward is not necessarily the moment it first becomes available. The player can continue building locks instead of immediately starting multiball, increasing the ambition of the future sequence while accepting the risk of keeping the ball alive for longer. Software transforms a feature traditionally perceived as an instant reward into a decision. Starting now secures a result. Continuing to build may produce more, but it exposes the entire plan to a drain.

2025 | Dungeons & Dragons: The Tyrant’s Eye | The ruleset becomes a campaign

Dungeons & Dragons: The Tyrant’s Eye pushes this evolution much further. Brian Eddy leads the physical game design while Sullivan directs a software architecture in which characters, classes, experience, inventory, items, choices, encounters, progression, and multiple endings become part of the general structure. The game does not simply use monsters and references from Dungeons & Dragons. It attempts to translate some of the fundamental principles of role-playing into the language of pinball. A character can evolve, accumulate resources, and continue a journey that no longer depends entirely on the score produced during the few minutes of a single game.

PinSave | The machine now remembers the player

Persistence reaches another stage here. An identified player can recover a character, level, inventory, and progression during a later session. The technology belongs to Stern’s connected ecosystem, but its value depends on what the ruleset chooses to do with it. Sullivan uses this infrastructure to give durable memory to systems he has been developing for decades. Playboy and The Mandalorian already used secondary resources as a way of storing value inside a game. Venom extended that memory across multiple sessions. Dungeons & Dragons turns it into genuine character continuity.

Dungeons & Dragons | Randomness must never erase decision-making

Dice and randomness naturally belong to the universe of Dungeons & Dragons, but their use in pinball requires a delicate balance. If everything becomes deterministic, part of the identity of role-playing disappears. If randomness dominates everything, the player loses the relationship between quality of execution and outcome. The ruleset must therefore allow variation and decision-making to coexist. Events may change, paths may branch, and some situations may differ from one game to another, but shots, choices, and resources still need to offer the player a form of mastery. This logic extends an idea already visible thirty years earlier in WHO dunnit: a machine can generate variation without becoming arbitrary.

The party | Multiplayer finally joins the logic of the theme

Dungeons & Dragons also gives cooperative play especially strong thematic meaning. Several players can contribute to the same adventure instead of simply adding separate individual journeys. The principle aligns directly with tabletop role-playing, where progression belongs to the party. Software therefore does more than manage four separate scores. It transforms multiplayer into a shared structure and makes that difference itself part of thematic integration.

From WHO dunnit to Dungeons & Dragons | Thirty years of giving the machine more memory

A remarkable line connects Sullivan’s machines despite the enormous technological distance between generations. WHO dunnit already examined the current state of the game to select a relevant reward. Playboy developed an economy alongside score. Game of Thrones altered the approach according to the chosen faction. The Mandalorian linked resources with equipment. Venom allowed progression to survive across sessions. Dungeons & Dragons now remembers character, experience, and inventory. The hardware has transformed radically, but the movement remains coherent: the more the machine can know about what the player has built, the more Sullivan uses that information to modify what it will offer next.

The intermediate player | Depth should never present itself as a barrier

This move toward increasingly sophisticated rules does not fundamentally alter Sullivan’s philosophy. He continues to create entry points that function without requiring encyclopedic knowledge. A player discovering the machine should understand that an action produces something. A returning player should begin noticing relationships between systems. An experienced player then discovers optimization, stacking windows, resource choices, and advanced objectives. This progression in understanding matters as much as progression within the ruleset itself. A machine can contain enormous depth without requiring every player to master it from the first ball.

Steve Ritchie | Giving strategic structure to speed

The relationship with Steve Ritchie spans Terminator 2, The Getaway, Star Trek: The Next Generation, Game of Thrones, and Star Wars. Ritchie’s playfields often favor direct trajectories and immediately perceptible physical energy. Sullivan builds behind them an architecture where the importance of each shot can change continuously. The player continues to pursue the flow of the playfield, but the software forces a decision about where that energy should be invested. Star Wars provides an especially clear example through its movable multipliers: the physical playfield remains the same, but the best trajectory depends on decisions made elsewhere in the ruleset.

Barry Oursler | The partner who allows him to fully embrace co-design

Barry Oursler occupies a different place in Sullivan’s career. WHO dunnit gives the programmer the opportunity to officially expand his role and participate in the conception of a game whose theme itself depends on software structure. The partnership represents a vision of development in which playfield and ruleset grow together. One does not arrive after the other. Mechanisms suggest rules, rules demand new destinations, and physical testing forces both creators to modify ideas that appeared convincing on paper.

George Gomez | Making staging part of the system

The collaborations with George Gomez span several technological generations and demonstrate the growing importance of audiovisual presentation within software. Revenge from Mars requires spectacular synchronization between video and the physical playfield. Playboy uses theme through a very different progression. Ghostbusters pushes the volume of animations, voices, and states much further. For Sullivan, none of these elements sit outside the rules. They participate in how the player understands the rules, identifies progression, and experiences the machine’s reactions.

John Borg | Giving direction to brutality

John Borg’s playfields present Sullivan with another problem. Sharkey’s Shootout, The Munsters, and especially Teenage Mutant Ninja Turtles can expose the ball strongly and demand fast reactions. The ruleset must therefore provide a clear direction without requiring the player to process excessive information during moments when the playfield is already applying pressure. On TMNT, the physical difficulty is part of the machine’s identity. The software does not attempt to hide it. It gives the player a reason to confront that difficulty by organizing characters, episodes, training, and multiballs around the playfield’s nervous character.

Brian Eddy | Bringing persistence into the language of pinball

The Mandalorian, Venom, and Dungeons & Dragons now form a major part of Sullivan’s second career. All three begin from Brian Eddy playfields with readable destinations, then progressively expand software memory and possibility. The Mandalorian develops resources, equipment, and cooperation. Venom allows progression to survive game over. Dungeons & Dragons transforms that persistence into a campaign with character, inventory, and experience. The partnership therefore uses an immediately understandable physical architecture as the foundation for a second architecture whose depth can continue to unfold long after the first game.

Skills & Roles

Pinball Software Engineering | Lead Game Development | Rules Design | Game Programming | Concept Development | Game Design | Core Rules Architecture | Mode Design | Wizard Modes | Multiball Design | Scoring Systems | Resource Economies | Persistent Progression | Cooperative Play | Device Programming | Real-Time Software | Gameplay Integration | Audiovisual Coordination | DMD Integration | LCD Integration | Post-Release Development | Licensed Theme Integration | Player Progression | Difficulty Design

Dwight Sullivan has crossed more than three decades of radically different technologies without the fundamental nature of his work disappearing. He began on architectures where every computing resource mattered and much of the code remained extremely close to the hardware. He moved through DMD, Pinball 2000, successive Stern platforms, the massive growth of audiovisual content, and finally connectivity capable of preserving data across multiple games. Available power changed, the number of systems increased, and team sizes evolved, but the central question remained the same: what does the machine need to understand about the current state of play in order to make the next shot more interesting than the previous one?

Key dates and contributions

Date

Project or milestone

Contribution and significance

1989

Williams

Joins Williams and begins his career in pinball software.

1990

Riverboat Gambler

First major project and introduction to real-time architectures.

1991

Terminator 2

Takes over software on Steve Ritchie’s project at the beginning of the DMD era.

1992

The Getaway: High Speed II

Continues the collaboration with Ritchie around a playfield built on speed.

1993

Star Trek: The Next Generation

Software and broader participation in design and license integration.

1994

Road Show

Works with Pat Lawlor on a very different physical architecture.

1995

WHO dunnit

Concept, design, and software around a variable investigation.

1996

Junk Yard

Concept, design, and software around an intentionally unconventional progression.

1998

The Champion Pub

Programs a machine strongly dependent on highly specific mechanisms.

1999

Revenge from Mars

Contributes to Pinball 2000 software before Williams closes its pinball division.

1999

Stern Pinball

Joins Stern after Williams exits pinball.

2002

Playboy

Concept, design, and software with an economy running alongside scoring.

2006

Pirates of the Caribbean

Rules design and software on Dennis Nordman’s playfield.

2009

WMS Gaming

Leaves Stern and continues working in game software.

2014

Return to Stern

Begins a major second period as Senior Game Developer.

2015

Game of Thrones

Develops several strategic approaches around the same playfield.

2016

Ghostbusters

Dense ruleset and reward choices integrated from the Skill Shot onward.

2017

Star Wars

Characters, missions, and multipliers redraw the value of shots.

2017

Hall of Fame

Inducted into the Pinball Expo Hall of Fame.

2019

The Munsters

Adjusts ruleset density to a more direct machine.

2020

Teenage Mutant Ninja Turtles

Lead Game Development on an especially demanding playfield.

2021

The Mandalorian

Resources, equipment, cooperation, and altered conditions of play.

2023

Venom

Hosts, Speed Run, and persistent progression across multiple sessions.

2025

Dungeons & Dragons: The Tyrant’s Eye

Campaign, characters, inventory, experience, and persistent progression.

He began on machines that remembered the state of a switch, he now works on machines capable of remembering the story of a player

When Dwight Sullivan joined Williams in 1989, the programmer’s task was already complex, but the machine’s memory was still largely confined to the current game. A switch changed state, a mechanism responded, a value progressed, and a few minutes later game over reset almost everything. More than three decades after Riverboat Gambler, Dungeons & Dragons can recover a character, experience, items, and progression before the new session has even developed its first major sequence. Between those two extremes, Sullivan has crossed nearly every major transformation of modern pinball software without abandoning the logic that structures his work.

Terminator 2 introduced him to the expressive power of the DMD. Star Trek showed that a license could directly influence the rules. WHO dunnit turned the current state of the game into information used to generate new responses. Revenge from Mars brought software into the visual space of the playfield. Playboy gave a clear place to an economy running alongside score. Game of Thrones and Star Wars made shot value dependent on strategic decisions taken beforehand. The Mandalorian transformed resources and equipment into progression systems. Venom allowed the machine to remember what had been accomplished beyond game over. Dungeons & Dragons finally makes that memory the foundation of a campaign capable of surviving across sessions.

The common thread is not the number of rules. Sullivan has never measured the richness of a game by the number of pages required to explain it. His work instead attempts to transform information into decision-making. A shot does not need to change physically in order to gain a different value. It is enough for the player to have selected a character, moved a multiplier, preserved a resource, prepared a multiball, continued a campaign, or accepted the risk of delaying a reward. That invisible architecture runs through his entire career.

Dwight Sullivan has therefore done more than accompany the evolution of pinball software. He has helped expand what pinball considers a game to be. First a few balls and a score, then a network of resources, paths, and states, and finally a progression capable of surviving beyond the machine itself. The hardware has changed, displays have grown, and connectivity has opened possibilities that a Williams programmer in 1989 could not yet exploit. The essential function remains intact: understand what the player has just done in order to make the next decision more interesting.

Highlights

  • Pinball Software Engineering
  • Lead Game Development
  • Rules Design
  • Game Programming
  • Concept Development
  • Game Design
  • Core Rules Architecture
  • Mode Design
  • Wizard Modes
  • Multiball Design
  • Scoring Systems
  • Resource Economies
  • Persistent Progression
  • Cooperative Play
  • Device Programming
  • Real-Time Software
  • Gameplay Integration
  • Audiovisual Coordination
  • DMD Integration
  • LCD Integration
  • Post-Release Development
  • Licensed Theme Integration
  • Player Progression
  • Difficulty Design

Key dates

  1. Williams Joins Williams and begins his career in pinball software.

  2. Riverboat Gambler First major project and introduction to real-time architectures.

  3. Terminator 2 Takes over software on Steve Ritchie’s project at the beginning of the DMD era.

  4. The Getaway: High Speed II Continues the collaboration with Ritchie around a playfield built on speed.

  5. Star Trek: The Next Generation Software and broader participation in design and license integration.

  6. Road Show Works with Pat Lawlor on a very different physical architecture.

  7. WHO dunnit Concept, design, and software around a variable investigation.

  8. Junk Yard Concept, design, and software around an intentionally unconventional progression.

  9. The Champion Pub Programs a machine strongly dependent on highly specific mechanisms.

  10. Revenge from Mars Contributes to Pinball 2000 software before Williams closes its pinball division.

  11. Stern Pinball Joins Stern after Williams exits pinball.

  12. Playboy Concept, design, and software with an economy running alongside scoring.

  13. Pirates of the Caribbean Rules design and software on Dennis Nordman’s playfield.

  14. WMS Gaming Leaves Stern and continues working in game software.

  15. Return to Stern Begins a major second period as Senior Game Developer.

  16. Game of Thrones Develops several strategic approaches around the same playfield.

  17. Ghostbusters Dense ruleset and reward choices integrated from the Skill Shot onward.

  18. Star Wars Characters, missions, and multipliers redraw the value of shots.

  19. Hall of Fame Inducted into the Pinball Expo Hall of Fame.

  20. The Munsters Adjusts ruleset density to a more direct machine.

  21. Teenage Mutant Ninja Turtles Lead Game Development on an especially demanding playfield.

  22. The Mandalorian Resources, equipment, cooperation, and altered conditions of play.

  23. Venom Hosts, Speed Run, and persistent progression across multiple sessions.

  24. Dungeons & Dragons: The Tyrant’s Eye Campaign, characters, inventory, experience, and persistent progression.

Associated machines

9 machines