Start with league_meta. The game engine uses the version key to decide which parser to load. Always set version to "2.0" or higher to trigger the "new" feature set.
A comprehensive JSON configuration for a new cricket league should be divided into logical sections. Below is an illustrative example, followed by an explanation of each critical component. game configurationjson cricket league file new
"league_meta":
"name": "Global T20 Champions League",
"season": 1,
"start_date": "2026-05-15",
"end_date": "2026-06-30",
"number_of_teams": 8
,
"match_rules":
"overs_per_innings": 20,
"max_overs_per_bowler": 4,
"powerplay_overs": [1, 6],
"fielding_restrictions":
"powerplay_outsiders": 2,
"non_powerplay_outsiders": 5
,
"decision_review_system": true,
"reviews_per_team": 2,
"tiebreaker": "super_over"
,
"points_system":
"win": 2,
"tie": 1,
"loss": 0,
"abandoned": 1,
"bonus_run_rate_threshold": 1.25,
"bonus_points": 1
,
"tournament_structure":
"group_stage":
"rounds": "double",
"number_of_matches_per_team": 14
,
"playoffs":
"type": "ipl_style",
"qualifier1": "1_vs_2",
"eliminator": "3_vs_4",
"qualifier2": "loser_qualifier1_vs_winner_eliminator",
"final": "winner_qualifier1_vs_winner_qualifier2"
,
"gameplay_params":
"wicket_degradation": true,
"dew_factor": 0.3,
"injury_probability": 0.05,
"default_pitch_type": "balanced",
"dynamic_weather": true
A standard Cricket League configuration file is typically organized into logical parent objects. Below is an analysis of the key sections. Start with league_meta
If you have been using an older configuration file (perhaps from a game version released before 2023), you are missing out on critical features. Here is what the new configuration JSON offers: A standard Cricket League configuration file is typically