← Latest papers
💻 computer science

Dynamic Resource Allocation for Ensemble Determinization MCTS

This paper proposes and validates two dynamic resource allocation strategies—adjusting the number of determinization trees and nonuniformly distributing simulation budgets—for Ensemble Determinization MCTS, demonstrating statistically significant performance improvements in high-uncertainty board games like Jaipur, Lost Cities, and Splendor.

Original authors: Jakub Kowalski, Adam CięĊkowski, Artur KrzyĊyński, Mark H. M. Winands

Published 2026-07-15
📖 6 min read🧠 Deep dive

Original authors: Jakub Kowalski, Adam CięĊkowski, Artur KrzyĊyński, Mark H. M. Winands

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are trying to solve a massive, chaotic puzzle, but you can't see the whole picture. You only know a few pieces, and the rest are hidden under a foggy blanket. This is what playing a board game like Jaipur, Lost Cities, or Splendor feels like for a computer. There are hidden cards, random shuffles, and secret strategies. To make a good move, the computer uses a brainy trick called Monte Carlo Tree Search (MCTS).

Think of MCTS as a team of explorers. Instead of just one explorer guessing the path, the computer sends out a whole squad. In the version of MCTS used here, called Ensemble Determinization MCTS, the squad splits up. Each explorer imagines a different version of reality where the hidden cards are revealed in a specific way. They all run simulations (mental rehearsals) of the game, and then they vote on the best move.

The big question the authors asked was: How should we manage our team of explorers? Should we send out a fixed number of them every time? Should we give every explorer the exact same amount of time to think?

The paper suggests that the answer is "No, not always." Instead, the computer should be a smart manager that dynamically allocates resources. Here is how they tested two new management styles:

1. The "Flexible Team Size" Strategy

Imagine you are leading a group of detectives. If the clues are very confusing and the suspects look almost identical, you might need more detectives to be sure. But if the clues are crystal clear, maybe you don't need a huge crowd; a smaller team is fine.

The authors proposed a system where the computer changes the number of "explorer trees" (the detectives) on the fly.

  • The Rule: If the team is split and can't agree on a move (the "margin" between the best and second-best move is small), the computer adds more trees to get a clearer picture. If the team is super confident and agrees easily, it reduces the number of trees to save time.
  • The Result: In simulations, this worked wonders for Jaipur and Splendor. For example, in Jaipur, using this flexible team size boosted the win rate by 3.3 percentage points compared to a fixed team. In Splendor, it jumped by 5.1 percentage points.
  • The Catch: It didn't work as well for Lost Cities. In fact, for that game, the results were mixed or even slightly negative. The authors suggest this means the "right" number of detectives depends heavily on the specific game being played.

2. The "Smart Budget" Strategy

Now, imagine you have a total of 250,000 mental simulations (a "budget") to spend on a single turn. The old way was to split this budget equally among all the explorers. If you had 10 explorers, each got 25,000 simulations.

The authors asked: What if we give more time to the explorers who are struggling and less time to the ones who already know the answer?

  • The Rule: They tried several methods to decide who gets more time. One method, called "Across-tree UCB," treated the whole team as a single unit, focusing all the extra time on the moves that were most uncertain across the entire group. Another method, "Move Pruning," stopped wasting time on moves that were clearly bad.
  • The Result: This was a hit-or-miss game. The "Across-tree UCB" method was a star performer when combined with a "voting" system, improving Jaipur and Splendor scores. However, other methods, like trying to balance based on "win rate differences," actually made things worse, dropping scores by over 10 percentage points in some cases.
  • The Lesson: You can't just throw money (or simulations) at a problem. If you give extra time to the wrong explorers, you might confuse the whole team.

The Big Reveal: Don't Just Add It Up

The most interesting finding came when they tried to combine both strategies (changing the team size and the budget). You might think, "If Strategy A adds 3 points and Strategy B adds 2 points, combining them should add 5 points!"

But the computer didn't work like that. In Jaipur, the combined strategies only added 2.9 percentage points, even though the math predicted they should add 6.5. In Splendor, the gain was 2.1 points instead of the predicted 7.3.

The authors explain that these strategies sometimes get in each other's way. It's like having a flexible team size and a smart budget is great, but if you change the team size while you are trying to distribute the budget, the two systems might clash. The paper suggests that you can't just pick the best "size" and the best "budget" separately and expect them to work perfectly together; you have to test them as a package.

What About Time?

Finally, the authors tested these ideas not just by counting simulations, but by giving the computer a strict one-second time limit per turn (like a real game clock).

  • The flexible strategies still helped. In Lost Cities, a smart voting setup climbed from 47.6% to 54.6% wins under the time limit, turning a losing strategy into a winning one.
  • However, the ranking of the best strategies sometimes changed when switching from "count simulations" to "count seconds." This means that a strategy that looks great in a simulation might not be the best choice if you are racing against a clock.

The Bottom Line

The paper doesn't claim to have "solved" these games. Instead, it shows that dynamic resource allocation—being a flexible manager who adjusts the team size and budget based on how confused the team is—can significantly boost performance.

  • For Jaipur and Splendor: Being flexible is a clear win, boosting scores by 3 to 5 percentage points.
  • For Lost Cities: It's tricky; the benefits are smaller and less consistent.
  • The Warning: The paper explicitly rules out the idea that "more trees" or "more simulations" is always better. Sometimes, having a smaller, more focused team or stopping the search early on bad moves is the key to victory.

The authors conclude that while these dynamic tricks are powerful, they are highly dependent on the specific game. What works for Jaipur might fail for Lost Cities, so there is no single "magic setting" that works for every board game. The best approach is to test and tune these strategies for the specific game you are playing.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →