Guides

16.1.1  Game Results Sets must have a Fixed Paytable Structure. Variable Prizes, e.g. shares depen- dent on the number of Tickets sold are not permitted, except as additional bonuses.

16.1.2  The theoretical Payback percentage and Prize odds of Game Results Sets must be constant (a fixed number), as determined by the Fixed Paytable Structure.

15.1.1  Game Results Sets (Deals) and Subsets (Decks, Rolls) must be specified on Tickets and/or in cGaming System, as applicable with the following parameters, at a minimum:

1. Game name (theme);
2. Unique identifier;
3. Ticket price;
4. Paytable unique identifier; and
5. Theoretical Payback percentage.

15.1.2  There must be no variations of pre-defined parameters when Game Results Set and Tickets are duplicated for extended sales.

14.1  Integrity

14.1.1  Both one-ply and two-ply physical Tickets must have tamper proof design in order to pre- vent determination of winning or losing Tickets. In addition, two-ply physical Tickets must be designed with sufficient opacity of layers, adhesive, Ticket size and cuts, pull-tabs covering results and printing variations to prevent determination of winning or losing Tickets without leaving signs of tampering.

Tickets may be offered for sale to players as physical Tickets and/or in the form of Electronic Tickets. The word “Ticket” is used to mean either one, unless specified as “physical Ticket”. Furthermore, physical Tickets may be designed with one-ply or two-plies, where the Game result is hidden between non-transparent plies.

13.1.1  Player Terminals and/or Backend System must have the capability to display a complete Play history for the most recent Game played and nine Games prior to the most recent Game. Retention and display of prior Games is also preferred. The display must indicate the following information in a clear and understandable manner, and in the same sequence as the original Game Play:

12.1  Game Play

12.1.1  The Player Terminal may only initiate Game Play:

11.1.1    Player Terminal must be capable of immediately detecting, displaying, recording in a Game error log and communicating to the Backend System, if technically possible, the conditions listed in 11.1.2.

11.1.2  The Player Terminal and all peripherals must be disabled under the following conditions, and may only be enabled after the condition has been resolved:

10.1.1  The Player Terminal and/or Backend System must have the capability to set and display specific Game options. If Player Terminal is utilized, restricted technical procedures must be followed, e.g. require the use of a separate configuration program, as applicable.

Restricted Game options are those options that, if configured incorrectly, would result in a violation of one or more of these Standards in this document, or introduce a risk to the integrity, security and accounting capability of the Game that is not mitigated through other controls.

9.1.1  The Player Terminal must provide the following Administrative Modes:

1. Audit mode - used for the purposes of verifying the last Game including any status indicators and meters;
2. Game option mode - for setting and verification of Game options; and
3. Diagnostic mode - for the testing of terminal hardware, software and communication with Associated Equipment.

9.1.2  The Player Terminal must have the following minimum diagnostic functions, if applicable: