Pinball Xperience
Luke Peters

Luke Peters

Current position
Rules Designer | Software Developer | Development Director

Biography

LUKE PETERS

Director of Rules and Code Development | Spooky Pinball

Luke Peters holds a central position in contemporary Spooky Pinball, but understanding his role first requires correcting a confusion that appears even in some specialist databases: Luke Peters is not “Spooky Luke.” Spooky Luke is Lukas Kastner, currently Chief Operating Officer and game designer for the manufacturer. Luke Peters is another member of the team, officially presented by Spooky as Director of Rules and Code Development. The distinction changes the interpretation of many credits. Kastner works with Corwin “Bug” Emery on the physical architecture of recent playfields; Peters works on rules design, their development and, depending on the project, either directly on software or in the direction of the team implementing it.

His first clearly identifiable commercial credits appear around Halloween and Ultraman: Kaiju Rumble! in 2021, before his influence becomes much easier to read on Scooby-Doo, Where Are You! and then Looney Tunes. On the latter, Spooky directly credits him with story/rules design while Eric Priepke handles the code. The Texas Chain Saw Massacre, Evil Dead and Beetlejuice then broaden his involvement inside teams where rules, narrative and programming are distributed across several creators. His current position gives that progression a clear logic: Luke Peters works on the layer that transforms a physical playfield into a playable system, determining how objectives open, how progressions intersect, what is retained or lost, how a license becomes a sequence of actions, and how that architecture is ultimately translated into code.

His career also reflects a wider transformation at Spooky. The manufacturer’s earliest games could still concentrate many responsibilities among a handful of highly versatile people. Recent productions require a clearer separation between game design, engineering, rules, software, animation, audio and integration. Peters sits directly inside that evolution. His work does not appear as a ramp or sculpture, but it determines a large part of what the player understands after launching the ball: why a shot matters, what it just accomplished, what it prepares, what can be combined and how far the game can ultimately progress.

Identity

Name

Luke Peters

Profession

Rules Designer | Software Developer | Development Director

Primary Manufacturer

Spooky Pinball

Current Role

Director of Rules and Code Development

Primary Field

Rules Design | Code Development

Other Documented Fields

Story Development | Software | Game Development

First Commercial Credit Cycle

Halloween | Ultraman: Kaiju Rumble!

Major Machines

Halloween | Ultraman | Scooby-Doo | Looney Tunes | The Texas Chain Saw Massacre | Evil Dead | Beetlejuice

Particularly Clear Credit

Story / Rules on Looney Tunes

Professional Location

Spooky Pinball, Benton, Wisconsin

Not to Be Confused With

Lukas Kastner, aka Spooky Luke

Public information documents his work on machines much better than his personal biography. His date of birth, education and professional history before Spooky are not documented with enough confidence to include here. That absence should not be filled by associating him with unrelated people named Luke Peters: the name is common, and several profiles with no connection to pinball appear in searches.

Two Lukes at Spooky | A Necessary Distinction

The confusion between Luke Peters and Spooky Luke is widespread enough to distort entire filmographies. Spooky’s own team structure separates them clearly. Lukas Kastner, Spooky Luke, is Chief Operating Officer and Game Design. Luke Peters is Director of Rules and Code Development. When Scooby-Doo, Looney Tunes, Evil Dead or Beetlejuice list “Spooky Luke” under game design, that credit belongs to Kastner. When Luke Peters appears under rules or software, it refers to Peters.

That distinction also helps explain how Spooky develops machines today. Corwin “Bug” Emery and Lukas Kastner define much of the physical terrain of recent projects: shot architecture, zones, circulation and major physical devices. Luke Peters works on what that terrain asks the player to do and how those actions are interpreted by the system. The same ramp can launch a mode, increase progress, lock a ball, modify a multiplier or become strategically irrelevant in another state. The wood remains unchanged; the rule changes its meaning.

Rules Design | Giving the Playfield a Function

A playfield creates possibilities. Rules design turns them into decisions. A ramp does not become strategically interesting simply because it exists, but because a rule determines what it opens, what it scores, what it risks closing or how it interacts with other objectives. That layer sits at the center of Luke Peters’ work.

