Pinball Xperience
Lonnie Ropp

Lonnie Ropp

Current position
Pinball Software Development

Biography

LONNIE D. ROPP

Software Designer, Programmer and Game Designer | Data East, Sega Pinball and Stern Pinball

Lonnie D. Ropp occupies a distinctive place in the history of American pinball software because his career connects the birth of Data East Pinball almost continuously to the modern Stern era. His first commercial credit dates back to Laser War in 1987, the first machine produced by Data East Pinball. His most recent identified commercial credit remains John Wick in 2024, where he shares software duties with Tim Sexton. Thirty-seven years separate those two productions, a period during which he worked across three manufacturers, several electronic architectures, the arrival of the DMD, Sega WhiteStar, Stern SAM and SPIKE, the transition to LCD displays and the transformation of pinball code into an environment capable of continuing to evolve years after a machine enters production.

Software forms the core of his career. Laser War, Time Machine, Phantom of the Opera, Star Wars, Jurassic Park, The Who’s Tommy Pinball Wizard, Guns N’ Roses, Apollo 13, Space Jam, Star Wars Trilogy, Harley-Davidson, The Lord of the Rings, Pirates of the Caribbean, Iron Man, Tron: Legacy, Star Trek, Game of Thrones, Ghostbusters, Stranger Things, James Bond 007 and John Wick represent only part of his catalog. This continuity makes it possible to observe the complete evolution of the profession, from programs operating under severe resource limitations to architectures where scoring, modes, mechanisms, animation, music, lighting, player profiles and software updates all need to function simultaneously.

Ropp should not, however, be reduced to software implementation alone. Several documented credits place him directly in game design. The Who’s Tommy Pinball Wizard associates his name with both game design and software. Space Jam also credits him in both disciplines. Harley-Davidson was designed with John Borg while Ropp also handled software. Stern also includes him within the design team for Avatar alongside John Borg, in addition to his programming work. These examples remain a minority compared with the scale of his software catalog, but they show that he understands pinball from both sides of the same interaction: physically organizing what the player can shoot and programming what those shots actually mean.

His career also includes a less visible internal dimension. Ropp has held responsibilities as Director of Software Game Design at Stern and contributed to the transmission of the profession to later generations of developers. When Mike Kyzivat sought to join Stern in 2007, his first interview was conducted by Ropp. His patented work on Tournament Play with Joe Blackwell, Dwight Sullivan and later Keith Johnson also shows an interest in software systems extending beyond the ruleset of a single machine.

Identity

Name

Lonnie D. Ropp

Profession

Software Designer | Programmer | Game Designer

Primary field

Pinball Software Development

Documented pinball debut

1987

First commercial credit

Laser War

Associated manufacturers

Data East | Sega Pinball | Stern Pinball

Documented roles

Software | Game Design | Concept / Development

Documented leadership role

Director of Software Game Design

First period

Data East Pinball

Second period

Sega Pinball

Third period

Stern Pinball

Most recent identified commercial credit

John Wick, 2024

Major machines

Laser War | Star Wars | Jurassic Park | The Who’s Tommy | Guns N’ Roses | Apollo 13 | Space Jam | Harley-Davidson | The Lord of the Rings | Avatar | Star Trek | Game of Thrones | Ghostbusters | Stranger Things | James Bond 007 | John Wick

Before Data East | Rock-Ola and entry into game development

Before Data East Pinball, Lonnie Ropp worked within the Rock-Ola environment. This period predates his long-term career in pinball and already placed him within an industry where electronics, commercial amusement and physical-machine production intersected. The available information establishes this experience without supporting an artificially detailed reconstruction of positions and dates that remain insufficiently documented.

His arrival at Data East came while the new pinball division was still assembling its teams, developing its technical architecture and learning how to manufacture within a market dominated by Williams and Bally. Ropp therefore did not enter an organization with decades of internal procedures behind it. He joined a company that had to build both its machines and its own development methods at the same time.

That situation naturally influenced the work itself. In a young development team, the boundaries between programmer, designer, technician and developer are less rigid than in a highly specialized organization. Problems are solved by smaller groups, and decisions circulate quickly between software, sound, mechanisms and playfield architecture.

Ropp’s career would retain traces of that early environment. Even after Stern developed much more specialized departments, his professional background remained that of a programmer capable of understanding decisions made both before and after the code itself.

1987 | Laser War | Programming Data East Pinball’s first machine

Laser War became Data East Pinball’s first commercial pinball machine in 1987 and Lonnie Ropp’s first documented pinball credit. Beginning a career on the first production from a new manufacturer means working with an architecture that has no existing catalog or internal development history to rely on. Routines, testing methods and the relationships between hardware, software and audio have to be proven directly on a machine intended for commercial release.

The technical environment bears little resemblance to that of a contemporary Stern. Memory is limited, processors offer modest resources and every event has to be designed within constraints that directly influence game design. Adding another reaction, state or sequence is never free. The developer has to decide what deserves to be stored, displayed, played and tracked during the game.

Laser War is also associated with the introduction of a particularly advanced digital stereo sound system for pinball at the time. Software therefore already has to interact with an audiovisual dimension that Data East uses as a point of differentiation. The relationship between programming, sound and immediate machine response would remain important throughout the manufacturer’s later titles.

