Player Settings

1. Introduction

The Player Settings panel is divided into two sections — one for the Out of Position (OOP) player and one for the In Position (IP) player.
Both must be configured before solving.

Each panel allows you to:

• Set each player’s range
• Define bet and raise sizes for each street (flop, turn, and river)
• Optionally enable an all-in action for each street

---

2. What Does Each Setting Do?

Player Ranges Required

Both the OOP and IP players require a range to be set.
A player’s range represents all the hands that player can hold.
Each hand in the range has an associated weight, which determines how often that hand is played.

You can set the selected weight using the slider at the top of the range selector, then click on a hand to assign that weight.

• Selecting hands: Click individual hands or click and drag to apply weights across multiple hands.
• Removing hands: Click individual hands or click and drag.
• Adjusting weights: Move the top slider and click again to modify probabilities.

If you want to generate a quick range that includes only the top X% of all hands, use the bottom slider to select a percentage range.
The order of hands follows the Sklansky–Karlson model.

---

Bets & Raises Required

Perhaps the most important settings when building a game tree are the bet and raise options.
Each player panel (OOP and IP) lets you configure these for every street (flop, turn, and river).

Each playable street requires at least one bet and one raise.

• Bets occur when no prior action has taken place on that street.
• Raises occur after an opponent has already bet.
• Bets or raises set to 0 are ignored.

Both are entered as percentages, though their meanings differ slightly.

---

Bet Percentages Required

Bet percentages are based on the current pot.

• Example: A 50% bet with a pot of 100 results in a bet of 50.

Formulas:
Bet Amount = Current Pot * Bet Percent
Bet Percent = Bet Amount / Current Pot

---

Raise Percentages Required

Raise percentages are slightly more complex, but follow a consistent logic:

Formulas:
Raise Amount = Raise Percent * (2 * Last Bet + Pot) + Last Bet
Raise Percent = (Raise Amount - Last Bet) / (2 * Last Bet + Pot)

To calculate manually:

---

All-Ins Optional

Each street includes an All-In toggle.
When enabled, this adds an all-in action whenever a player can act (betting or raising).

Despite appearances, this does not significantly increase game tree size, because an all-in terminates further action on that hand.
In practice, adding an all-in is almost “free” in terms of computational cost — so we recommend keeping it enabled.

---

Copy OOP Toggle Optional

The IP player panel includes a Copy OOP toggle that mirrors the OOP player’s bet and raise sizes.
This is useful when you want both players to use identical betting structures.

🔹 Note: This copies only bets and raises, not player ranges.

---

3. Common Questions

What Bet Sizes Should I Use?

Keep the number of bet sizes as small as possible while still representing key parts of the full game.

For example:
If you only choose 5%, 10%, and 15%, these all represent small bets — missing important larger options.
Instead, consider using 25%, 50%, and 100%, or even a single 50% bet — this provides a more balanced abstraction.

---

Why Shouldn’t I Set Too Many Bet Sizes?

Modern solvers use bet size abstraction — limiting the number of available sizes to control tree growth.
Even with a small number of bet sizes, trees can require tens of gigabytes of RAM.

Using too many sizes can make the tree unsolvable on most consumer systems.

---

Can I Use More Bet Sizes for River or Turn Solves?

Yes — single-street solves (like river or turn-only spots) allow for more bet sizes because fewer cards remain to be dealt, as such the game tree doesn't grow as much.

• River: No cards left to draw → tree growth is minimal.
• Turn: Only one card left → manageable tree size.

However, this does not apply to turn and river settings within a flop solve — only when solving those streets independently.

💡 Pro Tip: After adding bet sizes, click Estimate Tree Size to see real-time RAM usage.

---

4. Decreasing Tree Size Tips

• 📝 Decrease SPR: Lower the stack-to-pot ratio. Smaller stacks mean fewer betting rounds.
• 🧠 Simplify Your Tree: Remove low-frequency or unrealistic actions.
• ⚙️ Merging Threshold: Combine similar bet sizes.
• 💾 All-In Threshold: Replace large bets with all-ins to reduce depth.
• 🔍 Max Actions: Limit consecutive bets before forcing all-ins.

---

Need Help?

If you encounter any issues while setting up your game:

• 📧 Email: [email protected]
• 📝 Contact Form
• 📚 FAQ Section