On a modern pinball machine, this extends far beyond writing a list of modes. Multiple progression ladders must be built, persistence between balls has to be defined, scoring needs structure, multiball conditions must be controlled, priorities have to be established when several features are active, tournament exceptions must be considered, action buttons need functions, the interface must reflect the actual state of the game and all of it has to remain understandable while the ball continues moving. As the game grows richer, rules design increasingly resembles systems architecture.

The challenge is even greater at Spooky, whose recent games rely heavily on thematic mechanisms. Rules cannot ignore hardware. A lock, trap door, upper playfield or animated toy needs a reason to activate and a coherent rhythm of use. A spectacular device triggered without strategic purpose quickly becomes a mechanical animation; connected to readable progression, it can become one of the moments the player actively works toward.

2021 | Halloween | Early Credits in Spooky’s Modern Generation

Halloween represents one of the earliest clearly documented commercial credits in Luke Peters’ career. The machine uses a physical architecture built around the John Carpenter license, with several zones, central drop targets, the Strode house and Smith’s Grove. Corwin “Bug” Emery contributes to the rules and David Fawcett handles the initial software; Luke Peters also appears within the rules development credits associated with the project and later becomes involved in the software evolution of this generation.

The ruleset transforms murders, chases and confrontations with Michael Myers into a series of modes accessible through central objectives. The game alternates narrative modes, multiballs and progressions associated with specific devices. The approach remains coherent with the film: instead of replaying Halloween chronologically as a closed campaign, the game breaks its major scenes and characters into objectives the player can gradually encounter.

Halloween also exposes a weakness Spooky will continue to face: the distance between the ambition of a ruleset and its level of completion at launch. The machine receives a long sequence of updates, fixes and balancing changes. For Peters, this period therefore represents both an entry into rules design and an introduction to software as a living product capable of evolving long after physical production has started.

Ultraman: Kaiju Rumble! | Same Terrain, Different System

Ultraman shares much of its physical architecture with Halloween, but the two machines aim for different thematic experiences. Luke Peters is documented within Ultraman’s software and rules development alongside David Fawcett and Corwin Emery. Comparing the two games already demonstrates an important principle: a shared layout does not force two machines to share the same strategic identity.

Shots can remain physically similar while objectives, progressions and scoring conditions completely recontextualize them. Halloween uses the playfield to track and replay situations drawn from the film; Ultraman transforms the same basic structure into Kaiju battles, escalating power and combat progression. The ability to reprogram the meaning of the same physical terrain becomes even more visible later with Looney Tunes and The Texas Chain Saw Massacre.

Scooby-Doo, Where Are You! | Peters’ First Major Rules Architecture

Scooby-Doo represents a much clearer milestone in his career. Corwin “Bug” Emery and Lukas Kastner handle game design. Duane Foust contributes engineering, Spooky DJ handles software and Luke Peters takes on rules design, with close collaboration between rules and code. The source material is especially rich: Mystery Inc., monsters, investigations, Scooby Snacks, the Mystery Machine and episodes from the original series provide several natural layers of progression.

The player begins by selecting a member of Mystery Inc., with specific advantages affecting the game. Fred can influence Mystery Machine Multiball progress, Velma makes clue collection easier, Scooby changes outlane protection, while Daphne and Shaggy alter other parameters. These choices do not replace the core ruleset but slightly change how the player approaches it. Peters therefore uses the characters as gameplay variables rather than simple avatars displayed on screen.

The structure then expands into Case Modes, Character Modes, multiple multiballs and wizard modes. Mystery Machine Multiball requires preparation followed by locking three balls; Captain Cutler strongly uses the upper playfield; Scooby Snack Multiball uses targets and apron locks. Long-form progression ultimately leads toward Would’ve Gotten Away With It and other endgame objectives. The result gives Scooby-Doo considerable depth, but also reveals one of the risks of this approach: when too many systems progress simultaneously, the player may understand the theme instantly while taking far longer to understand what truly matters strategically.

Scooby-Doo | A Machine Whose Code Keeps Growing

Scooby-Doo also demonstrates the limitations of software development continuing after commercialization. Several announced functions or systems already embedded in the rules architecture are expanded, corrected or completed across later updates. Character perks, wizard modes, stacking opportunities, operator settings and the behavior of specific sequences continue evolving.

This progression creates two valid readings. Over time, it gives the machine a richness its early version could not fully deliver and demonstrates the team’s ability to use actual player feedback. At the time of purchase, however, it can also create the sense that part of the software promise arrives after the physical machine. That tension remains central to Peters’ role: directing rules development means not only defining the destination, but managing the distance between that destination and the version actually delivered.

Character Select | Light Asymmetry Rather Than a Different Game

Scooby-Doo’s character selection provides a good example of how Peters uses a license. Fred, Daphne, Velma, Shaggy and Scooby do not need five completely separate campaigns to exist meaningfully inside the ruleset. Their perks modify systems that are already present and encourage players to choose according to preference or weakness.

The system remains intentionally less radical than a complete rules transformation. Players preserve their general knowledge of the machine while gaining small strategic variations. The idea works especially well for a theme centered on a group whose members each have an easily recognizable role.

Wizard Modes | Giving the Subsystems a Destination

A large number of modes only creates long-term value if the player understands where they lead. Scooby-Doo uses several upper progression levels to connect investigations and characters. Would’ve Gotten Away With It requires engagement with the different Case Modes before turning previously encountered antagonists into a concluding sequence.

This construction reveals one of the stronger elements in Peters’ rules design: systems accumulated during the game tend to return within higher objectives instead of remaining completely isolated. Depth gains a destination. The more branches a wizard mode requires, however, the more important it becomes to make the route toward that destination readable.

2023 | Looney Tunes | The Credit That Best Defines His Role

Looney Tunes is one of the clearest ways to understand Luke Peters as a rules designer, not because the machine is necessarily his most complex ruleset, but because responsibilities are unusually well defined. Corwin “Bug” Emery and Lukas Kastner handle game design, Duane Foust engineering, Spooky DJ electronics, Eric Priepke software and Spooky directly credits Peters with story/rules design.

The game takes place in an ACME factory where film reels have been scattered. That concept immediately gives the game structure: shots recover Film Reel Segments, which then unlock episodes inspired by classic cartoons. Another branch uses the spinner to open Area 51 & 3/4. ACME Items, Roadrunner, combo jackpots, different multiballs and Blueprints layer around this main progression without all demanding the same actions.

Its success comes from the relationship between theme and function. An episode is not merely “Mode 4” covered by a video. Film reels, ACME devices, Roadrunner speed and Taz can all be understood as concepts from the cartoons before the player knows their exact scoring values. The license therefore becomes part of the teaching language of the ruleset.

Looney Tunes | Episodes, ACME and Multiple Scoring Paths

Episodes form the main narrative branch. The player collects film segments on shots, then uses the ACME Crate or Vault to launch a sequence. Several episodes use their own structures rather than repeating a simple timed sequence of lit arrows. Some introduce stages, mistakes or special behaviors designed to evoke the cartoon they reference.

Around that branch, Peters builds secondary economies. ACME Items operate as tools or rewards, Roadrunner develops a speed-related progression and can influence multipliers, while combos create another reason to link specific trajectories. Giant Rocket Multiball, Rocket Skates Multiball, Anvil Frenzy and TNT Add-A-Ball use physical mechanisms as strategic events rather than mere spectacle.

The richness is real, but the editorial weakness should also be stated clearly: Looney Tunes can demand a great deal from players who want to go beyond simply starting an episode and shooting what flashes. Sub-economies, access conditions and feature interactions create a machine with strong long-term depth, but strategic reading takes time. Strong thematic cohesion reduces that difficulty without eliminating it.

Duck Amuck | Using the Source Material as Wizard Mode Architecture

The choice of Duck Amuck as an advanced objective is particularly revealing. The cartoon revolves around Daffy Duck being tormented by an animator who changes his environment, appearance and even the rules governing his world. The source material is therefore naturally suited to a wizard mode capable of modifying the game’s usual behavior.

