Game development architecture that decouples the game logic from the graphics logic

• US 8,251,807 B2
• Filed: 11/01/2007
• Issued: 08/28/2012
• Est. Priority Date: 09/28/2001
• Status: Expired due to Fees

• Current Assignee: IGT (International Game Technology)
• Original Assignee: IGT (International Game Technology)
• Inventors: LeMay, Steven G., Nelson, Dwayne R., Breckner, Robert E., Schlottmann, Greg A., Beaulieu, Nicole M., Palchetti, Johnny, Benbrahim, Jamal
• Primary Examiner(s): DEODHAR, OMKAR A
• Application Number:
  US11/933,918
• Publication Number:
  US 20080096656A1
• Time in Patent Office: 1,762 Days
• Field of Search: 463/29
• US Class Current: 463/29
• CPC Class Codes: A63F 13/12 involving interaction between a plurality of game devices, e.g. transmisison or distribution systems protocols for networked virtual reality, networked games H04L29/06034
• CPC Class Codes: A63F 13/30 Interconnection arrangements between game servers and game devices; Interconnection arrangements between game devices; Interconnection arrangements between game servers
• CPC Class Codes: A63F 2300/552 for downloading to client devices, e.g. using OS version, hardware or software profile of the client device
• CPC Class Codes: G07F 17/32 for games, toys, sports, or amusements

Abstract

A disclosed gaming machine is designed to execute a modular gaming software architecture. A plurality of gaming software modules may be loaded into RAM on the gaming machine and executed to play a game of chance. Many of the gaming software modules are designed to communicate via application program interfaces so that the logic in many of the gaming software modules may be designed independently of each other. In particular, the modular gaming software architecture allows a game flow software module used to generate a game of chance on the gaming machine to be decoupled from a game presentation software module used to present the game chance. Thus, a group of games may be designed where the games share a common game flow software module but use different game presentation software modules to change the look and feel of the game.

Claims

1. A method comprising:

by a game flow software module that includes game flow logic and a state machine, the game flow software module being executed or executing from one or more random-access memory (RAM) locations within a gaming machine;

receiving a request to start a game flow for the play of a game of chance, the game flow including rules for playing the game of chance;

generating a plurality of game states in the game flow, the plurality of game states being used or usable to play the game of chance according to the rules; and

communicating game state information for one or more of the game states to one or more other gaming software modules via one or more application program interfaces,

wherein the game flow logic and the state machine for generating the game states is separate from logic for the one or more other gaming software modules, the logic for the one or more other gaming software modules including core logic for core gaming machine-wide functionality, the logic for the one or more other gaming software modules not including game flow logic for generating the game states.

2. The method of claim 1, further comprising:

loading the game flow software module into the one or more RAM locations.

3. The method of claim 1, further comprising:

generating a game outcome for the game of chance based on the game state information; and

communicating the game outcome to one or more of the other gaming software modules via one or more of the application program interfaces.

4. The method of claim 1, further comprising:

receiving a command to end the game of chance; and

entering an idle state based on the command.

5. The method of claim 1, further comprising:

receiving a command to process an award for the game of chance; and

processing an award based on the command.

6. The method of claim 1, wherein:

the one or more other gaming software modules include a game presentation software module;

communicating game state information for one or more of the game states to one or more other gaming software modules via one or more application program interfaces comprises communicating game state information for one or more of the game states to the game presentation software module;

the game flow logic and the state machine for generating the game states is separate from game presentation logic for the game presentation software module; and

the method further comprises generating, by the game presentation software module, a game presentation for the game of chance based on the game state information communicated by the game flow software module, the game presentation being suitable for display on a display screen of the gaming machine.

7. The method of claim 1, wherein:

the one or more other gaming software modules include a gaming operating system software module operable to;

load and unload other ones of the other gaming software modules into the one or more RAM locations from a memory device; and

control the play of the game of chance; and

the game flow logic and the state machine for generating the game states is separate from game operating system logic for the gaming operating system software module.

8. The method of claim 1, wherein one or more of the one or more application program interfaces are each selected from the group consisting of:

a game flow interface, a bank interface, and a configuration interface.

9. The method of claim 1, further comprising:

storing critical game data for the game of chance in one or more non-volatile memory devices or locations separate from the game flow logic.

10. The method of claim 1, wherein at least one of the one or more other gaming software modules is located on or within a remote gaming device at a location remote from the gaming machine.

11. A method comprising:

by a game presentation software module that includes game presentation logic, the game presentation software module being executed or executing from one or more random-access memory (RAM) locations within a gaming machine;

receiving a request to start a game presentation for the play of a game of chance;

receiving game state information for one or more game states of the game of chance;

generating graphics and audio information based on the game state information;

displaying, or causing to be displayed, graphics and sounds for one or more of the game states based on the graphics and audio information on a display screen of the gaming machine and on audio output devices of the gaming machine;

communicating presentation state information for the game presentation with one or more other gaming software modules via one or more application program interfaces,

wherein the game presentation logic for generating the graphics and audio information is separate from logic for the one or more other gaming software modules, the logic for the one or more other gaming software modules including core logic for core gaming machine-wide functionality, the logic for the one or more other gaming software modules not including game presentation logic for generating graphics and audio information.

12. The method of claim 11, further comprising:

reading critical game information for the game of chance from a non-volatile storage device.

13. The method of claim 11, further comprising:

updating metering displays for the game of chance on the gaming machine.

14. The method of claim 11, further comprising:

