PentagonWarSimulator
Precision Conflict Modeling via Phase-Separation Logic and Chess-Engine Strategy.
Detailed guide • Recommended defaults • Mobile-friendly

Parameter Guide

This page explains what each control does, what to start with, and when to change it. If you are new: keep defaults, then adjust one parameter at a time.

Back to Home

Core scenario controls

Blue coalition i

Recommended: 1–6 countries Default: scenario list

Pick the countries you want to model as Blue. More members usually means more depth, logistics, and complexity.

  • Start small (1–3) to understand the mechanics.
  • Add allies when you want coalition effects.

Red coalition i

Recommended: 1–6 countries Default: scenario list

Pick the opposing coalition. Large coalitions can increase compute time and widen uncertainty bands.

  • If you want a clearer outcome, avoid overly symmetric matchups at first.

Battleground / Theater i

Recommended: pick the real focal region Default: scenario battleground

The theater is the “map anchor” for the run. Geography influences operational reach, supply realism, and domain emphasis.

  • Naval-heavy theaters increase sea weighting.
  • Landlocked theaters shift weight to land/air.

Year i

Recommended: latest available Default: current dataset year

Changing the year changes baseline capability inputs. Use it to explore “near-future” vs “current” balance.

  • Keep year fixed when comparing strategies.

Intensity i

Recommended: Medium Default: Medium

Intensity is the master “tempo knob.” If outcomes feel too slow or too explosive, adjust intensity first.

  • Higher intensity usually reduces “draw” probability (decisions happen faster).

Max days i

Recommended: 60–120 Default: 60

A longer horizon lets the simulation “breathe.” A short horizon makes it harder to separate evenly matched sides.

  • Use 60 for fast tests, 120 for more realism.

Monte Carlo controls

MC iterations i

Recommended: 400–1200 Default: 600

Iterations control statistical stability. If your probabilities jump around, increase iterations.

  • Mobile: 200–400
  • Desktop: 600–1200

Seed i

Recommended: fixed when comparing Default: auto

Use a fixed seed for fair comparisons. Use random seed for exploratory browsing.

Outcome probabilities i

Recommended: interpret as uncertainty Default: shown after run

A 60/30/10 split is a strong edge. A 40/39/21 split is uncertain and will look more mixed in the phase separation.

Phase separation clarity i

Recommended: trust the edge Default: automatic

When the edge is strong and draw risk is low, you’ll see cleaner “oil-water” separation. Otherwise it stays partially mixed.

Chess decision layer controls

Duel plies i

Recommended: 96–136 Default: 96

Plies are the length of the duel story. Think of it as “how many chess beats occur during the simulation timeline.”

Duel depth i

Recommended: 2 Default: 2

Use depth 2 as your default. Use depth 3 when you want the cleanest decisions and your device can handle it.

Simulation speed i

Recommended: 0.55–0.75 Default: 0.65

If the duel feels jumpy, slow it down. If you want fast demo runs, speed it up.

MC–Chess relationship i

Recommended: MC dominant Default: MC dominant

Chess follows the evolving uncertainty. When the MC edge is small, the duel can look tactical and volatile.

Core model selection

Cinematic i

Use when: you want speed Default: available

Cinematic emphasizes a coherent storyline and quick feedback. Losses are easier to interpret but less granular.

Dense i

Use when: sensitivity testing Default: available

Dense introduces more knobs and internal multipliers. It can be more expressive, but needs careful parameter control.

Integrated i

Recommended: for realism Default: available

Integrated is your “serious mode.” It’s slower, but it makes the geo + operational constraints matter more.

  • If results feel too deterministic, increase MC iterations instead of changing many knobs.

User data input i

Status: Coming soon Default: disabled

You’ll be able to bring your own country metrics and run the same engine against your custom assumptions.

Disclaimer

PentagonWarSimulator is an independent simulation/game project. It is not affiliated with the U.S. Department of Defense, the Pentagon, or any government agency. This website and simulator are for research-style exploration, education, and entertainment.