IP Library › Granted Patent US 12,472,436
Granted Patent B2
US 12,472,436 · App. 17/889,677 · Granted Nov 18, 2025

Game definition file

Inventors: Luke Dicken (San Francisco, CA); Johnathan Pagnutti (San Francisco, CA); Yang Wen (San Francisco, CA)
Assignee: Zynga Inc.
A63F13/69A63F13/45A63F13/77A63F13/79G06F9/44505
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,472,436
App. No.
17/889,677
Granted
Nov 18, 2025
Kind
B2
Abstract

A client device receives compiled software for a game engine. The game engine is for playing a designated game. The client device receives a game definition file for the designated game. The game definition file stores rules for the designated game. The game definition file defines the rules using non-compiled machine-readable code. The client device executes the game engine at the client device to enable playing of the designated game via the client device. Executing the game engine includes: accessing the game definition file; and providing, via a user interface generated on the client device, interactive gameplay of the designated game according to the rules for the designated game defined by the game definition file.

Claims (43)

1 . A method implemented at a client device, the method comprising:

accessing compiled software for a game engine, the game engine being for playing a plurality of games via the client device;

receiving and storing at the client device a plurality of game definition files comprising respective game definition file for each of the plurality of games, each game definition file comprising a respective ruleset that defines game mechanics specific to a corresponding one of the plurality games, wherein each game definition file defines the respective ruleset using non-compiled machine-readable code; and

executing the game engine at the client device to enable playing, at different instances of execution, each of the plurality of games via the client device by use of the game engine, wherein executing the game engine in each instance comprises:

accessing the respective game definition file of a user-selected one of the plurality of games; and

providing, via a user interface generated on the client device, interactive gameplay of the selected game according to the game mechanics specific to the selected game as defined by corresponding game definition file, the game engine thus implementing different game mechanics for different respective games using in common the compiled game engine software in unmodified form between the respective instances of execution.

2 . The method of claim 1 , wherein each game definition file comprises one or more blocks of text data that provides a respective textually-defined ruleset specifying gameplay mechanics for the corresponding game.

3 . The method of claim 2 , wherein the one or more blocks of text data is structured in a predefined format that the game engine is complementarily configured to identify and implement.

4 . The method of claim 1 , further comprising:

receiving an updated game definition file for a particular on of the plurality games; and

executing the game engine at the client device to play the particular game, wherein executing the game engine comprises:

accessing the updated game definition file for the particular game; and

providing, via the user interface generated on the client device, interactive gameplay of the particular game according to game mechanics defined by an updated ruleset specified by the updated game definition file for the particular game.

5 . The method of claim 4 , wherein the updated game definition file is received without receiving an updated game engine and without updating the game engine.

6 . The method of claim 1 , wherein each game definition file represents a different respective formal first order predicate logic for playing the corresponding one of the plurality of games via the game engine.

7 . The method of claim 1 , wherein the interactive gameplay of each game comprises providing, via the user interface, a graphical output and receiving, via the user interface at the client device, a user input for taking a user action in the respective game.

8 . The method of claim 1 , wherein the ruleset of each game definition file comprises at least one rule that defines a logical manipulation of a game state in response to a user action or a current game state in the corresponding game.

9 . The method of claim 8 , wherein the logical manipulation of the game state determines character movement behavior specific to the corresponding game.

10 . The method of claim 8 , wherein the logical manipulation of the game state determines movement behavior of one or more content items specific to the corresponding game.

11 . The method of claim 8 , wherein the logical manipulation of the game state determines how points are assigned in the corresponding game.

12 . The method of claim 1 , wherein:

the compiled software for the game play engine is received, at the client device, from an application store server; and

the plurality of game definition files are received, at the client device, from a game server.

13 . A client device comprising:

processing circuitry; and

a memory storing instructions which, when executed by the processing circuitry, cause the processing circuitry to perform operations comprising:

accessing compiled software for a game engine, the game engine being for playing a plurality of games via the client device;

receiving and storing at the client device a plurality of game definition files comprising respective game definition file for each of the plurality of games, each game definition file comprising a respective ruleset that defines game mechanics specific to a corresponding one of the plurality games, wherein each game definition file defines the respective ruleset using non-compiled machine-readable code; and

executing the game engine at the client device to enable playing, at different instances of execution, each of the plurality of games via the client device by use of the game engine, wherein executing the game engine in each instance comprises:

accessing the respective game definition file of a user-selected one of the plurality of games; and

providing, via a user interface generated on the client device, interactive gameplay of the selected game according to the game mechanics specific to the selected game as defined by corresponding game definition file, the game engine thus implementing different game mechanics for different respective games using in common the compiled game engine software in unmodified form between the respective instances of execution.

14 . The client device of claim 13 , wherein each game definition file comprises one or more blocks of text data that provides a respective textually-defined ruleset specifying gameplay mechanics for the corresponding game.

15 . The client device of claim 14 , wherein the one or more blocks of text data is structured in a predefined format that the game engine is complementarily configured to identify and implement.

16 . The client device of claim 13 , wherein each game definition file represents a different respective formal first order predicate logic for playing the corresponding one of the plurality of games via the game engine.

17 . The client device of claim 13 , wherein the ruleset of each game definition file comprises at least one rule that defines a logical manipulation of a game state in response to a user action or a current game state in the corresponding game.

18 . The client device of claim 17 , wherein the logical manipulation of the game state determines movement behavior of one or more content items specific to the corresponding game.

19 . The client device of claim 17 , wherein the logical manipulation of the game state determines how points are assigned in the corresponding game.

20 . A non-transitory machine-readable medium having stored thereon instructions for causing a client device, when executing the instructions, to perform operations comprising:

accessing compiled software for a game engine, the game engine being for playing a plurality of games via the client device;

receiving and storing at the client device a plurality of game definition files comprising respective game definition file for each of the plurality of games, each game definition file comprising a respective ruleset that defines game mechanics specific to a corresponding one of the plurality games, wherein each game definition file defines the respective ruleset using non-compiled machine-readable code; and

executing the game engine at the client device to enable playing, at different instances of execution, each of the plurality of games via the client device by use of the game engine, wherein executing the game engine in each instance comprises:

accessing the respective game definition file of a user-selected one of the plurality of games; and

providing, via a user interface generated on the client device, interactive gameplay of the selected game according to the game mechanics specific to the selected game as defined by corresponding game definition file, the game engine thus implementing different game mechanics for different respective games using in common the compiled game engine software in unmodified form between the respective instances of execution.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 16, 2022
From: DICKEN, LUKE; PAGNUTTI, JOHNATHAN; WEN, YANG
To: ZYNGA INC.
Reel/Frame 061795/0636 →
Continuity (2)
Continuation 17027483 · Sep 21, 2020
Related Publication 20230076907A1 · Mar 9, 2023
References Cited (181)
US 6099408A · Schneier et al. · 2000 [cited by applicant]
US 9044675B2 · Stafford et al. · 2015 [cited by applicant]
US 9498704B1 · Cohen et al. · 2016 [cited by applicant]
US 10105603B2 · Bucher et al. · 2018 [cited by applicant]
US 10105608B1 · George et al. · 2018 [cited by applicant]
US 10237615B1 · Gudmundsson et al. · 2019 [cited by applicant]
US 10293260B1 · Evans et al. · 2019 [cited by applicant]
US 10387514B1 · Yang et al. · 2019 [cited by applicant]
US 10556182B2 · Ntoulas et al. · 2020 [cited by applicant]
US 10946281B2 · Fear et al. · 2021 [cited by applicant]
US 11291915B1 · Dicken et al. · 2022 [cited by applicant]
US 11318386B2 · Dicken et al. · 2022 [cited by applicant]
US 11344808B2 · Estanislao · 2022 [cited by applicant]
US 11420115B2 · Dicken et al. · 2022 [cited by applicant]
US 11465052B2 · Dicken et al. · 2022 [cited by applicant]
US 11565182B2 · Dicken et al. · 2023 [cited by applicant]
US 11642594B2 · Dicken et al. · 2023 [cited by applicant]
US 11673049B2 · Dicken et al. · 2023 [cited by applicant]
US 11724193B2 · Dicken et al. · 2023 [cited by applicant]
US 11738272B2 · Dicken et al. · 2023 [cited by applicant]
US 11806624B2 · Dicken et al. · 2023 [cited by applicant]
US 11957982B2 · Dicken et al. · 2024 [cited by applicant]
US 12083436B2 · Dicken et al. · 2024 [cited by applicant]
US 12109488B2 · Dicken et al. · 2024 [cited by applicant]
US 12145069B2 · Dicken et al. · 2024 [cited by applicant]
US 12214281B2 · Dicken et al. · 2025 [cited by applicant]
US 20020178212A1 · Sirhall · 2002 [cited by applicant]
US 20050071306A1 · Kruszewski et al. · 2005 [cited by applicant]
US 20060246973A1 · Thomas et al. · 2006 [cited by applicant]
US 20070054717A1 · Youm et al. · 2007 [cited by applicant]
US 20070066403A1 · Conkwright · 2007 [cited by applicant]
US 20080096668A1 · Yoshioka · 2008 [cited by applicant]
US 20080162268A1 · Gilbert · 2008 [cited by applicant]
US 20110300847A1 · Quy · 2011 [cited by applicant]
US 20120109956A1 · Ramaiyer et al. · 2012 [cited by applicant]
US 20120123570A1 · Guinn · 2012 [cited by applicant]
US 20120317064A1 · Hagiwara et al. · 2012 [cited by applicant]
US 20130184070A1 · Gadher et al. · 2013 [cited by applicant]
US 20130310156A1 · Gadher et al. · 2013 [cited by applicant]
US 20130324209A1 · Kishimoto et al. · 2013 [cited by applicant]
US 20140089399A1 · Chun et al. · 2014 [cited by applicant]
US 20140324749A1 · Peters et al. · 2014 [cited by applicant]
US 20150174493A1 · Stauffer et al. · 2015 [cited by applicant]
US 20150230756A1 · Luna et al. · 2015 [cited by applicant]
US 20150273340A1 · Cudak et al. · 2015 [cited by applicant]
US 20160067611A1 · Ware et al. · 2016 [cited by applicant]
US 20160067612A1 · Ntoulas et al. · 2016 [cited by applicant]
US 20160256784A1 · Schultz et al. · 2016 [cited by applicant]
US 20170100674A1 · Ntoulas et al. · 2017 [cited by applicant]
US 20170169656A1 · Froy, Jr. · 2017 [cited by applicant]
US 20180001205A1 · Osman et al. · 2018 [cited by applicant]
US 20180361253A1 · Grosso · 2018 [cited by applicant]
US 20190091576A1 · Taylor et al. · 2019 [cited by applicant]
US 20190171957A1 · Yang et al. · 2019 [cited by applicant]
US 20190388787A1 · Padmanabhan et al. · 2019 [cited by applicant]
US 20200167475A1 · Liu et al. · 2020 [cited by applicant]
US 20200168045A1 · Idris · 2020 [cited by applicant]
US 20200206631A1 · Sumant et al. · 2020 [cited by applicant]
US 20200250555A1 · Kwon et al. · 2020 [cited by applicant]
US 20200298118A1 · Yannakakis et al. · 2020 [cited by applicant]
US 20210001229A1 · Somers et al. · 2021 [cited by applicant]
US 20210027182A1 · Harris et al. · 2021 [cited by applicant]
US 20210146258A1 · Pedersen et al. · 2021 [cited by applicant]
US 20220088474A1 · Dicken · 2022 [cited by examiner]
US 20220088478A1 · Dicken · 2022 [cited by examiner]
US 20220088481A1 · Dicken · 2022 [cited by examiner]
US 20220088482A1 · Dicken · 2022 [cited by examiner]
US 20220088483A1 · Dicken · 2022 [cited by examiner]
US 20220088484A1 · Dicken · 2022 [cited by examiner]
US 20220088485A1 · Dicken · 2022 [cited by examiner]
US 20220088486A1 · Dicken · 2022 [cited by examiner]
US 20220176252A1 · Dicken et al. · 2022 [cited by applicant]
US 20220226730A1 · Dicken et al. · 2022 [cited by applicant]
US 20220249950A1 · Dicken et al. · 2022 [cited by applicant]
US 20230054150A1 · Dicken et al. · 2023 [cited by applicant]
US 20230070555A1 · Dicken et al. · 2023 [cited by applicant]
US 20230347245A1 · Dicken et al. · 2023 [cited by applicant]
US 20230356088A1 · Dicken et al. · 2023 [cited by applicant]
US 20230405467A1 · Dicken et al. · 2023 [cited by applicant]
US 20240050859A1 · Dicken et al. · 2024 [cited by applicant]
CA 2488432 · 2014 [cited by applicant]
“U.S. Appl. No. 17/875,659, Non Final Office Action mailed Feb. 22, 2024”, 8 pgs. [cited by applicant]
“U.S. Appl. No. 17/985,637, Corrected Notice of Allowability mailed Mar. 1, 2024”, 2 pgs. [cited by applicant]
“U.S. Appl. No. 18/141,642, Response filed Mar. 6, 2024 to Non Final Office Action mailed Dec. 6, 2023”, 10 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,503, Response filed Mar. 11, 2024 to Non Final Office Action mailed Oct. 11, 2023”, 15 pgs. [cited by applicant]
“U.S. Appl. No. 17/985,637, Corrected Notice of Allowability mailed Mar. 14, 2024”, 2 pgs. [cited by applicant]
“U.S. Appl. No. 17/875,659, Examiner Interview Summary mailed Mar. 29, 2024”, 2 pgs. [cited by applicant]
“U.S. Appl. No. 17/875,659, Response filed Apr. 9, 2024 to Non Final Office Action mailed Feb. 22, 2024”, 13 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,503, Notice of Allowance mailed Apr. 17, 2024”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 18/210,949, Non Final Office Action mailed May 29, 2024”, 7 pgs. [cited by applicant]
“U.S. Appl. No. 17/875,659, Notice of Allowance mailed May 31, 2024”, 5 pgs. [cited by applicant]
“U.S. Appl. No. 18/210,949, Response filed Jun. 21, 2024 to Non Final Office Action mailed May 29, 2024”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 18/141,642, Non Final Office Action mailed Jul. 1, 2024”, 8 pgs. [cited by applicant]
“U.S. Appl. No. 18/217,708, Non Final Office Action mailed Jul. 12, 2024”, 6 pgs. [cited by applicant]
“U.S. Appl. No. 18/210,949, Notice of Allowance mailed Jul. 15, 2024”, 7 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,503, 312 Amendment filed Jul. 17, 2024”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 17/680,565, Non Final Office Action mailed Jan. 11, 2023”, 6 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,497, Response filed Jan. 30, 2023 to Non Final Office Action mailed Oct. 6, 2022”, 12 pgs. [cited by applicant]
“U.S. Appl. No. 17/730,925, Notice of Allowance mailed Feb. 1, 2023”, 7 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,503, Non Final Office Action mailed Feb. 6, 2023”, 10 pgs. [cited by applicant]
“U.S. Appl. No. 17/680,565, Response filed Feb. 27, 2023 to Non Final Office Action mailed Jan. 11, 2023”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,502, Notice of Allowability mailed Jun. 7, 2023”, 5 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,497, Notice of Allowability mailed Jul. 10, 2023”, 4 pgs. [cited by applicant]
“U.S. Appl. No. 18/141,642, Preliminary Amendment filed Jul. 17, 2023”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 17/985,637, Non Final Office Action mailed Mar. 16, 2023”, 23 pgs. [cited by applicant]
“U.S. Appl. No. 17/985,637, Response filed Aug. 16, 2023 to Non Final Office Action mailed Mar. 16, 2023”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 18/222,151, Preliminary Amendment filed Aug. 21, 2023”, 7 pgs. [cited by applicant]
“U.S. Appl. No. 18/210,949, Preliminary Amendment filed Sep. 7, 2023”, 10 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,503, Response filed Sep. 26, 2023 to Final Office Action mailed Apr. 26, 2023”, 12 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,503, Non Final Office Action mailed Oct. 11, 2023”, 14 pgs. [cited by applicant]
“U.S. Appl. No. 18/217,708, Preliminary Amendment filed Nov. 2, 2023”, 8 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,503, Examiner Interview Summary mailed Nov. 17, 2023”, 3 pgs. [cited by applicant]
“U.S. Appl. No. 17/985,637, Notice of Allowance mailed Nov. 22, 2023”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 18/141,642, Non Final Office Action mailed Dec. 6, 2023”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,502, Response filed Dec. 2, 2022 to Non-Final Office Action mailed Sep. 2, 2022”, 10 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,502, Final Office Action mailed Dec. 23, 2022”, 10 pgs. [cited by applicant]
“U.S. Appl. No. 17/713,862, Notice of Allowance mailed Dec. 28, 2022”, 7 pgs. [cited by applicant]
U.S. Appl. No. 18/582,925, filed Feb. 21, 2024, Parametric Player Modeling for Computer-Implemented Games. [cited by applicant]
U.S. Appl. No. 17/027,483 U.S. Pat. No. 11,465,052, filed Sep. 21, 2020, Game Definition File. [cited by applicant]
U.S. Appl. No. 18/141,642, filed May 1, 2023, Operator Interface for Automated Game Content Generation. [cited by applicant]
“U.S. Appl. No. 16/948,503, Response filed Feb. 28, 2023 to Non Final Office Action mailed Feb. 6, 2023”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 17/680,565, Notice of Allowance mailed Mar. 16, 2023”, 7 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,502, Response filed Mar. 31, 2023 to Final Office Action mailed Dec. 23, 2022”, 10 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,497, Notice of Allowance mailed Apr. 3, 2023”, 7 pgs. [cited by applicant]
“U.S. Appl. No. 17/985,637, Examiner Interview Summary mailed Apr. 6, 2023”, 3 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,502, Notice of Allowance mailed Apr. 18, 2023”, 7 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,503, Final Office Action mailed Apr. 26, 2023”, 12 pgs. [cited by applicant]
“U.S. Appl. No. 17/730,925, Notice of Allowability mailed May 2, 2023”, 4 pgs. [cited by applicant]
“U.S. Appl. No. 17/680,565, Supplemental Notice of Allowability mailed May 24, 2023”, 2 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,496, 312 Amendment filed Feb. 23, 2022”, 8 pages. [cited by applicant]
“U.S. Appl. No. 16/948,496, Non Final Office Action mailed Aug. 16, 2021”, 6 pages. [cited by applicant]
“U.S. Appl. No. 16/948,496, Notice of Allowance mailed Nov. 23, 2021”, 7 pages. [cited by applicant]
“U.S. Appl. No. 16/948,496, Response filed Nov. 8, 2021 to Non Final Office Action mailed Aug. 16, 2021”, 10 pages. [cited by applicant]
“U.S. Appl. No. 16/948,496, Supplemental Notice of Allowability mailed Mar. 3, 2022”, 2 pages. [cited by applicant]
“U.S. Appl. No. 16/948,497, Final Office Action mailed May 12, 2022”, 8 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,497, Non Final Office Action mailed Aug. 26, 2021”, 6 pages. [cited by applicant]
“U.S. Appl. No. 16/948,497, Non Final Office Action mailed Oct. 6, 2022”, 7 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,497, Response filed Jan. 26, 2022 to Non Final Office Action mailed Aug. 26, 2021”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,497, Response filed Sep. 12, 2022 to Final Office Action mailed May 12, 2022”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,502, Final Office Action mailed May 12, 2022”, 8 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,502, Non Final Office Action mailed Sep. 2, 2022”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,502, Non Final Office Action mailed Oct. 6, 2021”, 6 pages. [cited by applicant]
“U.S. Appl. No. 16/948,502, Response filed Feb. 7, 2022 to Non Final Office Action mailed Oct. 6, 2021”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,502, Response filed Aug. 12, 2022 to Final Office Action mailed May 12, 2022”, 10 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,503, Final Office Action mailed Feb. 24, 2022”. [cited by applicant]
“U.S. Appl. No. 16/948,503, Final Office Action mailed Jul. 15, 2022”, 10 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,503, Non Final Office Action mailed Aug. 16, 2021”, 8 pages. [cited by applicant]
“U.S. Appl. No. 16/948,503, Response filed Jun. 24, 2022 to Final Office Action mailed Feb. 24, 2022”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,503, Response filed Nov. 15, 2022 to Final Office Action mailed Jul. 15, 2022”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,503, Response filed Dec. 16, 2021 to Non Final Office Action mailed Aug. 16, 2021”, 10 pgs. [cited by applicant]
“U.S. Appl. No. 17/027,448, Corrected Notice of Allowability mailed Jul. 22, 2022”, 2 pgs. [cited by applicant]
“U.S. Appl. No. 17/027,448, Non Final Office Action mailed Sep. 10, 2021”, 6 pages. [cited by applicant]
“U.S. Appl. No. 17/027,448, Notice of Allowance mailed Apr. 14, 2022”, 5 pgs. [cited by applicant]
“U.S. Appl. No. 17/027,448, Response filed Feb. 10, 2022 to Non Final Office Action mailed Sep. 10, 2021”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 17/027,477, Corrected Notice of Allowability mailed Oct. 13, 2022”, 2 pgs. [cited by applicant]
“U.S. Appl. No. 17/027,477, Non Final Office Action mailed Jan. 21, 2022”, 15 pages. [cited by applicant]
“U.S. Appl. No. 17/027,477, Notice of Allowance mailed Sep. 23, 2022”, 8 pgs. [cited by applicant]
“U.S. Appl. No. 17/027,477, Response filed Jun. 21, 2022 to Non Final Office Action mailed Jan. 21, 2022”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 17/027,483, Final Office Action mailed Apr. 14, 2022”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 17/027,483, Non Final Office Action mailed Dec. 21, 2021”, 13 pages. [cited by applicant]
“U.S. Appl. No. 17/027,483, Notice of Allowance mailed May 13, 2022”, 8 pgs. [cited by applicant]
“U.S. Appl. No. 17/027,483, Response filed Mar. 21, 2022 to Non Final Office Action mailed Dec. 21, 2021”, 10 pgs. [cited by applicant]
“U.S. Appl. No. 17/027,483, Response filed Apr. 28, 2022 to Final Office Action mailed Apr. 14, 2022”, 8 pgs. [cited by applicant]
“U.S. Appl. No. 17/027,502, Notice of Allowability mailed Apr. 8, 2022”, 2 pgs. [cited by applicant]
“U.S. Appl. No. 17/027,502, Notice of Allowance mailed Dec. 29, 2021”, 7 pages. [cited by applicant]
“U.S. Appl. No. 17/713,862, Preliminary Amendment filed Apr. 8, 2022”, 10 pgs. [cited by applicant]
“U.S. Appl. No. 17/875,659, Preliminary Amendment filed Nov. 8, 2022”. [cited by applicant]
U.S. Appl. No. 18/222,151, filed Jul. 14, 2023, on Device Game Engine Architecture. [cited by applicant]
U.S. Appl. No. 18/210,949, filed Jun. 16, 2023, Automated Prediction of User Response States Based on Traversal Behavior. [cited by applicant]
U.S. Appl. No. 18/217,708, filed Jul. 3, 2023, Automated Generation of Custom Content for Computer-Implemented Games. [cited by applicant]
“U.S. Appl. No. 18/210,949, Supplemental Notice of Allowability mailed Aug. 5, 2024”, 2 pgs. [cited by applicant]
“U.S. Appl. No. 16/948,503, Corrected Notice of Allowability mailed Aug. 9, 2024”, 2 pgs. [cited by applicant]
“U.S. Appl. No. 17/875,659, 312 Amendment filed Aug. 28, 2024”, 8 pgs. [cited by applicant]
“U.S. Appl. No. 18/217,708, Response filed Sep. 4, 2024 to Non Final Office Action mailed Jul. 12, 2024”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 18/141,642, Response filed Sep. 4, 2024 to Non Final Office Action mailed Jul. 1, 2024”, 12 pgs. [cited by applicant]
“U.S. Appl. No. 17/875,659, PTO Response to Rule 312 Communication mailed Sep. 6, 2024”, 2 pgs. [cited by applicant]
“U.S. Appl. No. 18/141,642, Notice of Allowance mailed Sep. 16, 2024”, 7 pgs. [cited by applicant]
“U.S. Appl. No. 18/217,708, Notice of Allowance mailed Dec. 6, 2024”, 7 pgs. [cited by applicant]
“U.S. Appl. No. 18/141,642, 312 Amendment filed Dec. 16, 2024”, 8 pgs. [cited by applicant]
“U.S. Appl. No. 18/222,151, Non Final Office Action mailed Dec. 19, 2024”, 6 pgs. [cited by applicant]
“U.S. Appl. No. 18/141,642, PTO Response to Rule 312 Communication mailed Dec. 27, 2024”, 2 pgs. [cited by applicant]