Ropp then worked on Torpedo Alley, Secret Service and Time Machine in 1988, Monday Night Football in 1989 and Phantom of the Opera in 1990. The production pace of the period allowed him to accumulate, within only a few years, an amount of experience that modern development cycles would distribute across a much longer span.

Data East | Programming with extremely limited resources

Early Data East software operates under severe constraints. Contemporary machines can load large libraries of sound, animation, dozens of modes and substantial quantities of persistent state. A programmer in the late 1980s works under a different logic, where memory limitations force every element to be prioritized.

That restriction is not only technical. It directly affects game readability. When a program cannot endlessly accumulate systems, each rule needs to produce a clear enough response to justify its existence. Events are shorter, the number of states is smaller and the relationship between a shot and its consequence is often more immediate.

The profession also requires close familiarity with hardware. The program does not exist independently from the playfield. It watches switches, fires coils, waits for mechanisms to move, monitors timing and has to handle situations where the ball fails to produce the event the software expected. Even a relatively simple ruleset therefore demands an understanding of the actual behavior of the physical machine.

That background helps explain the versatility Ropp later developed. Programming pinball for years means constantly observing how a layout behaves, which shots naturally return the ball, which mechanisms interrupt sequences and which rules players actually understand when the ball is moving quickly.

1992 | Star Wars | Translating a license through DMD and code

Star Wars places Lonnie Ropp on software in 1992 as Data East increasingly turns toward major licensed properties. The challenge is very different from that faced by a modern Stern. The developer does not have a large LCD capable of showing extended movie sequences or enough storage to integrate a massive library of audiovisual assets.

The universe therefore has to be expressed through a much smaller combination of DMD content, sound, lighting, callouts, scoring and shot relationships. Code plays a major role in the sense of theme because it determines when the machine recognizes an action and what response it associates with that action. A target only truly belongs to Star Wars when the surrounding disciplines give it a function that makes sense within the license.

This generation of Data East machines also demonstrates the growing role of software in licensed integration. A game can use the correct artwork and audio and still feel superficial if the program does not create a coherent relationship between the source material and progression.

Star Wars remains much simpler than major contemporary rules architectures. Its relevance within Ropp’s career comes from its historical position: he is already programming a major license at the point when the DMD is becoming a central component of the pinball experience.

1993 | Jurassic Park | Software surrounding a highly physical playfield

Jurassic Park became one of Data East’s major commercial successes in 1993. Game design is credited to Ed Cebula, Joe Kaminkow and John Borg, while Lonnie Ropp works on software with John Carpenter and Neil Falconer. That distinction matters: Ropp should not be presented as the designer of the playfield simply because his program has to understand every aspect of its operation.

The machine has a strong mechanical presence, including the T-Rex capable of capturing the ball and the Raptor Pit that returns it aggressively. These devices require software to manage states more complex than a simple momentary switch closure. The machine has to know that a ball has been captured, determine what the mechanism should do, synchronize effects and resume play correctly once the ball is returned.

The code also has to absorb the characteristics of a game where several physical events produce fast or unpredictable returns. Software quality therefore depends as much on handling normal operation as on managing situations where the mechanism does not behave exactly according to the theoretical sequence.

Jurassic Park illustrates a central characteristic of Ropp’s work: his proximity to mechanisms does not mean he designed them, but he has to give them a logical existence and integrate their consequences into the rules.

1994 | The Who’s Tommy Pinball Wizard | Software and game design combined

The Who’s Tommy Pinball Wizard represents a different case because Lonnie Ropp receives credits for both game design and software within a collaborative development that also involves Joe Kaminkow, Ed Cebula and Lyman Sheats. Software is likewise developed within a team including Ropp, Lyman Sheats and John Carpenter.

The license has an unusually direct relationship with pinball. Tommy and the Pinball Wizard make the act of playing the machine itself part of the source material. The famous blinder, capable of hiding the flippers from the player, does not merely represent the theme visually. It immediately changes the way the machine is played by removing part of the visual information normally required for control.

The idea works because design and software can be developed together. The physical blinder has to activate in the correct contexts, the rules need to justify its use and the program has to manage the change of state cleanly. The effect would be much less meaningful if it appeared only as an animation disconnected from gameplay.

Tommy remains a Data East machine of its period, with a ruleset less extensive than contemporary titles and several sequences that reveal the more direct structure of early-1990s games. Its integration of the license is particularly coherent, however, and Ropp’s role across both disciplines makes it an important project within his catalog.

1994 | Guns N’ Roses | A music license managed through software

Guns N’ Roses arrives in the same year with a different licensing challenge. Game design is collaborative and includes Joe Kaminkow, John Borg, Lyman Sheats and Slash. Lonnie Ropp works on software with Lyman Sheats and Orin Day. His contribution therefore needs to remain situated within that discipline rather than being expanded into authorship of the entire concept.

A music machine does not provide the same raw material as a film adaptation. Progression cannot simply recreate a sequence of scenes. It needs to organize music, scoring, modes and playfield responses so that the identity of the band remains present throughout a game whose duration is inherently unpredictable.

