they can't get rid of the awps from 32red theyre my fav!
can someone explain to me how they are not random.
Have you never played a Fruit Machine, and maybe got the "Hi Lo" with numbers 1 to 12? If so, do the results from going Hi or Lo from any number look as though they are "fair" (e.g. the number was selected randomly, and you had a chance of winning equivalent to the natural odds of selecting a single number from a "pack" of 12).
Most regular players know that these Fruit Machines will "block" larger wins until they have taken in enough since the previous large payout to bring the RTP back within a pre-set target range. One rather obvious sign of this is getting a number such as "2", and going Hi, only to get "1" - and this always seeming to happen to "block" the advance to a far larger win, and further happening a good deal more often than the natural odds of selecting "1" from a "pack" of 12.
The AWP games within the MGS suite are pretty good reproductions of Fruit Machines. There are many patterns, and some are just so very obvious that it is clear the games are not random. Take Treasure Ireland, on the feature trail. If you have an extra life, and are near to the "block" and land on "?", you will ONLY throw the number needed to advance to the other "?". This can result in a cycle of 6,8,6,8,6,8...... etc, with each bonus being a non-advancement one, such as "eliminate", "continue/yes". The sequences of 6,8,6,8.... are very noticeably non-random, and it is clear you are trapped in a piece of "eye candy" whose only purpose is to make you think an extra life has any real value. Once the extra life has been lost on "?", you will find the cycle of 6,8,6,8.... immediately broken, and you will be allowed to advance to the current "block", which represents how much the game is willing to pay.
The errors in Gee Gees are BECAUSE the game is NOT a random slot at all, and runs to pre-determined max win which increases as the game takes in more and more money. When the discoball was held, and the next spin was awarded nudges, it was NOT intended that the jackpot be paid on that spin, however, instead of doing what a proper Fruit Machine would have done, which would be to award one less nudge than was needed, it awarded enough to bring down BOTH because the error failed to carry the held reel over to what was probably a different routine in the software, and this routine then replaced the held discoball with the symbol that was intended to be offered, which would have given the player a "near miss" with 2 discoballs to nudge down, perhaps in the hope of getting a hold, and have a chance of receiving the third on the next spin.
This case should be a significant embarrassment to MGS, but I see no real concern from operators, although it is early days yet.
Perhaps the only way to make MGS take this seriously is to make a specimen complaint through proper channels, asking for the spins to be formally audited, and an explanation given as to why you were not paid out for 3 discoballs. Once the error is made "formal" in this respect, MGS will HAVE to take it seriously and fix it.
First, make a FORMAL complaint to the casino, and if no luck, to a dispute resolution service or the gaming regulator.
Since this was at 32Red, it should be enough to make a formal complaint to them, and also raise your concerns with one of the top people, who happen to be active members of this forum. Pat Harrison (operations manager) and Ed Ware (CEO). The fact that there is no history is a concern in itself, this history MUST be found (it is an eCogra requirement for play history to be kept, and made available - particularly in cases such as this). I believe 32Red recently decided to go for eCogra certification. If it is an onerous task to extract the play history, it is the fault of MGS, rather than 32Red, and means the AWP part of their software does not adhere properly to requirements.
Once a play history is found, WHAT happened should be pretty obvious, although WHY may not be.
Since this is a common enough error, it should be possible to recreate a sequence where a held reel is swapped out in the spin, although it is unlikely to be a denial of a large win. A sequence of screenshots, or better still a video, can be presented as evidence of there being this bug.
I play the AWP games a great deal, and I do NOT want to see them go, but players DO need to be given an HONEST description of what these games really are, since many non-Brits have no real understanding of non-random UK style AWP games, (other than that they are "rigged", something more associated with rogue software).
Despite my extensive play on these AWP games, I have seen this particular error (held reel swapped for BAR next spin) ONCE. This may be because I know how these games work, and rarely bother with "hold" unless I am GUARANTEED a win by holding reels for the next spin, or I have 2 Jackpot symbols (however, I have NEVER had the third come in). Another possibility is that this error crept in recently, and I am going to see more of it this month.