synchronizing the display of graphics with the output of sounds on the gaming machine.

15. The method of claim 11, further comprising:

communicating a message to one or more of the other gaming software modules that acknowledges the completion of the game presentation for one or more of the game states.

16. The method of claim 11, wherein:

the one or more other gaming software modules include a gaming operating system software module operable to;

load and unload other ones of the other gaming software modules into the one or more RAM locations from a memory device; and

control the play of the game of chance; and

the game flow logic and the state machine for generating the game states is separate from game operating system logic for the gaming operating system software module.

17. The method of claim 11, wherein:

the one or more other gaming software modules include a game flow software module;

the method further comprises generating, by the game flow software module, a game flow for the game of chance;

communicating presentation state information for the game presentation with one or more other gaming software modules via one or more application program interfaces comprises receiving game state information from the game flow software module; and

the game presentation logic for generating graphics and audio information is separate from game flow logic for the game flow software module.

18. The method of claim 11, wherein:

at least one of the one or more other gaming software modules is located on or within a remote gaming device at a location remote from the gaming machine.

19. The method of claim 18, wherein the one or more other gaming software modules include a gaming operating system software module located on the remote gaming device and operable to:

load and unload other ones of the other gaming software modules into the one or more RAM locations from a memory device; and

control the play of the game of chance.

20. The method of claim 18, wherein:

the one or more other gaming software modules include a game flow software module located on the remote gaming device;

the method further comprises generating, by the game flow software module, a game flow for the game of chance;

communicating presentation state information for the game presentation with one or more other gaming software modules via one or more application program interfaces comprises receiving game state information from the game flow software module; and

the game presentation logic for generating graphics and audio information is separate from game flow logic for the game flow software module.

21. The method of claim 11, further comprising:

communicating presentation sub-state information via one or more application program interfaces.

22. A method comprising:

by a gaming operating system being executed or executing from one or more random-access memory (RAM) locations within a gaming machine;

receiving a request to start the game of chance;

communicating, via a game flow application program interface, a command to a game flow software module that, when received by the game flow software module, causes the game flow software module to generate game state information for a plurality of game states in a game flow for the game of chance;

communicating a plurality of commands to the gaming machine to control the play of the game of chance based on the game state information; and

communicating with one or more other gaming software modules via one or more application program interfaces,

wherein logic for implementing the gaming operating system, including core gaming machine-wide functionality, is separate from logic for the one or more other gaming software modules, including game flow logic for implementing the game flow software module to generate the game state information.

23. The method of claim 22, wherein:

the one or more other gaming software modules include a game presentation software module;

communicating with one or more other gaming software modules via one or more application program interfaces comprises communicating with the game presentation software module;

the game flow logic for generating the game states is separate from game presentation logic for the game presentation software module;

the logic for implementing the gaming operating system is separate from the game presentation logic for the game presentation software module; and

the method further comprises generating, by the game presentation software module, a game presentation for the game of chance based on the game state information, the game presentation being suitable for display on a display screen of the gaming machine.

24. The method of claim 23, wherein the game presentation software module is located on or within a remote gaming device at a location remote from the gaming machine, and the game presentation software module causes the game presentation to be displayed on a display screen of the remote gaming device.

25. The method of claim 22, wherein the one or more other gaming software modules include a gaming device driver that communicates with a gaming device located on the gaming machine.

26. The method of claim 25, wherein the gaming device is selected from the group consisting of lights, printers, coin hoppers, bill validators, ticket readers, card readers, key pads, button panels, display screens, speakers, information panels, motors, mass storage devices and solenoids.

27. The method of claim 22, further comprising:

receiving a request to play a particular game of chance;

loading, in response to the request, from a memory storage device a game flow software module that generates the game flow for the particular game of chance; and

loading, in response to the request, from a memory storage device a game presentation software module that presents the game of chance on a display screen of the gaming machine.

28. The method claim 22, further comprising:

communicating, via an application program interface, a command to a bonus game flow software module, the command causing the bonus game flow software module to generate a bonus game flow for a bonus game.

29. The method of claim 22, wherein one or more of the application program interfaces are each selected from the group consisting of:

a game flow interface, a presentation interface, a bank interface and a configuration interface.

30. The method of claim 22, further comprising:

communicating game information via the one or more application program interfaces.

31. The method of claim 30, wherein some or all of the game information is selected from the group consisting of:

game state information, presentation state information, configuration information, betting information, game outcome information, critical event data, I/O information and metering information.

32. The method of claim 22, further comprising:

receiving a game outcome from the game flow software module via at least one of the one or more application program interfaces.

33. The method of claim 22, further comprising;

sending a command to process an award to the game flow software module via the game flow application program interface.

34. The method of claim 22, further comprising:

receiving presentation state information from a game presentation software module via the one or more application program interfaces.

35. The method of claim 34, wherein the game presentation software module is located on a remote gaming device.

36. The method of claim 22, further comprising:

sending a command to the game flow software module via the game flow application interface, the command causing the game flow software module to end the game of chance.

37. The method of claim 22, further comprising:

storing a game history for the game of chance to a non-volatile memory device.

38. The method of claim 22, further comprising:

communicating game information to one or more remote gaming devices.

39. The method of claim 38, wherein at least one of the remote gaming devices is a player tracking server.

40. The method of claim 38, wherein at least one of the remote gaming devices is a gaming machine.

41. The method of claim 22, further comprising:

loading one or more gaming software modules from a remote file storage device.