This is one of the clearest examples of strong license adaptation in rules design. The original material does not simply provide a name for a feature that already existed; it inspires the feature itself. When this relationship works, the player can understand the thematic joke and the gameplay concept at the same time.

Looney Tunes | A Solid Initial Code Followed by Real Maturation

Looney Tunes launches with a structured rules foundation, then receives several waves of development: new episodes, Taz Mania, scoring changes, qualification adjustments, revisions to ACME Items, multiballs, bonus behavior, callouts and lock logic. The public version available in early 2024 is therefore not the end of development but the beginning of a longer maturation period.

Again, continuous development has two sides. Updates can correct behaviors that hundreds of internal test games may not reveal and enrich systems after observing real-world play. They also show how heavily scope must be controlled by a rules director. Every new idea adds exceptions, interactions with already active modes and potential bugs that grow rapidly with each added feature.

The Texas Chain Saw Massacre | Same Physical Architecture, Radically Different Rules

The Texas Chain Saw Massacre shares its general architecture with Looney Tunes but produces a completely different experience. Game design remains with the Bug Emery / Lukas Kastner partnership. Benjamin Heckendorn handles a central part of the software and contributes alongside Bug Emery, Hilton Jones and Luke Peters to rules and narrative development.

The comparison with Looney Tunes is especially useful for understanding Peters’ work. On similar physical terrain, the objectives become pursuit, capture, violence, preparation for the Sawyer family and progression through the world of the film. The ramps and repeatable trajectories do not physically change, but the reasons for shooting them, the order in which they matter and the way the game contextualizes them significantly alter the perception of the playfield.

The credit is shared, which prevents any individual rule from being assigned to Peters without direct documentation. His involvement must be understood within a group where Ben Heck contributes major software work, Bug Emery brings broader creative and narrative direction and Hilton Jones also participates in story/rules development. The Texas Chain Saw Massacre confirms his role in rules architecture without turning every feature into an individual credit.

Two Opposite Licenses | Rules as the Second Identity of a Layout

Looney Tunes and The Texas Chain Saw Massacre offer a particularly strong demonstration of how important rules design can be. Two machines may share a physical shot architecture without asking the player to think in the same way. Callouts, modes, rewards, locks and progressions rebuild the meaning of those trajectories.

The experiment goes beyond the industrial efficiency of reusing a playfield platform. It demonstrates that physical architecture represents only part of the experienced game design. The player never plays geometry alone; the player plays the decisions that software assigns to that geometry.

2024 | Evil Dead | A Rules Architecture Split Across Two Films

Evil Dead returns to a collective rules structure. Corwin “Bug” Emery and Lukas Kastner handle physical game design, Ben Heck takes charge of initial software and participates in rules alongside Bug Emery, Hilton Jones and Luke Peters. The machine uses the first two Sam Raimi films and immediately asks players to choose between their progressions. That decision directly structures access to modes: four major modes are associated with each film, accompanied by intermediate stages and eventual wizard modes.

The modes themselves are often divided into several phases. Evil Awakens, Hacked to Bits, Undying Love, Hello Lover and Evil Ash do not simply light a uniform sequence of arrows. Targets, ramps, the cellar, the hand, loops and other mechanisms change function according to the sequence. Deadites, Cabin Multiball, Boomstick Multiball, Blood Flood, Mystery and Linda Tricks add more transversal systems capable of interacting with the cinematic progression.

That density suits Evil Dead, a series where objects, severed limbs, traps and tonal shifts constantly create new situations. It also produces one of Spooky’s largest software challenges. When several modes, multiballs, physical states and features can overlap, every interaction becomes another scenario the code must handle without contradiction.

Good Linda / Bad Linda | Turning a Thematic Choice Into Risk

The Good Linda / Bad Linda system shows especially well how a license element can become a player decision. Linda’s state affects the difficulty and potential value of certain sequences: a more favorable state can make some objectives easier while reducing their scoring ceiling, while a more hostile state increases risk in exchange for greater potential.

