This is a huge release for several reasons: First, in order to ensure that RBG will be compatible with the next major update to the IOS platform, I had to rearchitect the foundation/framework. Everything appears to be working correctly, but in order to be absolutely sure, I have to invest in an upgraded development environment in order to be able to perform the necessary beta testing. The changes that I made were less difficult than I had anticipated. This either means I was overly intimidated by the required changes or that I have learned a lot more about developing for Apple devices that I had realized. The good news is that I should have until June to fully vet the new architecture. This will be my number one priority for the next couple of months. This release adds yet another new game: Dice Baccarat. I fully expect that the Baccarat Players will like this one. As the name implies, the game uses dice instead of cards. Also, rather than complex rules that govern whether 2 or 3 cards are used to complete a hand, both the Banker and the Player receive 3 dice. The outcome of those dice represent the final total for each hand. I like the game and I hope you will, too! With the addition of this game, RBG now boasts 76 games that you can learn, practice, and enjoy. In addition to the new game and the foundational redesign, I invested a lot of time and effort implementing an extremely robust regression testing module. This module provides me the ability to define the cards and expected outcomes for a specific game and then to simulate those hands, read the hands that are dealt, compare the hands and verify the outcome to what is predefined by the test. This will hopefully prove invaluable to ensuring that when code is changed in the core engines to support a game, I can be assured that those code changes will not break an existing game. Currently, I have 100+ tests defined across 15 games. Bug Fixes: 1. Craps & Crapless Craps: Place wagers that were not working on a Come Out roll were not being properly refunded and removed if the established point matched the Place space. 2. Roulette: Rolando reached out using "Send Feedback" to alert me to the fact that wagers could not be placed on the row for 13, 14, 15. From what I was able to determine, I accidentally deleted those coordinates for the IPhone 16 Pro Max sized devices when the game was updated to support the new iPhone AIr devices. Thanks so much for the heads up, Rolando! That's the type of bug that I may never have noticed because that size device is only ever used on a simulator. Happy 2026 to all! As always, I appreciate your continued support and the constant stream of requests, suggests, and even the bug reports. If you haven't already, please consider leaving a review in the App Store to share your thoughts with others who are just discovering RBG. Please be safe! ~Danny

I wasn't planning on any additional releases for the rest of the year. However, Kyle reached out using "Send Feedback" and reported an issue about a hand using three wild cards having been read incorrectly. When I dove deeper into his report, I uncovered a pretty significant flaw in how those hands were being read and how they were being sorted. I've updated the code and performed some significant regression testing. The new approach is leaner and more elegant and everything appears to be "good to go". Thank you, Kyle! I appreciate that you reached out and that you sent me a screenshot to use while I was diagnosing and triaging the issue. There is also a bug fix in this release that applies to how two hands with natural Trips were being compared. I have no idea when the code "broke", but a Player was kind enough to reach out and make me aware. It is flabbergasting (and frustrating) that I can inadvertently break something that has worked for years and not be aware of it. If RBG ever hits critical mass, my first investment will be in a QA team. I've created a backlog item to invest some time in developing a more robust regression testing engine. Lastly, I had to make a slight adjustment to the start up sequence from the recent release. My current major focus is on rearchitecting Riverboat Gambler so that it will remain compatible when the next major version of IOS gets released next summer. Because this is the first app I ever created and I have been learning on this journey, this work requires a chainsaw - not a scalpel. Lots to do!!! Thanks to Rob for reaching out and letting me know about the issue! Assuming this release proves to be stable, it will be the final release of the year (I said that LAST time - DOH!) Happy holidays to all! I sincerely hope you have the opportunity to spend quality time with the people who are most important to you! ~Danny

I wasn't planning on any additional releases for the rest of the year. However, Kyle reached out using "Send Feedback" and reported an issue about a hand using three wild cards having been read incorrectly. When I dove deeper into his report, I uncovered a pretty significant flaw in how those hands were being read and how they were being sorted. I've updated the code and performed some significant regression testing. The new approach is leaner and more elegant and everything appears to be "good to go". Thank you, Kyle! I appreciate that you reached out and that you sent me a screenshot to use while I was diagnosing and triaging the issue. Assuming this release proves to be stable, it will be the final release of the year. Happy holidays to all! I sincerely hope you have the opportunity to spend quality time with the people who are most important to you! ~Danny

I am hoping this is the final release for 2025 and I hope everyone has the opportunity to enjoy the upcoming holiday season with the folks who are most important in their lives! This release addresses a couple of issues with the Riverboat Gambler Academy games on the new IPhone Air devices AND adds Roulette to those devices. Additionally, it increases the decreases the frequency of ads to every 100 hands (from 95). As I've promised, I will continue to decrease that frequency as the Player Community continues to grow. Please keep spreading the word to your friends, family, and casino buddies. There is a full backlog of requests and enhancements and I'm looking forward to jumping into those in 2026. This has been a fabulous year and I have been humbled by the support and encouragement from the Player Community. Please stay safe! ~Danny