Software therefore becomes central to orchestration. It determines when sequences begin, how events overlap and how player actions receive responses matching the energy of the license. That responsibility becomes even more demanding when multiballs, magnets and audiovisual events are operating simultaneously.

Guns N’ Roses remains strongly marked by Data East’s mid-1990s design philosophy. Its visual density and some of its behavior can appear less readable today, but its ability to transform the band into an interactive experience does not rely solely on artwork and music. The program forms part of that integration.

Sega Pinball | New branding, continued teams

The transition from Data East Pinball to Sega Pinball does not completely disrupt the development teams. Lonnie Ropp continues within the same industrial lineage, creating a clear human continuity behind the corporate change. Baywatch opens this phase of his catalog in 1995, followed by Apollo 13, Twister, Space Jam, Star Wars Trilogy, The X-Files and eventually Harley-Davidson.

Sega gradually introduces the WhiteStar architecture, new electronic capabilities and a commercial strategy that continues to rely heavily on licensed properties. Software gains resources, but industrial pressure remains strong and development cycles continue to move quickly.

Every platform change forces programmers to rebuild part of their working habits. Routines change, development tools evolve and new resources become available. A career as long as Ropp’s therefore cannot be understood as remaining inside one stable technical environment. It requires several successive periods of relearning.

This era also sees his game-design credits reappear on selected projects, including Space Jam and later Harley-Davidson, while software remains his primary discipline.

1995 | Apollo 13 | Thirteen balls as a software problem

Apollo 13 remains defined by its 13-ball multiball, an extraordinary number of balls released simultaneously onto the playfield. Game design is credited to Joe Balcer and Joe Kaminkow, with a mechanical team including Joe Balcer, John Borg and Rob Hurtado. Lonnie Ropp works on software with Neil Falconer and Orin Day.

That distinction matters because the concept of thirteen balls should not be assigned to Ropp individually. His responsibility begins when the machine has to understand what is actually happening during the sequence. A multiball of this size requires the management of numerous released balls, switches firing almost continuously, scoring, event priorities and the conditions needed to return cleanly to a normal game state as the chaos gradually disappears.

Thirteen balls also reduce the usefulness of individual pieces of information. When several switches can activate within fractions of a second, the code has to determine which events deserve an audiovisual response and which ones can remain secondary. Without that hierarchy, the machine could easily produce an unusable accumulation of sound and information.

Apollo 13 therefore demonstrates one of software’s least visible responsibilities: managing a deliberately excessive situation without completely losing the logical structure of the game. The 13-ball multiball is spectacle before precision, and the number of balls naturally reduces player control. The technical achievement lies in allowing the machine to organize that excess without losing track of its internal states.

1996 | Space Jam | A documented return to game design

Space Jam credits Lonnie Ropp with game design and software alongside Orin Day, within a project where Joe Kaminkow is also involved in design. The machine uses the film’s combination of basketball and Looney Tunes characters and builds several functions around translating the sport directly into shots.

The central basket and its magnetic system illustrate that logic. The ball is not simply fired at a target decorated with a basketball hoop. The machine attempts to reproduce the sporting action within the physical geography of the playfield. Software has to recognize these actions, manage the corresponding scoring and synchronize audiovisual feedback.

Space Jam remains a relatively direct machine whose depth does not approach the larger Stern rulesets developed decades later. Its strengths lie in accessibility, immediate use of the license and an architecture that can be understood quickly by casual players.

For Ropp, the credit mainly confirms that game design was not a single isolated occurrence in his career. He periodically participated in physical design when project structures and team needs allowed him to expand beyond programming.

1997 | Star Wars Trilogy | The same license on another technical generation

Star Wars Trilogy allows Ropp to return in 1997 to a license he had already programmed five years earlier. That relatively short interval makes the comparison useful. The industrial context has changed, Sega WhiteStar provides different capabilities and the development team has accumulated much more experience with DMD presentation and major film licenses.

The difference also demonstrates that a programmer can never treat the development environment as permanently mastered. Electronic platforms evolve, integration methods change and player expectations advance rapidly.

Star Wars Trilogy remains strongly shaped by Sega’s late-1990s design philosophy, with substantial thematic presence but a playfield whose density and certain trajectories can feel less fluid than the strongest layouts of the period. Software accompanies that physical architecture without being able to erase its limitations.

The distinction between code quality and overall machine quality becomes especially important here. A program can manage its functions correctly without turning an average trajectory into an excellent shot. The final experience always depends on the interaction between disciplines.

1999 | Harley-Davidson | Design with John Borg and software

Harley-Davidson represents an important milestone because Lonnie Ropp officially shares game design with John Borg while also handling software. The machine arrives at the exact moment Sega exits the pinball business and Gary Stern acquires the operation that becomes Stern Pinball.

The layout uses a relatively accessible architecture centered on clear trajectories and an approach suited to a license built around the road, motorcycles and Harley culture. The game does not reach the depth of later Stern productions, but its straightforward structure fits the commercial environment of the late 1990s.

