Allow 3-5 ants per team

[saphiooo]

Allowing for increased flexibility in the number of ants per team, with more developed error handling for cases where (1) north and south teams don't have the same number of ants, and (2) there are too few or too many ants in a team.

Updated the docs accordingly.

[Grace-H]

The section above the divider is for setup code that is modified before running the simulation--should the exceptions be further down below "Begin Game" with the other class definitions?

[saphiooo]

yes - sounds good! I'll place them below the other class definitions.

[Grace-H]

I like that the game better handles varying team sizes.

It seems like ANTS_COUNT, NORTH_SYMS, and SOUTH_SYMS are now varying parameters and not constants, so I think it could be good design to merge this code into the game configuration functions. What do you think about refactoring to move this logic into generate_game_config and adding these three variables to the config dictionary?

Alternatively, NORTH_SYMS and SOUTH_SYMS could be constant lists of length 5 but at opposite ends of the alphabet, so that certain letters (like E) are always on the same team. Then, a config key 'ants_count' would tell you how much of each list to use

[saphiooo]

Refactoring the logic sounds good. I'm more hesitant about having SOUTH_SYMS start from the end of the alphabet, as the indicator for the south anthill is already X, but NORTH_SYMS and SOUTH_SYMS could be the constant lists of ['A', 'B', 'C', 'D', 'E'] and ['F', 'G', 'H', 'I', 'J'] respectively instead.

[Grace-H]

Good point about the anthill symbol

[saphiooo]

It seems odd to prompt teams for the number of ants in their team every game, if teams for the entire Antcode project are set in stone. However, I left some relevant code that does use this approach at the end of the generate_game_config() function.

3+ ants colliding previously resulted in the program breaking due to referencing a nonexistent ant symbol. A future update will optimize the communication surrounding the collision ("Ants F, G, and H collided" as opposed to "Ants F and G collided / Ants F and H collided / Ants G and H collided").

[saphiooo]

There appears to be a rare edge case scenario where 3 ants colliding can result in another AttributeError due to the way proposed_moves was changed. Planning to update soon with some refactoring that should fix the issue.