This is a pretty consequential release for a couple of reasons. First, game #75 (requested by Sean and his wife, Nicole) has been added. More about that in a second… Additionally, I was finally able to work in the time necessary to update my development environment so that I could properly support the latest iPhone17 models. It’s difficult to explain how complicated (and risky) it can be when I update my development environment. When it fails, it is a nightmare to restore my environment. Because I don’t have the resources to own a myriad of computers like a “big box software company” may, I must time my upgrades for when I feel like the current RBG release is ultra stable (a.k.a bug free). Additionally, I have to be confident that the version of the tools to which I will upgrade are also considered stable for my equipment. Most of the time, an environment upgrade only requires me to update the tools that I use to write the code. But, sometimes, it’s also necessary to upgrade my underlying operating system. When both are required, the risk of something going wrong is huge. In order to support the new IPhone Air, I had to upgrade my tools and my laptop. I had to do this in order to install the development tools that would allow me to use simulators for that new device. Thankfully, all upgrades worked. There was a lot of code that needed to be updated to work with the most recent IOS version and the development studio, but those changes were not overly involved and things seem to be working as expected. In this release, I was able to use the simulators for IPhone Air devices to test all of the games. I uncovered many issues with the preliminary screens that I created in advance of the environment refresh. I believe I have addressed all of them. Additionally, while testing, I uncovered some issues with screens for other phone devices. I want to stress to all RBG Player: if you encounter anything “funky” with a game on your device, please don’t hesitate to reach out using “Send Feedback” and let me know. You will not hurt my feelings. With 75 games on multiple devices and screen resolutions, there are certainly going to be issues that I have not caught. I don’t make a secret of the fact that I play RBG everyday, but that I almost exclusively play Mississippi Stud. Another “win” in this release is that I added Craps & Crapless Craps to the IPhone Air devices. I still must do some work to plot the coordinates for Roulette. My goal is to add that game in next week’s release which I hope will be the final release for 2025. The new game is "Trilux Blackjack". Yes, yet another Blackjack variant! This game is really just standard Blackjack, but it puts the optional Trilux bonus on steroids. It's almost impossible not to play this game given the potential payouts of those bonuses. Many thanks to Sean and Nicole for recommending the game and then testing and providing their feedback. As always, it is the RBG Player Community that continues to allow this app to achieve its potential. Please stay safe! ~Danny

This "maintenance release" includes several updates to underlying "shared frameworks" that are used by RBG to handle things like ads, error handling, and logging. Additionally, I've streamlined some code to consolidate the code base. The next release will include another new game as I get back to the business of focusing on games and features. Please keep your suggestions and requests coming. The backlog is HUGE, but there is always room for more Player ideas. Hopefully, there will only be one more release before the holidays. Stay Safe! ~Danny

This "maintenance release" includes several updates to underlying "shared frameworks" that are used by RBG to handle things like ads, error handling, and logging. Additionally, I've streamlined some code to consolidate the code base. The next release will include another new game as I get back to the business of focusing on games and features. Please keep your suggestions and requests coming. The backlog is HUGE, but there is always room for more Player ideas. Hopefully, there will only be one more release before the holidays. Stay Safe! ~Danny

Due to a dependency on some 3rd Party libraries that have limited "backwards compatibility" as is applies to device operating system versions, I've had to increase the minimum version of iOS that Riverboat Gambler will support. As of this release, RBG will require iOS version 15 or greater. While that might sound bad, I don't think it will have far reaching ramifications given that logs indicate most of the folks in the Player Community are already using iOS 15 or higher. Progress is generally good and upgrading our devices typically brings exciting new features and benefits! Additionally, this release temporarily renames some games while some confusion about trademarks is resolved. Once the misunderstandings have been addressed, I'm confident/hoping the name changes can be reversed. A lot more games and features are coming! Please keep your suggestions and requests coming and, if you haven't already, please consider leaving a review in the App Store. Be Safe! ~Danny

Due to a dependency on some 3rd Party libraries that have limited "backwards compatibility" as is applies to device operating system versions, I've had to increase the minimum version of iOS that Riverboat Gambler will support. As of this release, RBG will require iOS version 15 or greater. While that might sound bad, I don't think it will have far reaching ramifications given that logs indicate most of the folks in the Player Community are already using iOS 15 or higher. Progress is generally good and upgrading our devices typically brings exciting new features and benefits! Additionally, this release temporarily renames some games while some confusion about trademarks is resolved. Once the misunderstandings have been addressed, I'm confident the name changes can be reversed. A lot more games and features are coming! Please keep your suggestions and requests coming and, if you haven't already, please consider leaving a review in the App Store. Be Safe! ~Danny