That type of rule is more interesting than a simple themed bonus because it changes the decision itself. The player does not merely collect a reference to the film; the player accepts a strategic tradeoff with the machine. The theme therefore directly supports risk and reward.

Evil Dead | The Clearest Example of the Post-Launch Code Problem

Evil Dead’s software history is extensive. Across 2025 and 2026, the game receives new multiballs, modes, sub-wizard modes, wizard modes, Video Mode, Spooky Tokens, scoring revisions, ball-save changes, Mystery improvements, new Linda behavior, tournament options, stacking corrections and a long series of fixes involving VUKs, switches, mechanisms and game states. Kandarian Demon, Destroy the Book, Hero From The Sky and Hail to the King gradually join the existing architecture.

This evolution demonstrates the ability of the team, with Peters directing the rules/code side, to continue developing a commercial machine in depth. It also exposes a clear weakness in the model. Evil Dead begins its commercial life before all of its upper progression is available. For an owner, the idea of a game being enriched across two years can be attractive; it does not replace the reasonable expectation that a premium-priced machine arrives with sufficiently complete software.

As Director of Rules and Code Development, Peters carries particular responsibility for that balance. The goal is not to eliminate post-launch evolution. A connected pinball machine benefits from corrections and new ideas. The real measure is whether future updates represent enrichment or whether they are required to deliver parts of the core experience that should already have been present.

Spooky Tokens | Turning Later Development Into Replayable Access

The addition of Spooky Tokens to Evil Dead demonstrates an interesting way to make advanced content more accessible once implemented. Tokens can be earned during play and later spent to access certain sub-wizard or wizard modes directly. The system reduces frustration for players who want to revisit difficult-to-reach content without removing the normal campaign.

It also reflects a broader change in home pinball. A machine in a private collection is not used only like an arcade game where every attempt starts from zero. Persistence, profiles, tokens and shortcuts can become tools for exploring software over weeks or months. Peters works in a period where rules design increasingly has to account for this long-term domestic relationship with a machine.

Director of Rules and Code Development | Designing, Then Making It Converge

Luke Peters’ current role extends beyond being the rules designer of one title. Director of Rules and Code Development means coordinating a space where creative intentions and technical constraints have to remain aligned. A mode may sound excellent on paper and still become poor gameplay if it requires a mechanism to remain in the wrong position for too long, interrupts flow too aggressively or conflicts with three other active systems. Conversely, stable code with too few meaningful decisions can produce a technically clean but shallow game.

The role also requires collaboration with programmers who bring very different approaches. David Fawcett, Spooky DJ, Eric Priepke, Ben Heck and Casey Butler all appear across this period. Peters therefore should not be credited as the sole author of their code. His influence lies in rules definition, development, overall coherence and, on certain titles, direct software contribution.

Code direction also requires prioritization. Blocking bugs, missing rules, scoring balance, additional content and quality-of-life improvements do not carry the same urgency. A small development team cannot build everything simultaneously. Part of Peters’ role is deciding which areas need to be addressed first so the game remains coherent as versions continue to change.

2025 | Beetlejuice | From Rules Contributor to Established Software Direction

Beetlejuice represents another step forward. Corwin “Bug” Emery and Lukas Kastner remain responsible for physical game design. Christopher Franchi handles the artwork. Software brings together Spooky DJ, Casey Butler and Luke Peters, while Peters’ official Director of Rules and Code Development position gives him a structural role within the project.

The playfield uses a motorized Sandworm as a central presence, the Waiting Room upper playfield, multiple ramps, scoops, locks and several devices directly tied to the film. The ruleset has to give each one a purpose without reproducing the overload that can occur when every feature demands attention simultaneously. Beetlejuice returns to a standard cabinet after Evil Dead, but the game still relies on many mechanical states and thematic sequences.

Peters’ relevance on this project therefore lies less in one signature mode than in the convergence of the entire system. Spooky DJ and Casey Butler work on code, game design imposes physical mechanisms, the movie provides a large audiovisual library and Spooky Speak introduces another form of player input. Rules/code direction has to make those elements behave as one game.

Beetlejuice | Spooky Speak and a New Layer of Interaction

Spooky Speak introduces voice control into selected machine interactions. The idea is especially appropriate for Beetlejuice, a film where saying a name three times is one of the best-known rules of the story. Turning that concept into a real pinball function gives the theme a presence extending beyond artwork or video.

It would nevertheless be incorrect to assign the invention or entire implementation of Spooky Speak to Luke Peters without more specific technical documentation. His role lies within the team responsible for integrating the interaction into the broader ruleset and software. A voice command needs to understand the current game state, accept or reject an action, provide a physical alternative where necessary and never make progression dependent on unreliable recognition.

The feature also illustrates how much the profession has changed. A modern rules designer no longer works only with switches, coils and scoring. Action buttons, profiles, networking, peripherals, toppers and now voice commands can all become inputs into the game system.

Rules as the Interface Between License and Player

Nearly every machine connected to Luke Peters uses a strong license. Halloween, Ultraman, Scooby-Doo, Looney Tunes, Texas Chainsaw, Evil Dead and Beetlejuice arrive with characters, objects and scenes already familiar to their audiences. Part of his work is translating that cultural memory into actions.

The translation works best when the rule feels natural inside the source material. Searching for clues in Scooby-Doo, recovering cartoon reels in Looney Tunes, choosing between two films in Evil Dead or speaking Beetlejuice’s name do not require the player to forget the license in order to understand the system. The theme already provides part of the vocabulary.

The opposite risk is trying to integrate every reference. A rich license can produce an inflation of modes, sub-modes, collectibles and exceptions until the main structure becomes difficult to perceive. Peters therefore works continuously between two goals that can conflict: exploiting the depth of the source while preserving a hierarchy the player can actually learn.

Readability | The Major Challenge of Modern Spooky Rulesets

Recent Spooky games do not lack content. Their difficulty more often lies in how clearly that content is organized. Scooby-Doo can layer character selection, cases, clues, multiballs, snacks, side quests and wizard progressions. Looney Tunes combines episodes, ACME systems, Roadrunner, Area 51 & 3/4, combos and several multiballs. Evil Dead adds film selection, eight primary modes, sub-wizards, wizard modes, Linda, Deadites, tokens, video modes and additional side economies.

For expert players, that density supports long-term discovery and strategy. For newcomers, it can delay the moment when the machine clearly reveals what matters. Peters’ strongest work appears when theme, insert, callout and rule converge strongly enough that the intended behavior becomes intuitive. The weaker moments appear when software depth requires too much external knowledge before it becomes readable.

Stacking | Where Depth Becomes Architecture

Stacking is one of the places where modern rules quality is tested most severely. Allowing a multiball to coexist with a mode can create extremely rich sequences, but every combination raises questions: which timer continues, which event receives audio priority, which jackpots count toward multiple systems, what happens when a mechanism required by two features needs to move into different states?

Spooky’s update histories show how many of these interactions require later corrections. Peters therefore works in an area where depth and stability are directly connected. Adding a new system costs more than the time required to program that system alone; it also requires checking its behavior against everything that already exists.

Software | Writing the Rule Is Not Enough

Luke Peters’ move toward code direction highlights a basic truth of modern pinball. A rule only truly exists once it has been implemented, displayed, lit, scored, tested and made capable of surviving unexpected states. A player can tilt during a transition, drain while a mechanism is opening, start two features almost simultaneously or trigger ball search at an awkward moment. Software must always return the machine to a coherent state.

Peters therefore operates between design and execution. Depending on the machine, he writes rules, contributes code or directs development while another programmer handles most of the implementation. That flexibility explains why his name appears differently from title to title and why a single “Software” column does not adequately describe his work.

Continuous Development | A Strength That Needs Control

Spooky relies heavily on post-launch updates. Scooby-Doo, Looney Tunes and Evil Dead all receive major revisions long after initial deliveries. For a small team, the approach allows software development to continue without delaying physical production for many additional months.

It also allows the community to become a large-scale source of observation. Thousands of games across the installed base expose dominant strategies, scoring exploits, bugs, unclear feedback and rules used less often than expected. Strong software support can therefore improve a machine significantly.