Ropp’s dual role creates a direct relationship between geography and logic. Shots can be designed with an understanding of how the code will eventually use them, while rules can be shaped around trajectories that actually work on the physical machine rather than around a theoretical structure applied afterward.

Harley-Davidson also becomes a machine of industrial transition. Produced as Sega Pinball becomes Stern Pinball, it physically connects two periods that Ropp crosses without interruption. Stern would later produce additional runs of the title.

1999 | Sega becomes Stern Pinball

When Sega decides to leave pinball, Gary Stern acquires the division’s assets and establishes Stern Pinball. For part of the team, including Lonnie Ropp, this transition does not represent leaving the profession but continuing the same industrial structure under a new identity.

The context is nevertheless critical. Williams exits pinball during the same period and Stern soon finds itself almost alone in maintaining regular large-scale pinball manufacturing in the United States. The market is considerably more fragile than it had been during previous decades.

Software gradually becomes one of the tools used to extend machine life despite constrained budgets and production volumes. Rules can provide depth that cannot always be achieved through adding more expensive physical mechanisms, while licensed content can be expressed through sounds, modes and sequences without requiring a new toy for every idea.

Ropp brings more than a decade of Data East and Sega experience into the new company. That human continuity forms an important part of the industrial knowledge Stern inherits at its creation.

Early-2000s Stern | Software gains depth

Austin Powers, Playboy, The Lord of the Rings, Terminator 3 and Pirates of the Caribbean mark the early Stern years of Lonnie Ropp’s career. Software begins to take on increasing responsibility for sustaining longer games and differentiating machines whose mechanical packages can sometimes remain relatively contained.

The Lord of the Rings illustrates this shift particularly well. The machine uses a structured progression built around Tolkien’s world, several major objectives and an architecture requiring the player to understand how separate sequences contribute to a larger journey.

Software has to track states, completed objectives, access conditions for major modes and the way multiple systems can interact. This architecture remains less elaborate than some contemporary productions, but it already demonstrates a fundamental change: the game is no longer simply a collection of independent features.

Pirates of the Caribbean continues in this direction with a license and objective structure requiring substantial coordination. Ropp is now working in an environment where code contributes directly to the long-term home-play value that becomes increasingly important to the collector market.

Tournament Play | Software beyond a single game

In 2002, Lonnie Ropp files a patent with Joe Blackwell and Dwight Sullivan covering the integration of Tournament Play into pinball operation. The system addresses distinctions between normal and competitive contexts along with the management of performances and rewards associated with organized play.

A second development is filed in 2004 with Joe Blackwell, Keith Johnson and Dwight Sullivan. This work expands the approach to tournament play and shows the team already treating software as a system capable of organizing an experience larger than the sequence between ball launch and game over.

These patents should not be confused with modern connected infrastructures. The technical context is very different and contemporary player accounts, achievements and online leaderboards do not yet exist in their current forms.

They nevertheless document an important expansion of software thinking at Stern. The program is no longer responsible only for managing the ball and internal rules. It can also modify the environment in which the game itself takes meaning.

Director of Software Game Design | Leadership, hiring and knowledge transfer

With seniority, Lonnie Ropp moves into a documented role as Director of Software Game Design at Stern. This change expands his responsibilities beyond the code associated with one machine and places him within the organization of a department becoming increasingly important to Stern’s product development.

The hiring of Mike Kyzivat provides a concrete example. In 2007, Kyzivat has his first Stern interview with Ropp before joining the company and building a long career within its software organization. Ropp therefore participates in bringing in developers who would later contribute to major machines of the next generation.

Knowledge transfer in pinball software involves much more than mastery of a programming language. Developers need to understand physical ball behavior, game pacing, information hierarchy, switch-detection problems, transitions between states and the ways a mechanism can end up in situations that normal scenarios did not anticipate.

A career beginning with Laser War creates an accumulation of real-world cases that theoretical instruction cannot easily reproduce. The value of that experience therefore appears both in solving problems and in preparing later developers to anticipate them.

2010 | Avatar | Design and software on a modern license

Avatar represents another 2010 project where Stern includes Lonnie Ropp alongside John Borg within its design team, while software is developed by Ropp and Lyman Sheats. Some databases reduce game design to John Borg alone, but Stern’s own presentation associates both Borg and Ropp with the design. That distinction should be preserved without treating their shared involvement as interchangeable authorship of every component.

The machine uses a relatively direct layout around a license requiring a strong representation of Pandora. Mechanisms, moving targets, magnets and the AMP Suit provide physical events that software integrates into objectives and progression.

Avatar remains simpler than the larger rulesets Stern would later develop. Its immediate readability makes the game easy to enter, but repetition can appear earlier for experienced players than on much deeper modern systems.

The project remains important within Ropp’s career because it again combines game design and programming more than twenty years after Laser War. His activity therefore never becomes completely confined to one specialist department despite the gradual increase in team size.

The 2010s | Software becomes a major source of longevity

Iron Man, Big Buck Hunter Pro, Avatar, Transformers, Tron: Legacy, X-Men, Avengers, Star Trek, Mustang, Game of Thrones, WWE WrestleMania, KISS, Ghostbusters and Aerosmith form part of the sequence of software credits associated with Ropp during this period. Not all of these machines assign him complete control over their rules, and several development teams may contribute to the same title.

That distinction becomes increasingly important as Stern specializes its roles. A rules designer may define structures, values and objectives while programmers implement them, manage hardware, build state logic and integrate systems across the machine. Referring simply to “code” can obscure a much more complex organization.

The market changes at the same time. Private gamerooms become increasingly important and a machine has to survive repeated use by the same player. A shallow ruleset quickly reveals its boundaries even when the playfield remains enjoyable.

This places greater pressure on software teams. Stability remains essential, but it is no longer sufficient. The program also has to manage progression, competing strategies, modes, multiballs, scoring and audiovisual content across a much longer ownership cycle.

Star Trek | Physical speed and software architecture

Star Trek in 2013 provides a strong example of the relationship between a flowing physical design and code capable of providing structured progression. Steve Ritchie’s playfield emphasizes fast, relatively clean trajectories. Software needs to exploit that movement without constantly interrupting it with heavy states or sequences requiring long pauses.

The relationship between physical rhythm and software rhythm is critical. A good mode on a fast machine needs to communicate objectives quickly enough that the player can understand them without taking attention away from the ball. Callouts and animations therefore function as interface tools as much as thematic content.

Ropp contributes within that software organization, but the result remains collaborative and should not be converted into a personal signature across the entire ruleset. The importance of the credit lies in his participation on a machine whose physical behavior differs substantially from the Data East and Sega games that formed the beginning of his career.

The transition from Laser War’s alphanumeric environment to an architecture like Star Trek demonstrates how many transformations his profession had already absorbed before Stern even moved to LCD displays.

Game of Thrones | Software as a strategic system

Game of Thrones in 2015 belongs to a generation in which Stern increasingly asks players to manage structured systems. Choices, progression, scoring and interaction between objectives give software a role far beyond running a sequence of independent modes.

An architecture of this type multiplies the number of states that need to be tracked. The program has to know player choices, progression, systems operating simultaneously and the way multiple modifiers affect scoring values.

This depth provides strong longevity but also increases cognitive load. A ruleset can be rich while still demanding substantial effort before a player understands why certain decisions are superior to others. Software therefore has to provide enough information hierarchy to prevent depth from becoming opacity.

Game of Thrones represents the level of complexity that would become increasingly normal in modern Stern development. For Ropp, it adds another stage to a career that began with programs where the amount of possible content was constrained in the opposite direction.

2016 | Ghostbusters | Software, rules and physical difficulty

Ghostbusters combines an unusual playfield, strong thematic presence and several software systems capable of producing dense games. Lonnie Ropp appears within the programming team alongside Dwight Sullivan, Corey Stup, Mike Kyzivat and Tanio Klyce. His credit therefore needs to be understood as part of a collaborative development.

The machine also illustrates what software cannot fix. Certain physical characteristics of the game, including the violence of several ball returns and the overall difficulty of the layout, strongly influence the experience. A well-developed program can provide objectives, rewards and safeguards, but it cannot erase shot geometry or independently alter a physically dangerous return.

That distinction matters when analyzing pinball programmers. A machine can be rich in rules and remain demanding or frustrating because of its physical construction. The reverse is also possible: an excellent playfield can be limited by a shallow code package.

Ghostbusters therefore demonstrates how final quality depends on the convergence of disciplines rather than on any one of them in isolation.

2019 | Stranger Things | Lead programmer on a new Stern generation

Stranger Things represents one of Ropp’s most identifiable recent credits. Stern presents him as lead programmer, with Mike Vinikour involved in game development and Brian Eddy responsible for game design. The machine uses the SPIKE platform and, on Premium and Limited Edition versions, a video projector capable of placing information and effects directly onto physical elements of the playfield.

That feature adds another layer to software responsibilities. The program is no longer commanding only inserts, sound, DMD or LCD content. It has to integrate a device that overlays digital information into the physical space where the ball is moving.

Stranger Things did not ship with all of the code depth it would eventually receive. Updates expanded progression and strengthened several sequences, giving the machine considerably greater maturity than its original release state. That evolution illustrates a major change in modern development: commercial release no longer always marks the end of software production.

The current version makes Stranger Things a far more complete machine, but its development history also demonstrates the risk of this model. An excellent final state does not entirely erase the difference between the machine suggested by its potential and the product delivered to early buyers. Post-release software can become a major strength while also exposing the limitations of launch schedules.

Stranger Things | Video projection and information hierarchy

The projector used on the higher versions of Stranger Things represents an important evolution because it moves part of the interface into the player’s direct view of the playfield. Instead of requiring the player to look away from the ball toward the main display for every piece of information, some feedback can appear directly within the game area.

That capability is only useful if software maintains a clear hierarchy of signals. Projection used too frequently or with excessive visual density could become distracting. Integration therefore has to choose moments when the information genuinely improves understanding or staging.

The device also becomes a thematic tool, especially when it visually transforms areas of the playfield or accompanies the shift toward the Upside Down. Software then connects game state, lighting, audio and projected imagery.