This release contains a fix to the games that use fully-wild wild cards. In cases where 3 wild cards were in a hand, the potential existed for a Straight Flush to be incorrectly read. This impacted DJ Wild, Wild Card Stud, and some of the video poker games. I screwed things up when I "tweaked" the code for The Riverboat Gambler Academy simulations. Doh! Many thanks to Kurt, Rita, Kelly, Jake, and others who reached out with screenshots to help address that bug! Another bug was reported by Jon and it impacted ALL of the Video Poker variants on iPads. The issue was that the results of a hand were not being properly displayed. The results (and the instructions for a hand after the deal) were actually positioned behind some of the cards. Thanks for taking the time to be part of the solution, Jon! More games are coming and some really cool requested enhancements. Please keep your suggestions and requests coming and, if you haven't already, please consider leaving a review in the App Store to share your thoughts with others. Stay safe! ~Danny

This release contains a fix to the games that use fully-wild wild cards. In cases where 3 wild cards were in a hand, the potential existed for a Straight Flush to be incorrectly read. This impacted DJ Wild, Wild Card Stud, and some of the video poker games. I screwed things up when I "tweaked" the code for The Riverboat Gambler Academy simulations. Doh! Many thanks to Rita, Kelly, Jake, and others who reached out with screenshots to help address that bug! Another bug was reported by Jon and it impacted ALL of the Video Poker variants on iPads. The issue was that the results of a hand were not being properly displayed. The results (and the instructions for a hand after the deal) were actually positioned behind some of the cards. Thanks for taking the time to be part of the solution, Jon! More games are coming and some really cool requested enhancements. Please keep your suggestions and requests coming and, if you haven't already, please consider leaving a review in the App Store to share your thoughts with others. Stay safe! ~Danny

This is probably one of the most consequential releases I’ve made for Riverboat Gambler. The release brings the total game count up to 74 on IOS. But, it also introduces a feature of which I am extremely proud: The Riverboat Gambler Academy! The vast majority of casino carnival (table) games are based on Poker; a game that has been around for more than 200 years. Personally, I have been playing Poker for more than 45 years and I still typically find myself in a casino 2-4 times each week. Frequently, I am asked, by new Players, to explain how to play a game (usually Mississippi Stud, because that is my preferred game). Most times, explaining the rules of a carnival game is easy. It’s just a matter of pointing out how normal Poker rules will be applied to the cards that are dealt. The real challenge occurs when folks don’t understand the basics of Poker; the fundamentals that govern all variants of the game. In Poker, the Player uses random cards from a deck that typically contains 52 cards to form the best possible hand against an established rank of hands. In “The Riverboat Gambler Academy”, I have added a set of simulations that I personally find invaluable to teaching anyone how to play poker-based games. At the end of the day, Poker is 100% about having the strongest/best hand at the table! The Academy simulations focus on developing an understanding of the nine standard poker hands (ten, when "High Card only" is counted; 11 when wild cards can be used to create "5 of a Kind”). Additionally, the simulations focus on helping a new Player understand the rank order of these hands with respect to their “strength”. With The Riverboat Gambler Academy, my aspiration is that folks who typically avoid the “carnival game pits” because they are intimidated by games they don’t understand, will feel more comfortable about trying those games. Why is this important to me? Because, like many, when I go to a casino, it’s not unusual for my friends and loved ones to avoid “the tables” because they “just don’t get it”. So, they just watch or they play slots. Introducing TWO new games: Fan-Tan This game has been on the “must do” list for a few years. It was requested by longtime supporter “Bishop Bryan”. Bryan gets the credit for most of the more complicated games in RBG (Craps, Roulette, Boule, Pai Gow Tiles…) and he’s been busting my chops for a long time since he requested this one. Recently, another Player, Michael (“Baccarat Broski”) brought it up and I realized that the underlying framework had evolved to the point that supporting the game would actually be quite simple to do. It’s an odd, yet interesting, Asian game and I encourage everyone to read the “About” and “How to Play” documentation. I’ve done my best to implement animation that does the game “justice” because it is unlike any other game you’ll experience in a casino. Five Treasures Baccarat Lately, Baccarat has been getting a lot of attention in Riverboat Gambler. There has been an influx of Baccarat Players discovering the app and they have been submitting their feedback and requests. “Big D” in Tahoe made me aware of Five Treasures and also collaborated with me on figuring out how to best support the TEN possible wagers in this game. As a result of his input, I’ve made changes to RBG that will enhance the ability to support some other games that are currently in the backlog. The game was a favorite of several of the folks who participate in the RBG beta program. If you’re not familiar with Baccarat, I highly encourage you to read the history and rules in the “How To Play” section. As one would expect, the variants are similar, but, they also do differ in some significant ways! As always: “THANK YOU”, everyone for your support, patience, and encouragement. Please stay safe! If you haven’t already, please consider leaving a review in the App Store to encourage others to “check things out”! ~Danny

In this release, I've performed a major overhaul to the iPad screens and started to lay a foundation for supporting the new iPhone 17 with more exact screens. The next release will contain yet another game as well as what I believe will be some extremely valuable training simulations. Stay tuned! Additionally, I have changed the order of the main menu to list the sub menus that group similar games at the top of the list (after my game, Mississippi Stud). I'm trying to figure out the best way to present the games organized by the appropriate "pit". A couple of things to remember relative to menus: 1. Any games that you designate as a "Favorite' in Preferences will be listed at the top of the menu. 2. The games on the Search Menu are always listed alphabetically. 3. Mississippi Stud will always be the first game on the games list because it is the reason that I created RBG and is still my primary "go to game" If you have any ideas or suggestions about the main menu, please reach out to me with your input. I'd love to hear it! Bug Fixes: 1. Asia Poker: Matthew uncovered an extremely rare edge case that was resulting in accidental Straights being played in the High Hand without properly optimizing the other hands. 2. Farobank: The wager that is required for the "mini-game" at the end of a deck was not being properly recorded. 3. Reading Straights: Some changes I made in the last release to "streamline things" had an impact on a handful of Straight situations; most notably the 3 Card Straights used in Blackjack for the Trilux bonus and "double gut shots" that used wild cards. Huge "Thank You!" to Yvette who uncovered the problem and took the time to alert me using "Send Feedback"! Seriously, folks! Our Player Community is amazing and patient and the primary reason RBG continues to evolve into the best table games simulator in the mobile market. I appreciate all of you! As always, please share with your friends, family, and casino buddies. RBG continues to evolve from the support and participation of a great Player Community! Please stay safe! ~Danny

In this release, I've performed a major overhaul to the iPad screens and started to lay a foundation for supporting the new iPhone 17 with more exact screens. The next release will contain yet another game as well as what I believe will be some extremely valuable training simulations. Stay tuned! Additionally, I have changed the order of the main menu to list the sub menus that group similar games at the top of the list (after my game, Mississippi Stud). I'm trying to figure out the best way to present the games organized by the appropriate "pit". A couple of things to remember relative to menus: 1. Any games that you designate as a "Favorite' in Preferences will be listed at the top of the menu. 2. The games on the Search Menu are always listed alphabetically. 3. Mississippi Stud will always be the first game on the games list because it is the reason that I created RBG and is still my primary "go to game" If you have any ideas or suggestions about the main menu, please reach out to me with your input. I'd love to hear it! Bug Fixes: 1. Asia Poker: Matthew uncovered an extremely rare edge case that was resulting in accidental Straights being played in the High Hand without properly optimizing the other hands. 2. Farobank: The wager that is required for the "mini-game" at the end of a deck was not being properly recorded. As always, please share with your friends, family, and casino buddies. RBG continues to evolve from the support and participation of a great Player Community! Please stay safe! ~Danny

Big release! Riverboat Gambler now contains 72 games! In this release, by request, I’ve added two additional variations of Baccarat: EZ Baccarat & Golden Frog Baccarat. Many thanks all who helped to beta test these games and most especially Michael who went to great lengths to document each game and provide me with reference materials. If you’re new to Baccarat, please read the “How to Play” to understand the game and the nuances that exist between the different variations in RBG. The differences are slight, but they are important and I cannot elaborate on them in these release notes. There are also a slew of fixes and enhancements in this release: 1. Baccarat (BUG): While modifying the core code for the new Baccarat games, I screwed something up such that the final hand results were not properly including paid wins for Ties, Player Pair, and Bank Pair wagers. Thanks to everyone who reached out to report the issue and provide screenshots. 
 2. Baccarat (BUG): A special shout out to Mark who reached out using “Send Feedback” to point out that the new Dragon Bonus that was added a couple of releases back was not paying properly when the payout was awarded from a Natural win or when a hand ended in Tie.
 3. Baccarat (ENHANCEMENT): I really started to get frustrated trying to "do the math" when the first two sets of cards were dealt in Baccarat so I added a "bubble" that shows the Baccarat total of those first two cards. The bubble disappears after a hand is finalized. Additionally, it does not appear when "Slow Roll" mode is enabled in Preferences; I figure you have plenty of time to "do the math" when you're revealing your own cards.
 4. Casino Wallet (BUG): There was a set of conditions that would improperly display the Casino Wallet if a game was in landscape mode on a phone. “Triple B” reached out via “Send FeedbacK” with a screenshot that made fixing that problem a snap. Many thanks for taking the time Triple B!
 5. Spanish 21 (BUG): There was an issue in Spanish 21 that caused the game to lock up if multiple Double Down actions were made and the Player was betting the Ante max. Kudos to Bobby for catching it and providing me with a screenshot. It was simple to reproduce and fix. Appreciate you, Bobby!
 6. Free Bet Blackjack (ENHANCEMENT): “Chicago Dan” hit me up via text using “Send Feedback” to make me aware that Free Bet should include the optional Push 22 wager. This wager pays if the Dealer busts with a 22 and can also be found in Double Down Madness. Appreciate the help, Dan! As usual, RBG continues to evolve and improve because Players take the time to get involved.
 A LOT more is coming. I’ve been receiving lots of requests and the backlog continues to fill up. If you haven’t already, please consider leaving a review in the App Store to share your experience with others who may consider evaluating the app. It’s one of the best things you can do to help me. Please be safe! ~Danny

This release is contains a couple of bug fixes and enhancements; one of which is intended to support the next release. 1. Double Down Madness (BUG): Thanks so much to Gary for reaching out to report that the game needed to complete the Dealer's hand if the Player hit a Blackjack AND had wagered the optional "Push 22" bonus wager. It's awfully hard to qualify for the bonus if the Dealer just folds against a Blackjack! It seems like a no-brainer, but I totally missed that Use Case. That Gary made the time to reach out using "Send Feedback" to point out this flaw is just one more example of why RBG continue to improve because of Player involvement. Thanks, Gary! 2. Keep It Straight (BUG): I honestly don't know when I screwed things up as it applies to reading Straights, but I suspect it may have been in the previous release when I addressed some issues in Asia Poker. Regardless, I owe a huge debt of gratitude to Corey and David who reached out using "Send Feedback" AND provided me with some screenshots for example of where Straight Flushes were not being identified. Screenshots of issues are invaluable because i can use them to reproduce a hand and trace the code to isolate issues. Thank you Corey and David! I appreciate your help. 3. Three Card Poker (BUG): This bug was easy to fix but never would have been found without the diligence that Chris applied to "stressing" the game! It definitely falls under the heading of "deep dive testing". Chris reached out using "Send Feedback" with detailed steps on how to lock up RBG via a series of unanticipated actions related to the new "Play Blind" feature. I cannot over emphasize how much effort goes into maintaining RBG and how appreciative I am to the Players who "break stuff" and let me know how they did it. Thank you, Chris! I also want the thank Dean for writing in via email to report the same bug. That Players are stress testing RBG really helps me feel better! I’m just “one guy” and doing everything is starting to become a real challenge. Thanks, fellas! 4. Baccarat (Enhancement): Baccarat now supports the optional "Dragon Bonus". I was made aware of this bonus by Michael who has been extremely helpful to me in addressing the Baccarat family of games in Riverboat Gambler. This bonus is actually pretty cool in that it pays based on the point spread between the winning and losing hands of a Baccarat coup. 5. New Baccarat Games Submenu (Enhancement): Baccarat is now listed under a new sub menu for "Baccarat Games". In this release, Classic Baccarat is the only Baccarat game in that menu. Spoiler alert: in the next release there will be some new games added to RBG. Care to guess what type of games they will be?!? Spoiler: the logo at the top of the Baccarat menu will provide some insight in "what's coming"...LOL 6. Zombie, Face Up, Down Under Blackjack on iPads (BUG): I was scratching my head on a series of iPad crashes in the logs that were reporting as "Blackjack" when I received a Send Feedback text from David about Zombie Blackjack crashing on his iPad. That simple text helped me to quickly find the issue and fix it. The Blackjack games all share code and since the app was crashing before Zombie could be fully configured, there was nothing in the logs to distinguish which variants were impacted. Appreciate you, David. Assuming all goes well with this release, there will be a "finalization" release next week and then I will be taking a step back for a couple of weeks. I really need to spend some time working on that "other platform" in order to close the gap in app features. Right now, IOS is crushing the other app! Love you all and appreciate your support! Please keep submitting your ideas and requests. The backlog is HUGE! If you haven't already, please consider leaving a review in the App Store. YOU are my best/only means of advertising. What you say about RBG matters more to potential new Players than anything I can say. Stay Safe! ~Danny

This was supposed to be “next week’s” release, but a bug in Craps required me to pause the last release (67.0.0) and get this puppy out sooner. I hate when that happens; especially because this release is just as huge & impactful as the previous one. I’m simply going to add to the previous release notes. I'm finally able to announce the release of a new game! That brings the total number of games in our virtual pit to 70! The game, "Keep It Straight", was requested by Dylan. This game is best described as a 1st cousin to "High Flush/I Love Suits". But, rather than chasing Flushes, the Player is chasing Straights. There are a couple of nuances, especially the fact that this is the only game of which I'm aware the Player can be forced to Fold. Key differences are: 1. The Dealer must qualify with at least a 3-Card Straight 2. The Player must qualify with at least a 2-Card Straight 3. The Play wager to commit the hand must be 2x-4x the original Ante Like several games, there is an option in Preferences to allow the Player to reveal his own cards after they've been dealt. Be sure to read "How To Play" for all of the details. Personally, I like the game & I'm looking forward to finding it in Live Play. If you're a fan of "Suits", I'm betting you'll like this one, too! Thanks again to Dylan for requesting the game! Additional updates in that were merged into this release: Three Card Poker (ENHANCEMENT) My hat is tipped to Ericha for reaching out and asking about the ability to “Play Blind” in 3-Card Poker. A couple of other folks have asked about this over the years and I was never able to make it work and never added it to the backlog. When Ericha asked, I had an epiphany and was able to easily incorporate it as a result of changes that have been made to the underlying framework over the years. Now, Players will find the option “Play Blind” on that game’s menu. When the feature is on, the cards will be dealt as normal, but the Player cards will be dealt face down. After a brief moment, the Dealer cards will be revealed and then the Player cards will be individually revealed. After the final card has been revealed, the hand will end and the winner will be declared. BUT WAIT - THERE’S MORE! For an even greater level of anticipation, combine the new feature with Player “slow roll” (see “Player Reveals Cards” in Preferences). Used together, the hand does not end until the Player has tapped to reveal their last card. Great suggestion, Ericha. It’s truly going to be a “game changer”! Keno (ENHANCEMENT) Like several games, Keno was originally added as part of a training exercise; I wanted to learn how to code the animation for the ball draws. At the time, device screens where pretty small so I did my best to maximize the screen real estate and make the spots on the board large enough to “tap” Recently, Bob, a seasoned Keno aficionado, reached out via “Send Feedback” to comment that hardcore Keno Players like himself. often relied on the game’s traditional “8 rows of 10 spots” when playing the game. Given that devices are larger these days, it made perfect sense to evaluate a change. Now, Bob, that’s exactly what we have! Thanks for the suggestion! Craps (BUG): The last release hosed up the Preferences screen for Craps on iPads. I’d inadvertently deleted some code that wasn’t being used on iPhone having forgotten that the code was shared between devices types. Sorry about that! If you follow me on Threads, X, Discord, or Facebook, you already knew about this. That's it for now! Please keep your ideas and requests coming. The backlog is pretty large and I'm doing my best to better organize it. As always, if you haven't already, please consider posting a review in the App Store to help promote RBG. I much prefer to be writing code than promoting/marketing the app. Please stay safe! ~Danny

After a few weeks of bug fixes and code refinements, I'm finally able to announce the release of a new game! That brings the total number of games in our virtual pit to 70! The game, "Keep It Straight", was requested by Dylan. This game can be best described as a first cousin to "High Flush/I Love Suits". Rather than chasing Flushes, though, the Player is chasing Straights. There are a couple of nuances, especially the fact that this is the only game of which I'm aware the Player can be forced to Fold. Some key difference include: 1. The Dealer must qualify with at least a 3-Card Straight 2. The Player must qualify with at least a 2-Card Straight 3. The Play wager to commit the hand must be 2x-4x the original Ante Like "Suits" and some of the other games, there is an option in Preferences to allow the Player to reveal his own cards after they've been dealt. Be sure to read "How To Play" for all of the details. Personally, I like the game and I'm looking forward to finding it in Live Play. From a payout perspective, the top bonus of 8000 to 1 for a 7-Card Straight Flush is as attractive as it is in I Love Suits, but, the game also feels like a "slow win/slow burn" type of game - like Pai Gow - because a requirement that the Dealer qualify with at least a 3-Card Straight. It seems to be more challenging for the Dealer to make a hand in this game than in Suits, BUT there is nothing restricting the Player from maxing out the Play bet like there is in Suits. Perhaps there's a "wash' in there somewhere. Thanks again to Dylan for requesting the game! There is also a new feature coming in the next release that will be beta-tested in this release. All I'm going to say is that it only impacts 3 Card Poker and is something that is going to blow the minds of the hardcore 3 Card Poker fans. I'm really excited to release it, but, inline with the need for me to work on release discipline, I'm fighting all of my urges to release it before it's fully vetted by others. I'm confident it should be out in the next release. That's it for now! Please keep your ideas and requests coming. The backlog is pretty large and I'm doing my best to better organize it. The next release will include some pretty significant enhancements to Keno & Three Card Poker that were also requested by Players. Stay tuned! As always, if you haven't already, please consider posting a review in the App Store to help promote RBG. I much prefer to be writing code than promoting/marketing the app. Please stay safe! ~Danny

This release is about bug fixes and setting things up to test the next new game! Spanish 21 Blackjack (BUG): Many thanks to Bobby for reaching out to let me know that if the Player tried to Re-Double Down during the hand but had an insufficient bankroll, the game would freeze up. For now, the simple fix was to check the bankroll before offering the option to "Re-Double". This means that in Spanish 21, you will not have the option to dig in your wallet or run to the Chip Store to get additional chips in the middle of a hand. I'm working on a more elegant fix, but I wanted to get this out so the game could be re-enabled. Thanks a lot for your help, Bobby! It wasn't an easy bug to reproduce and all of your help via "Send Feedback" was invaluable. Face Up Blackjack (BUG): Another bug fixed as a result of a Player reaching out via "Send Feedback". DJ correctly pointed out that it makes a lot more sense to always display the Dealer Hand Total for Face Up Blackjack because, as the name implies, the cards can be seen! DOH! That was a bit of a no-brainer, DJ! I really appreciate you calling it out. It was actually more challenging to implement because of a feature that was added recently to "always hide" the hand values. Also, it's not a State secret that the animation timing in the Blackjack games needs some serious attention. That's also in the backlog, but it will be a while. After Craps, Blackjack is the next largest "beast" and I'm just not ready to take a scalpel to it! Appreciate the assist, DJ! Chip Store (BUG): In addition to the game bug fixes, I believe that I've addressed an issue that was causing RBG to crash if a Chip Store purchase failed. I'm sure those situations caused some anxiety for people who experienced them, but I assure you that you were not charged for the transaction. The issue solely occurred because I was not properly handling the error message. If you haven't already, please take the time to post a review in the App Store. There are a couple of clowns who are going out of their way to regularly re-post some bad reviews with false claims about the app. I can only guess that they are developers (or friends of developers) who are intimidated by RBG and honestly believe that such childish antics are going to hurt the app. What they fail to realize is that Riverboat Gambler is a collaboration between me and an amazing Player Community and I'm pretty sure there are more of us than there are of them! Another new game is scheduled for the next release! It was requested by Dylan and it's awesome! I love it and I'm excited to release it! It's going through some beta testing right now. As always, thank you for your support and please stay safe! ~Danny

I'm not going to lie - this release will have me on "pins & needles" until it proves to be successful. In the last release, I had to perform some minor surgery on the Chip Store to address an issue that Alex reported. While I was triaging that issue, I came across some things in the code that I think may have been contributing to another, random, rare error. More about that, later. The whole concept of implementing the Chip Store was difficult for me when I first added the feature. TBH, I really only added the Chip Store because I wanted to understand what was involved in supporting "In-App Purchases". Back then, I never envisioned anyone besides myself and a couple of friends and family members downloading RBG. It wasn't easy. Because I was a newbie IOS developer, the programming patterns were foreign to me. Now, as my experience with the IOS platforms has grown and my skills have matured, I feel much more comfortable. Still, one thing I don't want to ever see is a mistake that would impact a Player's attempt to support my work by purchasing chips. Primarily, because I would feel awful if that happened and, secondarily, because I think there are some folks who have an inherent mistrust of apps. For that reason, touching that code creates a bit of anxiety. For some of the chip packages in the store, there is an optional "add-on" offer that is available after an initial purchase is completed. The add-on offer allows a Player to purchase the same about of chips at basically 50% of the initial price. Periodically, folks have reached out because their attempt to make the secondary purchase has failed. When this happens, they receive a very generic error message indicating the transaction failed and asking them to send me a screenshot of the error. Unfortunately, the error message is so generic that it hasn't allowed me to isolate the problem. It's important to note, that nobody ends up charged for the failed transaction. So, while the message has been useless in helping me to triage, it at least provides me the opportunity to assuage concerns. This is what I think I've discovered and what I'm addressing in this release: I think I've been processing the successful transactions too quickly and showing the add-on offers prematurely! Doh! In this release, I've streamlined the process that communicates with Apple for purchase transactions and I think I’ve mitigated the danger of generating an error because the original transaction is still technically processing when the add-on purchase transaction is started. I also discovered that there were error conditions that had been introduced since my implementation that I was not supporting. This could explain why the generic error message was being used as a default. Lastly, I realized that the screen that I use to display the error was potentially truncating the error message instead of allowing it to wrap. This last "issue" was simply caused by my inexperience when that screen was created 7+ years ago. So, there you have it. Hopefully, I didn't break anything. I will be keeping an extremely close eye on this release and exhaustively testing it in Production by buying a lot of chips! Please let me know if you experience any issues and, as always, thank you for your continued support! There are a couple of really cool games in the queue that were requested by Players and I'm looking forward to adding them to RBG! Be safe! ~Danny

Minor release to deal with some issues related to the Chip Store. I'm not 100% clear on the issue, so this is a bit of a "Hail Mary'. I intend to continue to drill deeper into the issues. Many thanks to Alex, for alerting me to the problems. I will continue to follow up on the issues until they are completely resolved. Please reach out using "Send Feedback" if you experience any problems with the Chip Store. ~Danny

Minor release to deal with some issues related to the Chip Store. I'm not 100% clear on the issue, so this is a bit of a "Hail Mary'. I intend to continue to drill deeper into the issues. Many thanks to Alex, for alerting me to the problems. I will continue to follow up on the issues until they are completely resolved. Please reach out using "Send Feedback" if you experience any problems with the Chip Store. ~Danny

A tremendous amount of work went into this release and I want to call out the Player Community for its help. In response to a series of reviews that questioned the randomness of the dice values, I decided to introduce an alternate way of generating random values between 1 and 6. Then, I solicited volunteers to evaluate the new approach. I'm not going to dive into the beta test or the results in these release notes. There's just not enough space. For more detailed information and some screenshots of some of the results (over time), please visit the support site: TheRiverboatGambler.com. Simply look for Craps or Crapless Craps in the games list and then from the "About Page" for either of those games, click on "Dice Randomization". As a result of the test I decided to retain the legacy approach that has been in RBG since about 2019 AND to add a second approach to generating random numbers. Now, the Player has the option to select between the two routines in Preferences. Simply scroll down the Preferences page and make your choice. I made this decision because it seemed wasteful to throw out the old code that was more than adequate when I could simply enhance the app by adding a second option. By default, RBG will use the new approach because, unlike the legacy routine, I have shared "the receipts" on the page I mentioned earlier. Additionally, when the app is first opened, the current histogram data will be cleared so that everyone is starting from a new baseline. The histogram is available from the game menu under "Roll History". Simply tap the chart image in the upper left corner of that screen. I want to thank everyone who participated in this test. Thank you for your assistance, your comments, your time, your feedback, and the screenshots of your histogram as the testing was underway. Riverboat Gambler truly is a wonderful collaboration with a great Player Community and I appreciate you more than you know! Now that this has been completed, I plan to get back to enhancing RBG and adding additional cool features. There is so much I want to do and the list of requests only continues to grow. Please help to spread the word by sharing RBG with your friends, family, and casino buddies. Also, if you haven't already, please consider leaving a review in the App Store. Stay safe! ~Danny

There have been a couple of reports of Craps causing the app to suddenly crash. I want to give a huge shout-out to Jerry for initially alerting me and then providing a lot of background information. I have limited information in the crash logs about the situation, so I'm speculating the cause is related to the ads that get shown after every 85 hands. If it happens to you, please consider using "Send Feedback" to provide me with any information or observations you may have. For the time being, I've updated the libraries that are used to support ads. It's a bit of a "Hail Mary" given nothing has changed in Craps for a very long time. Of course, I will continue to try to reproduce the issue so I can accurately identify the root cause and feel better about closing the bug report. Bug Fixes and Enhancements: 1. Double Down Madness (BUG): Many thanks to Aaron for reaching out using "Send Feedback" and correctly pointing out that, if the Player places an optional "Push 22" wager, the Dealer should complete his hand if the Player busts. 2. Craps (ENHANCEMENT): I've added an alternate method of randomizing the dice values. While I am confident the current algorithm is fair, there have been several complaints and, worse, accusations that I am "rigging" the dice. I do my best to remain "thick skinned" when it comes to constructive criticism, but I have to be honest that it really irritates me when folks post bogus statistics and accusing me of cheating the Player Community. Those who have been with me for any length of time can attest to the fact that I am quite proud of the collaborative relationship I have built with the Riverboat Gambler Player Community. That, and I am always willing to go "above and beyond" to address issues and suggestions. In this release, 80+ volunteer beta testers will play Craps using an alternate random number generator to determine the dice rolls. For more details, please refer to https://theriverboatgambler.com/about-games/how-to-play-craps-dice-beta.html on the support site. You can also find this link on the "About Craps" and "About Crapless Craps" pages of the support site. And, to the "fake Craps statisticians": when you post that there are "too many 7s (the most commonly rolled number on two six-sided dice) and claim you rolled ten 7s in a row, remember that, unless you're playing on "The Darkside", that means you won at least 9 times out of 10 from the Pass Line. That means those dice you believe are "rigged" are paying out for you - LOL. More games and enhancements are coming! Please keep sending me your suggestions and requests and keep sharing Riverboat Gambler with your friends. You, the Player Community, are my best form of advertising. Please stay safe! ~Danny

I'm trying to isolate the cause of a bug that causes the app to crash for some folks as soon as Riverboat Gambler is launched. I cannot reproduce the bug and I have no information in my logs. I suspect the issue is being caused by an external library that is used for showing ads or logging. At this point, all I can do is slowly revert some of those libraries. Please be patient with me as there may be a slew of updates coming. It's frustrating for me, too. I would much rather be working on some of the cool enhancements I have planned, but ensuring stability is critical. I appreciate your support and your patience! Please be safe! ~Danny