Starting position bug ?

[Foutsie]

Can somebody PLEASE explain the logic behind the starting positions?

I use the "fixed" positions but it's not very intuitive.
Use this example of playing an 8-player map with 6 people:
Starting positions 1-4 at top...5-8 at bottom
We fill spots 1-3 with team 1 then set pos. 4 to "closed"
We then fill spots 5-7 with team 2 and pos. 8 to "closed"

Even after all this, one of team 2 will most likely be in pos. 4.
This causes horrible problems for balancing.

Same thing happens with any map where number of players is not at maximum or players don't fill spots in order.

This could be an EASY fix for Relic. Just have a drop list for your starting position. It's ridiculous

Is there a work-around that I'm missing?

:fight:

[KretNuts]

That's because the game doesn't directly associate player/AI slots and map starting locations. When using fixed positions the game will try to fill in starting points that in theory should be left empty. Like in your example, you closed slot 4, but the game would place player 5 onto that starting position to fill the gap, then player 6 would fill position 5 and 7 would fill 6, then 7 and 8 would be left empty.

For now, the only solutions is via custom maps where you define how many starting positions there is and where do they start.

[ÜberJumper]

People have complained about this one for a while. Don't know why Relic's not fixed it.

[Foutsie]

I put it into the patch suggestions.
I would hope everyone agrees on this so maybe others will mention it.