Ropp’s contribution to Stranger Things therefore provides a useful measure of the distance between software in 2019 and software in Laser War. The central principle remains unchanged: a physical action needs to be recognized, interpreted and turned into a coherent response.

2022 | James Bond 007 | An incomplete launch followed by major software development

James Bond 007 places Lonnie Ropp within the software team of a machine designed by George Gomez, with Mike Vinikour heavily involved in rules development. The title provides one of the clearest examples of the difficulties associated with modern releases followed by extended post-launch development.

At launch, James Bond already had an ambitious architecture but code that did not yet represent the complete depth eventually intended for the system. Several progression elements and strategic layers were expanded through later updates, gradually changing how missions, gadgets and overall progression interacted.

The current result is significantly more coherent than the launch version. The machine now benefits from a ruleset offering strategic variety and longevity much closer to the potential of its playfield. That improvement should not erase criticism of the original release state: selling a machine while meaningful portions of the experience remain under construction requires early owners to wait for the product to reach full maturity.

Bond also demonstrates why rules design and software should remain distinct. Structural and scoring decisions cannot simply be attributed to Ropp. His programming role concerns implementation, system operation, interaction between states and stability within a team where Mike Vinikour plays a major role in rules development.

2024 | John Wick | Software with Tim Sexton

John Wick remains, as of September 2026, the most recent identified commercial credit for Lonnie Ropp. Elliot Eismin handles game design, Mike Vinikour rules, Robert Blakeman engineering, and Ropp develops software with Tim Sexton. The division of responsibility shows how much more specialized contemporary teams have become compared with Data East in 1987.

The machine uses a rules architecture built around the assassin universe, contracts, factions and multiple progression systems. Software has to coordinate those layers with a fast playfield where several trajectories can be repeated within very short periods of time.

John Wick has also continued to evolve well after launch, with updates still appearing in 2026. Modern code therefore becomes a maintained product over several years, changing the programmer’s responsibility. Correcting, balancing, extending and protecting established systems against regressions are now normal parts of the development cycle.

The credit becomes especially revealing when compared with Laser War. Ropp is still working with the same fundamentals, switches, scoring, mechanisms, states, failures and responses, but inside an architecture whose number of systems and development personnel bears little resemblance to his first machines.

Software and Rules Design | Related but distinct responsibilities

Lonnie Ropp’s career spans an era during which the separation between programming and rules design gradually became more formal. Early Data East teams naturally encouraged overlap because they were relatively small. A programmer could propose behavior, contribute to a scoring idea or revise a sequence directly in response to what the playfield revealed.

Modern Stern development operates with a far more specialized structure. Designers such as Dwight Sullivan or Mike Vinikour can play major roles in rules design while several programmers share implementation on the same project. A software credit therefore does not automatically mean the programmer invented every rule being implemented.

That separation does not reduce the importance of implementation. An excellent rule integrated poorly can create state conflicts, confusing interface behavior or fragile systems. The program has to understand what can operate simultaneously, how values change and which event receives priority when several actions occur almost at the same moment.

Ropp sits at the intersection of both eras. His game-design credits prove that he has directly worked on machine conception, while his much larger software catalog shows a career primarily built around interactive implementation and system architecture.

Software | Managing the states of a physical machine

A pinball machine does not operate like a video game where the program fully controls and observes the environment. Code watches a physical machine through sensors. It knows that a switch has activated, that a mechanism should have moved or that a ball is expected to be in a certain area, but it never sees the playfield directly the way the player does.

That difference creates large numbers of edge cases. A ball can strike a switch without following the expected path. A mechanism can take longer than anticipated. Two events can occur almost simultaneously. A ball can disappear from one area without immediately reaching the next expected sensor.

The program therefore requires an internal model of the game robust enough to absorb those deviations. Stability is not limited to avoiding software crashes. It also means preserving a coherent game when physical reality produces an unusual sequence.

Ropp’s career length means he has worked on these problems across several generations of technology, but the principle has not changed. Pinball software remains a continuous attempt to apply deterministic logic to an object that is never completely deterministic.

Priorities | When several events happen at once

Modern pinball can produce a large number of events within seconds. One shot can complete an objective, start a mode, award a jackpot, change a multiplier and activate a mechanism almost simultaneously.

The program has to decide which information matters most. A critical callout should not be buried beneath secondary feedback. A progression animation may need to wait until a more important sequence ends. A mechanism still has to receive its command even when the display is occupied by another event.

This hierarchy represents one of the least visible parts of the profession. When everything works correctly, the player does not think about event management. Information simply arrives in an order coherent enough to understand what just happened.

The enormous increase in rules depth between Laser War and John Wick has made this responsibility substantially more complex. The number of simultaneous systems has multiplied while the player’s attention is still primarily focused on one steel ball.

Audio, display and lighting | Software as coordinator

The program is not artistically responsible for music, animation or lighting direction, but it often determines when those assets appear. This coordination places software at the center of the audiovisual experience without transferring authorship of material created by other departments.

A jackpot may require a callout, animation, lighting effect and musical change to occur in exact synchronization. If one arrives too late, the impact of the event weakens even when every individual asset is excellent.

Ropp’s career spans a dramatic evolution in this coordination. Laser War operates with a limited set of signals. Stranger Things and John Wick have to manage large quantities of media and multiple layers of effects capable of triggering within extremely fast gameplay sequences.

The transformation also increases the risk of saturation. A machine responding to everything with equal intensity eventually loses meaningful hierarchy. Software therefore contributes to pacing by determining not only what reacts, but at what level of importance.

Updates | Development no longer ends on the production line

The earliest machines in Ropp’s career could receive ROM revisions, but the process was far more cumbersome than contemporary software distribution. Modern Stern machines can continue to gain content long after the first units have reached customers.

That capability allows bugs to be corrected, scoring adjusted, modes added and the readability of existing systems improved. Stranger Things, James Bond 007 and John Wick all demonstrate the importance of post-release development.

The method provides genuine flexibility, but it also introduces an editorial and industrial risk. The ability to complete a game later can encourage launches where software has not yet reached its final level of depth or polish.

Ropp’s recent career therefore needs to be understood within this context. The quality of modern software should be evaluated both by its current state and by what customers actually received at release.

Regression and maintenance | Larger code creates larger risk

Adding a new system to a mature ruleset can alter behavior far removed from the feature being introduced. A mode may share a switch with another sequence, a scoring change can affect a value already used elsewhere, or a new audiovisual priority can hide an older event.

Post-release development therefore requires regression testing capable of confirming that improvements do not destabilize systems that were already working correctly. This becomes especially important when code continues to evolve for several years.

The amount of content in a contemporary machine makes complete validation impossible for one developer working manually. Software, QA, game development and field testing all need to cooperate to explore the combinations that players will eventually discover.

Ropp began in a period where a program could remain relatively contained within a limited set of primary states. His recent work belongs to an environment where maintaining an existing architecture is as significant a discipline as adding new content.

Four decades of electronic platforms

Lonnie Ropp’s career accompanies several generations of pinball hardware. Early Data East machines use an architecture developed around the needs of a new manufacturer entering the market quickly. Those systems then evolve into more advanced Data East generations and the DMD era.

Sega introduces WhiteStar, a platform that later continues into the early Stern period. Ropp remains active when Stern develops SAM, and then works within SPIKE and the LCD generation.

Every transition creates new constraints and new possibilities. Methods for handling inputs, outputs, sound, display and storage change. Development tools themselves are replaced.

That technological continuity represents one of the most significant parts of his career. Ropp has not spent nearly four decades performing the same type of programming. The profession has changed repeatedly in hardware platform, software scale and organizational complexity.

An influence extending beyond the machine list

The number of credits associated with Lonnie Ropp can make it tempting to measure his importance simply by the quantity of games he programmed. That reading would be incomplete. His career runs through the entire Data East, Sega Pinball and Stern Pinball lineage, eventually including leadership, hiring, knowledge transfer and work on systems extending across more than one machine.

The Tournament Play patents show that expansion toward functions operating beyond a single ruleset. His involvement in hiring Mike Kyzivat documents another form of influence, this time through the people who continued developing Stern software alongside and after him.

His game-design work remains smaller in volume than his software output but should remain part of his professional identity. The Who’s Tommy, Space Jam, Harley-Davidson and Avatar represent different periods during which he participated directly in physical design in addition to programming.

That combination explains why his profile cannot be reduced to that of a historical programmer preserved inside one fixed technical role. His responsibilities change with the machines and with the industrial organization producing them.

Skills & Roles

Software Development | Pinball Programming | Game Design | Rules Implementation | State Management | Gameplay Systems | Hardware Integration | Audiovisual Integration | Software Architecture | Technical Leadership

Major Machines and Credits

Year

Machine

Manufacturer

Documented Role

1987

Laser War

Data East

Software

1988

Torpedo Alley

Data East

Software

1988

Secret Service

Data East

Software

1988

Time Machine

Data East

Software

1989

Monday Night Football

Data East

Software

1990

Phantom of the Opera

Data East

Software

1992

Lethal Weapon 3

Data East

Software

1992

Star Wars

Data East

Software

1993

Jurassic Park

Data East

Software

1993

Last Action Hero

Data East

Software

1993

Adventures of Rocky and Bullwinkle and Friends

Data East

Software

1994

The Who’s Tommy Pinball Wizard

Data East

Game Design / Software

1994

Guns N’ Roses

Data East

Software

1994

Maverick

Data East

Software / Concept

1995

Baywatch

Sega Pinball

Software

1995

Apollo 13

Sega Pinball

Software

1996

Space Jam

Sega Pinball

Game Design / Software

1997

Star Wars Trilogy

Sega Pinball

Software

1999

Harley-Davidson

Sega / Stern

Game Design / Software

2001

Austin Powers

Stern Pinball

Software

2002

Playboy

Stern Pinball

Software

2003

The Lord of the Rings

Stern Pinball

Software

2003

Terminator 3

Stern Pinball

Software

2006

Pirates of the Caribbean

Stern Pinball

Software

2008

Indiana Jones

Stern Pinball

Software

2008

CSI

Stern Pinball

Software

2009

24

Stern Pinball

Software

2009

NBA