The limit is both economic and editorial. An update adding a bonus mode is an expansion; an update delivering an essential part of the expected progression is correcting something that was missing. Rules/code direction also has to manage that boundary. Recent Spooky games show substantial post-launch improvements, but they also reveal a tendency to make future versions carry part of the weight of the product already sold.

A Signature Still Being Defined

Luke Peters now has enough machines behind him for several tendencies to become visible, but his work remains heavily collaborative. It would be excessive to turn every mechanic in Scooby-Doo, Evil Dead or Beetlejuice into a personal signature. Credits repeatedly involve Bug Emery, Hilton Jones, Ben Heck, Spooky DJ, Eric Priepke or Casey Butler.

Several patterns nevertheless emerge. Licenses are used as rules structures rather than simple naming layers. Parallel progressions are common. Games frequently offer several destinations rather than a single linear route. Physical devices are reused across different rule contexts. Finally, rulesets often continue evolving long after their first public version.

This approach produces rich, generous machines, but also increases the need for hierarchy, feedback and scope control. Those three areas will be especially important in evaluating how Peters’ work develops from here.

Strengths | Turning the License Into a System

The strongest quality of Peters’ work lies in the way many rules grow directly from the theme. Scooby-Doo turns investigation and the gang into progression structures; Looney Tunes organizes its campaign around missing films, ACME and characters; Evil Dead uses the choice between two movies, Linda and Deadites; Beetlejuice even uses the player’s voice.

Another strength is long-term depth. Machines Peters contributes to rarely reveal everything within a handful of games. Intermediate objectives, combinations, progression choices and wizard modes provide many layers to learn.

His experience with code adds another important dimension. A rules designer who understands implementation constraints can anticipate interactions, impossible states and the real development cost of a feature more effectively. His current role formalizes that relationship between imagination and feasibility.

Limitations | Density, Readability and Launch Maturity

Density remains the main area of concern. Adding several systems does not guarantee that their relationships will be understandable. A machine can contain ten interesting progressions while still making the player feel unsure which one is actually being advanced. Scooby-Doo and Evil Dead occasionally show this problem, especially before the player develops a solid understanding of the ruleset.

The second limitation concerns software maturity during early deliveries. Long update histories demonstrate significant development commitment, but also reveal that some machines reach their most complete form well after release. Development direction will need to reduce that distance if Spooky wants to preserve the ambition of its current rulesets without making post-launch work necessary to reach the expected level of completion.

Finally, additional interactions increase the risk of bugs involving stacks, timers, ball saves, VUKs, modes and mechanical states. The many corrections applied to recent productions provide concrete evidence of that challenge. Depth therefore cannot be evaluated separately from stability: the best rules architecture is one whose complexity can be explored without repeatedly exposing the technical limits beneath it.

Skills & Roles

Rules Design | Code Development | Rules Architecture | Software Direction | Story Development | Progression Design | Scoring Systems | Mode Design | Interactive Systems | Post-Launch Development

Major Pinball Credits

Year

Machine

Documented Role

2021

Halloween

Rules Development | involvement in later code evolution

2021

Ultraman: Kaiju Rumble!

Rules / Software Development

2022–2023

Scooby-Doo, Where Are You!

Rules | development with Spooky DJ

2023

Looney Tunes

Story / Rules

2023

The Texas Chain Saw Massacre

Rules / Story Development, shared credit

2024

Evil Dead

Rules, shared credit | later software development

2025

Beetlejuice

Software / Rules & Code Development

2026

Spooky Pinball

Director of Rules and Code Development

This filmography must not be confused with Lukas Kastner’s. “Spooky Luke” game design credits on Scooby-Doo, Looney Tunes, The Texas Chain Saw Massacre, Evil Dead and Beetlejuice belong to Kastner. Luke Peters works on rules, code and their direction. Keeping that separation clear is essential for correctly attributing each person’s contribution.

Primary Collaborations

Creator

Field

Collaboration

Corwin “Bug” Emery

Creative Direction | Game Design | Rules

Halloween | Ultraman | Scooby-Doo | TCM | Evil Dead | Beetlejuice

Lukas Kastner, Spooky Luke

Game Design | COO

Physical playfields on which Peters develops rules and software

Spooky DJ

Hardware / Software Engineering

Scooby-Doo | Beetlejuice | Spooky software development

David Fawcett

Software

Halloween | Ultraman

Eric Priepke

Software

Looney Tunes

Benjamin Heckendorn

Software | Rules

The Texas Chain Saw Massacre | Evil Dead

Hilton Jones

Story | Rules

The Texas Chain Saw Massacre | Evil Dead

Casey Butler

Software

Beetlejuice

Duane Foust

Engineering

Scooby-Doo | Looney Tunes and related platform

Matt “Count D” Montgomery

Music / Sound

Multiple Spooky productions

Key Dates and Contributions

Year

Milestone

Significance

2021

Halloween

First identified commercial credits in rules development for Spooky’s new generation.

2021

Ultraman: Kaiju Rumble!

Contributes to rules and software development on the parallel platform.

2022

Scooby-Doo, Where Are You!

Takes on a clearly identifiable role in rules architecture.

2023

Looney Tunes

Story / Rules, with Eric Priepke as primary software developer.

2023

The Texas Chain Saw Massacre

Participates in collaborative rules/story development.

2024

Evil Dead

Works on rules with Ben Heck, Bug Emery and Hilton Jones.

2025

Evil Dead Updates

The ruleset receives major modes, wizard modes, balancing changes and fixes.

2025

Beetlejuice

Part of the software team with Spooky DJ and Casey Butler.

2026

Spooky Pinball

Director of Rules and Code Development.

2026

Evil Dead

Development continues with new systems, Hail to the King and stability corrections.

Luke Peters | The Invisible Architecture of Spooky Machines

Luke Peters provides a useful way to understand another part of Spooky Pinball’s evolution. His name first appears around rules and software on the Halloween / Ultraman generation before becoming far more clearly defined on Scooby-Doo and Looney Tunes. The latter remains especially representative: Peters receives story/rules design while Eric Priepke programs the machine, making his contribution visible through the organization of Episodes, ACME Items, Roadrunner, different multiballs and the progression toward advanced modes.

The Texas Chain Saw Massacre and Evil Dead then show his ability to work inside collaborative architectures. Responsibilities are shared with Bug Emery, Hilton Jones and Ben Heck, while the physical terrain remains designed by Bug Emery and Lukas Kastner. That separation prevents Peters from being treated as a sole author, but it also reflects the reality of his profession: modern rules design is rarely built in isolation. License material, mechanisms, scoring, programming constraints and player feedback all have to converge.

His move into the role of Director of Rules and Code Development gives that experience a broader dimension. Beetlejuice brings several developers together around a software architecture where new interactions, mechanisms, audiovisual content and progression all have to remain coherent. Peters is now less a contributor appearing in one credit column than the person responsible for a domain that has become decisive for Spooky.

By 2026, his main challenge is also the manufacturer’s: preserving the ambition of its rulesets while improving readability, stability and launch completeness. The depth of Scooby-Doo, Looney Tunes and Evil Dead demonstrates what the team can build. The long software maturation of several of those games demonstrates what still needs tighter control. Luke Peters sits directly at the center of that equation, between the rule as imagined, the code capable of executing it and the machine the player actually experiences after pressing Start.

Highlights

  • Rules
  • Software Development
  • Code Development
  • Rules and Code Direction

Key dates

  1. First clearly documented Spooky credits involving the rules for Halloween and Ultraman: Kaiju Rumble!.

  2. Becomes a clearly identified contributor to Scooby-Doo, with a rules credit and software involvement alongside Spooky DJ.

  3. Works on Looney Tunes, again in rules and software.

  4. Contributes to the rules for Evil Dead as part of a team that also includes Ben Heck, Bug Emery, and Hilton Jones.

  5. Appears on the Beetlejuice software team alongside Casey Butler and Spooky DJ.

  6. Officially identified by Spooky Pinball as Director of Rules and Code Development.

Associated machines

5 machines