Slot Machine Domain Requirements Coded List (by Concern)
Requirements used for our experience have an ID, which is used for later reference (for example in ThemeDoc diagrams).
Slot Machine Game | |
---|---|
R-GM-1 | Slot machines have 5 reels |
R-GM-2 | Reels spin when play button is pressed |
R-GM-3 | Prizes are awarded according to a pay table means for cashing the credits out. It could be a ticket printer, coin hopper. |
R-GM-4 | A slot machine has one or more devices for entering money. |
R-GM-5 | As money is inserted credits are “assigned” to the player. |
R-GM-6 | A slot machine must provide some wy for cashing credits out (hopper, ticket printer, etc). |
Meters | |
---|---|
R-M-1 | Credit meter: shall at all times indicate all credits or cash available for the player to wager or cashout (GLI 11 4.10.1) |
R-M-2 | Credit Meter Incrementing: The value of every prize (at the end of a game) shall be added to the player's credit meter [….]. The credit meter shall also increment with the value of all valid coins, tokens, bills, Ticket/Vouchers, coupons or other approved notes accepted. (GLI 11 4.10.5) |
R-M-3 | Accounting Meters (GLI 11 4.10.9): Coin In: […] a meter that accumulates the total value of all wagers […]. Games-played: accumulates the number of games played; since power reset, since door close and since game initialisation. |
R-M-4 | Meters should be updated upon occurrence of any event that must be counted, including: play, cashout, bill in, coin in. |
G2S | |
---|---|
R-G2S-1 | The G2S protocol is designed to communicate information between an GM, and one or more host systems. |
R-G2S-2 | Meters within the G2S protocol: Each device is metered separately. Meters are always available on a device-by-device basis. (G2S 1.16) |
R-G2S-3 | Some G2S meters are: gamesSinceInitCn Number of games since initialisation. WonCnt: Number of primary games won by the player. LostCnt: Number of primary games lost by the player. |
R-G2S-4 | Important events must be reported in real-time, including: error conditions, tickets inserted, ticket printed. |
Error Conditions | |
---|---|
R-EC-1 | Gaming devices shall be capable of detecting and displaying error conditions and illuminate the tower light for each or sound an audible alarm. |
R-EC-2 | Error conditions should cause the gaming device to lock up and require attendant intervention. Error conditions shall be cleared either by an attendant or upon initiation of a new play sequence after the error has cleared except for those deemed as a critical error. |
R-EC-3 | Error conditions are: coin jam, reverse coin in, stacker full, bill jam, external doors open. |
R-EC-4 | Video based games shall display meaningful text as to the error conditions. |
R-EC-5 | Error conditions shall be communicated to an on-line monitoring and control system when this is available. |
Program Resumption | |
---|---|
R-PR-1 | After a program interruption (e.g., processor reset), the software shall be able to recover to the state it was in immediately prior to the interruption occurring. |
R-PR-2 | Restoring Power. If a gaming device is powered down while in an error condition, then upon restoring power, the specific error message shall still be displayed and the gaming device shall remain locked-up […]. |
R-PR-3 | An SM must store all meter information in persistent memory. (G2S 1.16) |
Game Recall | ||
---|---|---|
R-GR-1 | Information on at least the last ten (10) games is to be always retrievable on the operation of a suitable external key-switch, or another secure method that is not available to the player. | |
R-GR-2 | Last play information shall provide all information required to fully reconstruct the last ten (10) plays. All values shall be displayed; including the initial credits, credits bet, and credits won, payline symbol combinations and credits paid whether the outcome resulted in a win or loss […]. This information should include the final game outcome, including all player choices and bonus features. |
Demo Mode | ||
---|---|---|
R-DM-1 | Demo mode must enable testing of gaming machine features (both software and hardware based) | |
R-DM-2 | It must be possible to force the outcome of the gaming machine or control the winning prize. |
Slot Machine Domain Requirements List Grouped by Concern
A more detailed list of the main requirements per concern follows:
Slot Machine
- Slot machines have 5 reels
- Reels spin upon play button is pressed
- Prizes are awareded according to pay table
- A slot machine has device or entering money (a bill acceptor).
- As money is inserted credits are “assigned” to the player
Meters
- Credit meter: shall at all times indicate all credits or cash available for the player to wager or cashout (GLI 11 4.10.1)
- Software Meter Information Access. The software meter information shall only be accessible by an authorized person and must have the ability to be displayed on demand using a secure means. (GLI 11 4.10.8)
- Credit Meter – Incrementing. The value of every prize (at end of a game) shall be added to the player’s credit meter [….]The credit meter shall also increment with the value of all valid coins, tokens, bills, Ticket/Vouchers, coupons or other approved notes accepted. (GLI 11 4.10.5)
- Electronic Accounting and Occurrence Meters. Electronic accounting meters shall be at least ten (10) digits in length. These meters shall be maintained in credit units equal to the denomination, or in dollars and cents. If the meter is being used in dollars and cents format, eight (8) digits must be used for the dollar amount and two (2) digits used for the cent amount […] all meter information specified in this section (4.10) which must be preserved for a minimum of 72 hours in the event of power loss to the gaming device. (GLI 11 4.10.9)
- Accouting Meters GLI 11 4.10.9)
- Coin In* The machine must have a meter that accumulates the total value of all wagers, whether the wagered amount results from the insertion of coins, tokens, currency, deduction from a credit meter or any other means.
- Coin Out* The machine must have a meter that accumulates the total value of all amounts directly paid by the machine as a result of winning wagers, whether the payout is made from the hopper, to a credit meter or by any other means.
- Coin Drop*. The machine must have a meter that accumulates the total value of coins or tokens diverted to the drop;
- Attendant Paid Jackpots*. The machine must have a meter that accumulates the total value of credits paid by an attendant resulting from a single winning alignment or combination, the amount of which is not capable of being paid by the machine itself.
- Games-played. The machine must have meters that accumulates the number of games played i. Since power reset; ii. Since door close; and iii. Since game initialization (RAM clear).
- Meters should be updated upon ocurrence of any event that must be counted
Error Conditions (GLI 4.1.3.1, Nevada 1.070)
- Gaming devices shall be capable of detecting and displaying the following error conditions and illuminate the tower light for each or sound an audible alarm.
- Error conditions should cause the gaming device to lock up and require attendant intervention except as noted within this section.
- Error conditions shall be cleared either by an attendant or upon initiation of a new play sequence after the error has cleared except for those denoted by an “*” which will require further evaluation since deemed as a critical error.
- Error conditions shall be communicated to an on-line monitoring and control system, if applicable.
- Error condition include:
- Coin Acceptor
- Coin in
- Coin Jam
- Reverse Coin in
- …
- Hopper
- Hopper empty
- Hopper jam
- …
- Bill Acceptor
- Stacker full
- bill jam
- stacker door open
- stacker removed
- …
- Printer errors
- paper low
- paper jam
- printer disconnected
- Door open
- All external doors (i.e. Main, belly, top box)
- Drop box door
- bill validator door
- Other EC
- RAM error
- Low RAM battery
- Reel spin error
- Power reset
- […] video based games shall display meaningful text as to the error conditions.
Program Interruption and Resumption (GLI 4.14)
- Interruption. After a program interruption (e.g., processor reset), the software shall be able to recover to the state it was in immediately prior to the interruption occurring.
- Restoring Power. If a gaming device is powered down while in an error condition, then upon restoring power, the specific error message shall still be displayed and the gaming device shall remain locked-up. This is unless power down is used as part of the error reset procedure, or if on power up or door closure, the gaming device checks for the error condition and detects that the error is no longer in existence.
G2S
- The Game-to-System, or G2S, protocol is designed to communicate information between an electronic gaming machine, or EGM, and one or more host systems.
- Meters Within the G2S protocol, each device is metered separately. Meters are always available on a device-by-device basis. An EGM MUST store all meter information in persistent memory. The class description for a device includes the list of meters used by the device. (G2S 1.16)
- Event Handling The G2S protocol uses events to report that an action has taken place at an EGM. Events are always reported after the action has taken place—events are after-the-fact. In general, an event is generated whenever the state of a device changes (G2S 1.18
- Meters are:
- G2S_tiedCnt; “Number of primary games where there were no credits won or lost”;
- G2S_wonCnt; “Number of primary games won by the player”;
- G2S_lostCnt; “Number of primary games lost by the player”;
- G2S_wageredAmt; “Total amount wagered”;SAS 0x0000; SAS 'total coin in'
- G2S_gamesSinceInitCnt: “Number of games since initialization.” (G2S table 5.43)
- G2S_cabinetDoorOpenCnt: “Number of cabinet door opens.” (G2S table 5.43)
- Persistent Memory (G2S 1.24)
- The G2S protocol requires that an EGM maintain certain critical protocol-related data in persistent memory including meters, transaction logs and configuration data.
- If persistent memory fails or is reset by the operator,certain critical information may be lost. If this happens, the EGM MUST notify all affected hosts. For this reason, the commsOnLine command contains a series of attributes that indicates whether persistent memory may have been compromised.
Game Recall
- (GLI 4.18.1) Number Of Last Plays Required. Information on at least the last ten (10) games is to be always retrievable on the operation of a suitable external key-switch, or another secure method that is not available to the player.
- (GLI 4.18.2) Last Play Information Required. Last play information shall provide all information required to fully reconstruct the last ten (10) plays. All values shall be displayed; including the initial credits, credits bet, and credits won, payline symbol combinations and credits paid whether the outcome resulted in a win or loss. This information can be represented in graphical or text format. If a progressive was awarded, it is sufficient to indicate the progressive was awarded and not display the value. This information should include the final game outcome, including all player choices and bonus features. In addition, the results of Double-up or Gamble (if applicable).