Stern Pinball

Software

2010

Iron Man

Stern Pinball

Software

2010

Big Buck Hunter Pro

Stern Pinball

Software

2010

Avatar

Stern Pinball

Design Team / Software

2011

Transformers

Stern Pinball

Software

2011

Tron: Legacy

Stern Pinball

Software

2012

X-Men

Stern Pinball

Software

2012

Avengers

Stern Pinball

Software

2013

Star Trek

Stern Pinball

Software

2014

Mustang

Stern Pinball

Software

2015

Game of Thrones

Stern Pinball

Software

2015

WWE WrestleMania

Stern Pinball

Software

2015

KISS

Stern Pinball

Software

2016

Ghostbusters

Stern Pinball

Software

2017

Aerosmith

Stern Pinball

Software

2019

Stranger Things

Stern Pinball

Lead Programmer

2022

James Bond 007

Stern Pinball

Software

2024

John Wick

Stern Pinball

Software

Key Dates and Contributions

Year

Milestone

Significance

1987

Laser War

First documented pinball credit and first commercial production from Data East Pinball.

1992

Star Wars

Software on one of Data East’s early major film licenses of the DMD era.

1994

The Who’s Tommy Pinball Wizard

Game design and software on a collaborative project strongly integrated with its license.

1995

Apollo 13

Software on the machine featuring the 13-ball multiball.

1996

Space Jam

Game design and software.

1999

Harley-Davidson

Game design with John Borg and software during the Sega / Stern transition.

2002

Tournament Play

First patent filing with Joe Blackwell and Dwight Sullivan covering competitive play.

2004

Extended Tournament Play

Further development with Joe Blackwell, Keith Johnson and Dwight Sullivan.

2007

Software recruitment

Interviewed Mike Kyzivat during his entry into Stern.

2010

Avatar

Documented participation in the design team with John Borg and software with Lyman Sheats.

2019

Stranger Things

Lead programmer on a SPIKE machine integrating video projection on Premium and LE.

2022

James Bond 007

Software on a rules architecture substantially expanded after release.

2024

John Wick

Software with Tim Sexton on the machine designed by Elliot Eismin.

2026

John Wick

Software development continues through updates while it remains Ropp’s most recent identified commercial credit.

Lonnie D. Ropp | Software Development and industrial continuity in American pinball

Lonnie D. Ropp begins his documented pinball career with Laser War in 1987 and then follows the same industrial lineage through Data East, Sega Pinball and Stern Pinball. That continuity takes him through several major transformations of the medium: the transition from alphanumeric displays to DMD, the move to WhiteStar and then SAM and SPIKE, the arrival of LCD, the expansion of rulesets, increasingly specialized teams and post-release development becoming a normal part of contemporary pinball.

Software remains his primary field, but his career also includes several clearly documented game-design responsibilities. The Who’s Tommy Pinball Wizard, Space Jam, Harley-Davidson and Avatar represent different forms of that involvement. Those credits need to remain distinct from machines such as Jurassic Park, Apollo 13, Guns N’ Roses or John Wick, where his documented role belongs to software and does not support attribution of the layout or complete rules architecture.

His progression into Director of Software Game Design responsibilities, his involvement in hiring and his work on Tournament Play add a structural dimension to the catalog. Ropp contributes not only to individual machines but also to the continuity of software expertise transferred between several generations of Stern programmers.

As of September 2026, John Wick remains his most recent identified commercial credit. His documented career therefore spans thirty-seven years between Laser War and that production, with continuous adaptation to technical platforms and organizational structures that changed fundamentally over the same period. Lonnie Ropp’s importance within the industry rests as much on that continuity as on the number of machines carrying his name in their software credits.

Highlights

  • Software Development
  • Pinball Programming
  • Game Design
  • Rules Implementation
  • State Management
  • Gameplay Systems
  • Hardware Integration
  • Audiovisual Integration
  • Software Architecture
  • Technical Leadership

Key dates

  1. Laser War First documented pinball credit and first commercial production from Data East Pinball.

  2. Star Wars Software on one of Data East’s early major film licenses of the DMD era.

  3. The Who’s Tommy Pinball Wizard Game design and software on a collaborative project strongly integrated with its license.

  4. Apollo 13 Software on the machine featuring the 13-ball multiball.

  5. Space Jam Game design and software.

  6. Harley-Davidson Game design with John Borg and software during the Sega / Stern transition.

  7. Tournament Play First patent filing with Joe Blackwell and Dwight Sullivan covering competitive play.

  8. Extended Tournament Play Further development with Joe Blackwell, Keith Johnson and Dwight Sullivan.

  9. Software recruitment Interviewed Mike Kyzivat during his entry into Stern.

  10. Avatar Documented participation in the design team with John Borg and software with Lyman Sheats.

  11. Stranger Things Lead programmer on a SPIKE machine integrating video projection on Premium and LE.

  12. James Bond 007 Software on a rules architecture substantially expanded after release.

  13. John Wick Software with Tim Sexton on the machine designed by Elliot Eismin.

  14. John Wick Software development continues through updates while it remains Ropp’s most recent identified commercial credit.

Associated machines

9 machines