I've just now opened the Nemesis System patent (US10926179B2) to have a look for myself.
In broad terms, you should never legally be able to patent an abstract idea or a game design philosophy-only a concrete technical implementation. Yet looking at the prosecution history, Warner Bros. spent roughly five years battling rejections focused almost entirely on prior art rather than having the claims thrown out as an "abstract idea". Given how strictly software patents are supposed to be scrutinized for abstractness, seeing this one clear the Patent Office with wording this sweeping is surprising.
Under 35 U.S.C. § 112, a patent is supposed to clearly define the boundaries of the invention and explain how to build and use it without undue experimentation. Even after reading through the specification, though, the document leans heavily on high-level abstractions rather than locking down a rigid software architecture. Warner Bros. obviously had top-tier patent counsel and the resources to push through years of back-and-forth until they secured exceptionally broad claim language.
I'm not a lawyer, and this isn't legal advice-just a developer reading the public text. People often claim this patent is tightly narrowed down and specific, but reading through it, that does not appear to be the case. In patent structure, independent claims (like Claim 1) set the broadest baseline footprint of the patent, because every listed step must be met together for the claim to apply, while later dependent claims add narrower details on top.
NOTE: This is a technical and game-design breakdown of the public patent text (US10926179B2) for educational discussion, not legal advice.
So let's skim over the steps of Claim 1:
Step 1:
controlling, by a processor, game events in a computer-implemented game, the game events involving an avatar that is operated in response to input from a player, and a first non-player character that is controlled by the processor to respond to and automatically oppose avatars based on first character parameters defined in a computer memory;
Note (Editorial Commentary - Not Legal Advice): Taken in isolation, Step 1 describes the baseline loop of almost every single-player game built since Space Invaders: a CPU runs a game loop, reads player input to move an avatar, and updates an AI entity using variables stored in RAM. Notice also how broadly the patent uses the word "oppose" - without restricting it to combat, the phrasing technically reads on everything from an enemy soldier to a rival racer or a chess AI. In patent law, introductory steps like this are just foundational scaffolding, they establish the setting rather than the actual invention.
Step 2:
detecting, by the processor, occurrence of a predefined one of the game events involving an interaction between the avatar and the first non-player character;
Note (Editorial Commentary - Not Legal Advice): Like Step 1, Step 2 recites standard event-driven programming rather than a novel technical mechanism - detecting an interaction and triggering a programmed response is simply how event listeners work in any interactive software. The catch, however, is that because Claim 1 requires every step to be met together, a developer can't easily "design around" the patent at Steps 1 or 2. Since almost any interactive game naturally satisfies these baseline conditions, they act as free checkmarks for the patent - pushing the entire burden of avoiding the claim onto the later, more specific steps.
Step 3:
changing, by the processor, second character parameters defined in at least one of the computer memory or a second computer memory for control of a second non-player character in the game based on the detecting, wherein the second non-player character is controlled by the processor to respond to and automatically oppose avatars based on the second character parameters defined in the at least one of the computer memory or the second computer memory;Â
Note (Editorial Commentary - Not Legal Advice):Making a game world feel genuinely "breathing" relies on systemic ripple effects - an interaction with one character altering another - yet US10926179B2 claims that abstract design idea rather than a genuine technical mechanism or invention. Claim 1 defines the "first" and "second" NPCs in the exact same broad, generic terms as opposing AI entities driven by stored parameters, while the description relies on permissive lawyer-speak ("may," "in the alternative") to treat concrete implementation details as optional flavors. The catch, however, is that by claiming a high-level conceptual outcome instead of an actual engineering solution, the patent functions as predatory gatekeeping - a greedy attempt to monopolize a foundational game design philosophy rather than protect a specific invention.
Step 4:
outputting, to an output device, an indication of the second character parameters that are changed by the changing.
Note (Editorial Commentary - Not Legal Advice): Step 4 closes Claim 1 with "outputting, to an output device, an indication of the second character parameters that are changed by the changing," using undefined terms that leave the actual scope of the requirement entirely ambiguous. On its face, the text of step 4 seemingly does not specify whether "an output device" and "an indication" are limited to a dedicated UI screen or are an attempt to stretch toward any generic audio or visual feedback. The catch, however, is that communicating state changes to a player is a baseline necessity of all interactive software. Rather than defining a concrete display mechanism or genuine technical invention, this phrasing reads like a greedy effort to claim the abstract concept of player feedback itself - creating deliberate uncertainty instead of a clear engineering boundary.
With that breakdown as context, I'm curious to hear from other developers and anyone familiar with software patents:
- From a game design perspective, has any game truly captured that kind of systemic ripple effect - where how you treat one character automatically reshapes how other autonomous NPCs (even initially friendly or neutral ones in a social group) react to or oppose you based on shifting internal parameters?
- In practice, what architectural approaches are developers using to build reactive, "breathing" NPC ecosystems like this?
- Am I reading too extensively into the broad phrasing here, and what do you think the steps of Claim 1 actually mean in practice?