SDK does not support per-bet-mode wincap values - uses global config.wincap instead of BetMode.max_win

[sureshreddy-aimlabs]

When a game defines multiple bet modes with different max_win values (e.g., base mode with 5000x and superbonus with 25000x), the SDK incorrectly uses the global config.wincap value for all modes instead of the bet mode's specific max_win.

[sureshreddy-aimlabs]

While a game-level override can serve as a temporary mitigation, we would request that this be addressed within the SDK to ensure correct and consistent behavior across all games.

At present, the SDK applies the global config.wincap to all bet modes, instead of respecting the active mode’s BetMode.max_win. This leads to incorrect outcomes for games that intentionally define different max_win values per mode (e.g., base 5000x vs. superbonus 25000x).

Could the SDK be updated to derive and enforce the win cap from the selected bet mode’s max_win rather than relying on the global config.wincap? If you’re agreeable, we’d be happy to submit a pull request with the fix.

[DecJA]

Hi Suresh,

Good call - I'm in the process of pushing a few updates to this repo at the moment so have just included this:
#88

Changes to the setup are minimal and have been applied to all sample games. '0_0_expwilds' as an example of using different max-wins for different game modes.

Let me know if this solves the problem, or if you have any other additions feel free to make a PR.
At the moment, the config value is over-ridden early on in the 'create_books' function using the value passed to that specific mode.

Thanks