You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a recurring issue with large games (>= 8 human players, >= 8 bots) receiving the following error message inconsistently: "Unable to start game, inconsistent team/ID configuration for player or AI bot"
Typically, this occurred in games in team-preset, auto balancing off, with all human players in one team, all bots in another. Team sizes were either 8vs8 or set manually to greater sizes, e.g., !set teamSize 12.
The error occurred with unbalanced as well as balanced team sizes.
It seems to occur more frequently when using BARbarian AIs, less frequently with SimpleAIs.
!forcestart would not override the inconsistency issue.
We tried adding/removing AIs, balancing out the teams with Inactive or Simple AIs.
Would be good to add more diagnostics or a !set option to switch off the consistency checks.
The text was updated successfully, but these errors were encountered:
Can't start the match, it says something about inconsistent IDs
Sometimes after you set up a match you might be unable to start it with this message: "[teh]cluster1[06] Unable to start game, inconsistent team/ID configuration for player or AI bot"
This usually happens only when you turn off autobalance. Workaround:
type in !balance to fix all IDs and re-set all AIs, or turn autobalance back to advanced and use !preset coop instead, that puts all players into team 1 and AIs into team 2, and ensures that there are no ID conflicts.
We have a recurring issue with large games (>= 8 human players, >= 8 bots) receiving the following error message inconsistently:
"Unable to start game, inconsistent team/ID configuration for player or AI bot"
Typically, this occurred in games in team-preset, auto balancing off, with all human players in one team, all bots in another. Team sizes were either 8vs8 or set manually to greater sizes, e.g., !set teamSize 12.
The error occurred with unbalanced as well as balanced team sizes.
It seems to occur more frequently when using BARbarian AIs, less frequently with SimpleAIs.
!forcestart would not override the inconsistency issue.
We tried adding/removing AIs, balancing out the teams with Inactive or Simple AIs.
Would be good to add more diagnostics or a !set option to switch off the consistency checks.
The text was updated successfully, but these errors were encountered: