Maps
From Gladiabots Wiki
This page is deprecated. Maps are now randomly generated. This is the old map pool for historical reasons. |
Contents
Map pool
The map pool differs for each league and for unranked games in career as well as for sandbox mode:
Map | Bots | Resources | Bronze | Silver | Gold | Platinum | Diamond | Master | Grandmaster | Unranked | Sandbox |
---|---|---|---|---|---|---|---|---|---|---|---|
The seven wonders | 4 vs 4 | 7 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ |
Set your priorities | 5 vs 5 | 5 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |
Meeting point | 6 vs 6 | 5 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ||
Circle of Death | 9 vs 9 | 0 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | |||
Split team | 5 vs 5 | 0 | ✔ | ✔ | ✔ | ✔ | ✔ | ||||
Lake Rushtown (Mcompany) | 5 vs 5 | 11 | ✔ | ✔ | ✔ | ✔ | |||||
Kingmaker (Erik) | 3 vs 3 | 7 | ✔ | ✔ | ✔ | ||||||
Barred Spiral (radyjko8) | 6 vs 6 | 0 | ✔ | ✔ | ✔ | ||||||
Dominance (Revenge) | 3 vs 3 | 3 | ✔ | ✔ | |||||||
Flanking (LuBeNo) | 4 vs 4 | 0 | ✔ | ✔ | |||||||
Mind Game (Sneaky/RC) | 2 vs 2 | 3 | ✔ | ✔ | |||||||
Ambidextrous | 5 vs 5 | 2 | ✔ | ||||||||
Interference | 2 vs 2 | 2 | ✔ | ||||||||
Neighbours Fight | 3 vs 3 | 5 | ✔ | ||||||||
Starving | 3 vs 3 | 1 | ✔ | ||||||||
Twitter mission 1 | 2 vs 2 | 2 | ✔ | ||||||||
Twitter mission 2 | 3 vs 3 | 3 | ✔ | ||||||||
Back to back | 3 vs 3 | 6 | ✔ | ||||||||
1 v 1 | 1 vs 1 | 0 | ✔ | ||||||||
1 v 2 | 1 vs 2 | 0 | ✔ | ||||||||
3 v 3 | 3 vs 3 | 0 | ✔ | ||||||||
4 v 4 | 4 vs 4 | 0 | ✔ | ||||||||
7 v 7 | 7 vs 7 | 0 | ✔ |
Ranked maps
Unranked maps
Sandbox maps
Instantiation order
There exists an instantiation order for the bot starting positions rarely used in the game. The order is shown in the map images above.
It is used in the following places:
- If several bots from the same team try to pick up the same resource the instantiation order defines who takes it. If a bot cannot pick up the resource it idles instead.
- Team tag and team untag actions are evaluated in instantiation order.
- If several entities share identical attributes in the entity selection process of target selectors.
Determining the instantiation order
The program to the right can determine the instantiation order.
- Each bot tries to (exclusive) team tag the tag "A" to itself.
- If a bot is team tagged "A" it waits 3 ticks and then team untags the "A" and goes to idle.
As the result all bots are team tagged "A" in reverse of the instantiation order.