Difference between revisions of "Basics"

From Gladiabots Wiki
Jump to: navigation, search
(42 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 +
== Basics ==
 +
 +
''Gladiabots'' is a game between two players: the {{Tooltip|blue|In training and campaign you can only play as the blue side.}} and the {{Tooltip|red|In multiplayer and sandbox you can also play as the red side.}} side. Both players assign bot classes and programs to each bot starting on their team. Once they deploy their setup for a match, it all depends on their robots and the programs to win the match by scoring the most points.
 +
 
== Maps ==
 
== Maps ==
  
[[Image:Map set your priorities.png|thumb|Best score map SET YOUR PRIORITIES]]
+
[[File:Collection mode.png|thumb|Collection mode]]
  
Each map contains one or more bot starting positions for each team. Optionally maps can contain team bases and resources. Normally the same amount of bot starting positions and team bases are used for each team and the map objects have usually [https://en.wikipedia.org/wiki/Reflection_symmetry reflectional] or [https://en.wikipedia.org/wiki/Rotational_symmetry rotational] symmetry. Two starting positions or team bases that are symmetric belong to different teams. There exists an instantiation order for the bot starting positions rarely used in the game[https://forum.gladiabots.com/viewtopic.php?f=7&t=221]. Only a subset of all maps is used for ranked multiplayer.
+
Each map contains several bot spawn points for each team. Maps also contain secondary entities, like resources, bases, force fields or health packs. The maps are procedurally (randomly) generated and have [https://en.wikipedia.org/wiki/Reflection_symmetry reflectional] or [https://en.wikipedia.org/wiki/Rotational_symmetry rotational] symmetry, so the setup is the same for both players, but mirrored. This way, the game is always balanced and fair. Bots are placed in the same order as they appear on the team setup screen.
  
Each map has a size of 50x50 meters. If a bot touches the borders of a map, it will explode. When shooting a bot is able to hit another bot up to a distance of 15 meters. This distance is divided in short range (up to 3 meters), medium range (3 to 8 meters) and long range (8 to 15 meters).
+
Each map has a size of 50x50 meters.
  
 
== Game modes ==
 
== Game modes ==
 +
''Main Page: [[Game modes]]''
  
=== Elimination ===
+
In all three modes, the goal is to score more points than the opponent, but they differ in how you score those points and what extra map features are available.
  
The objective is to destroy more bots from the other team within the time limit. Bots can be destroyed by shooting them until they lost their shield and health or pushing them to the map borders. A game is evaluated as a draw if no team could destroy more bots after the time limit. The shield or health state of bots is not relevant to this objective.
+
=== Collection ===
  
=== Best score ===
+
The objective is to gather more resources than the other team within the time limit. Resources can be gathered by capturing them up and scoring them to an allied base; each resource scores one point. Bots respawn when destroyed in this mode.
  
The objective is to gather more resources than the other team within the time limit. Resources can be gathered by picking them up and moving them to an allied base. A game is evaluated as a draw if no team could gather more resources after the time limit. Neither the shield or health state of bots nor the count of remaining bots is relevant to this objective.
+
=== Domination ===
  
== Bot actions ==
+
The objective is to capture and hold more bases than the other team within the time limit. A base is captured by moving a bot into short range. Points are scored if the enemy does not recapture the base or places a bot within short range. Additional points are scored for every ally within a friendly base. Bots respawn when destroyed in this mode.
  
During each second, there are 4 cycles (or ticks) where the bot decides its next action. Once the bot has decided its action, it will execute this action for the entire duration of the tick. In every tick the bot can decide whether or not to attack an enemy, move towards an object, flee from an object, catch a resource (or pick up a resource), drop a resource, secure a resource (or score a resource), tag an object or even decide to do nothing. Outside of a few edge cases, a bot can detect and use the action another bot or itself was doing in the previous tick to make its decision.
+
=== Elimination ===
  
However, there are some edge cases that doesn't follow the conventional logic of the actions: (whether it is detecting actions or executing them)
+
The objective is to destroy more bots than the other team within the time limit. This mode has the simplest rules, but the hardest execution. A game is evaluated as a draw if no team could destroy more bots than the other team after the time limit. The shield or health state of bots is not relevant to this objective. Destroyed bots do not respawn in this mode.
 
+
* In the very first tick of the game all bots are detected as idling.
+
* If a bot is moving to an object that it can reach within the current tick, it will move there and idle for the rest of the tick. This action will be detected as idling instead of moving.
+
* The closest 2 bots can get to each other is restricted by the collision model. The collision model of a bot is a circle with a radius of ~0.5 meters <code><span style="color:red">GFX47 could you be more precise? Are there differences between SN, SG, AS and MG?</span></code>
+
** If one bot moves to another bot and touches it, it will not push the other bot. It will be detected as idle by other bots.
+
** If one bot tries to pass another bot at a very small distance, the two bots will collide and get pushed away from each other.
+
* If a bot is catching a resource, it will move to that resource until it is within the range where it then picks up the resource and goes into idle. While moving to the resource, it will be detected as moving to the resource. However, on the tick that it picks up the resource, it will be detected as idle unless it picks up the resource at the very end of a tick.
+
* Securing a resource follows similar rules to catching a resource, with the difference being that it moves to the base instead of a resource. Also, a bot will refuse to secure a resource if it doesn't have a resource picked up already.
+
* Both catching and securing a resource can be done ~0.5 meters <code><span style="color:red">GFX47 could you be more precise?</span></code> away from the resource or base.
+
* If two bots from different teams are close enough to pick up the same resource and try to do so, neither one will do so, and they will idle instead.
+
* The actions dropping a resource or tagging an object don't have their own action to detect, and simply are detected as idle.
+
 
+
== Shooting process ==
+
 
+
Although the bot classes have very different shooting behavior, they all share the same shooting process:
+
 
+
# The bot will start aiming for the time of their [[Bot_classes#Shooting_stats|aiming duration]].
+
# They will fire a bullet or group of bullets according to the [[Bot_classes#Shooting_stats|bullet configuration]].
+
#* Each bullet will either hit with the [[Bot_classes#Shooting_stats|attack power]] or miss completely according to the ''precision''.
+
#** The bots <code>precision counter</code> will increment by its precision value. The [[Bot_classes#Shooting_stats|precision value]] is determined by what range the target is in at the moment the bullet is fired. If the target is out of range, the precision value is 0.
+
#** If the <code>precision counter</code> is greater or equal to 100 the bullet will hit and the <code>precision counter</code> will be decremented by 100. Otherwise the bullet will miss.
+
#* If they have another shot to take during the attack cycle, they will then wait for the [[Bot_classes#Shooting_stats|time between shots]] and repeat step 2. The total time spent shooting all bullets is the [[Bot_classes#Shooting_stats|attack duration]].
+
# continue with 1.
+
  
 
== Health, shield and regeneration ==
 
== Health, shield and regeneration ==
  
All bots have a certain amount of [[Bot_classes#Health.2C_shield_and_regeneration|health]] and [[Bot_classes#Health.2C_shield_and_regeneration|shield]]. The shield absorbs damage before you take any damage to your health, and can regenerate after the bot isn't damaged for over 3 seconds. Any damage taken to your health is permanent. A fully destroyed shield regenerates in 3 seconds for any bot.
+
Based on the bot class all bots have a certain amount of [[Bot_classes#Health.2C_shield_and_regeneration|health]] and [[Bot_classes#Health.2C_shield_and_regeneration|shield]]. The shield absorbs damage before you take any damage to your health, and can regenerate after the bot isn't damaged for over 3 seconds. Any damage taken to your health is permanent. A fully destroyed shield regenerates in 3 seconds for any bot.
 
+
== Rough thoughts for shooting process ==
+
 
+
Is there a different precision value used when shooting from mid of short and mid range > no<br>
+
Explain Sniper misses / clarify shooting timing<br>
+
The explanation below cannot be true, because the current implementation has no offset for sniper shooting. Shooting is always at the beginning of a tick.<br>
+
How fast do bullets travel in the air ~50 meters / second<br>
+
Diagrams<br>
+
<br>
+
missed sniper shots although never shoot out range
+
They are caused by the bot checking it's AI 4 times per second, rather than in real time, while the "prep to fire" timer is in real time.
+
 
+
Example: sniper has a valid (retreating, long range) target and is prepping to fire > sniper checks it's AI (last tick before prep timer will be complete) target is still valid (still in long range), prep to fire timer continues > target moves out of range (before shot is fired, and before sniper checks AI on next tick) > prep to fire completes (before sniper checks AI on next tick) shot is fired, accuracy is calculated at 0% because target is out of range > shot misses
+

Revision as of 08:19, 9 July 2020

Basics

Gladiabots is a game between two players: the blue and the red side. Both players assign bot classes and programs to each bot starting on their team. Once they deploy their setup for a match, it all depends on their robots and the programs to win the match by scoring the most points.

Maps

Collection mode

Each map contains several bot spawn points for each team. Maps also contain secondary entities, like resources, bases, force fields or health packs. The maps are procedurally (randomly) generated and have reflectional or rotational symmetry, so the setup is the same for both players, but mirrored. This way, the game is always balanced and fair. Bots are placed in the same order as they appear on the team setup screen.

Each map has a size of 50x50 meters.

Game modes

Main Page: Game modes

In all three modes, the goal is to score more points than the opponent, but they differ in how you score those points and what extra map features are available.

Collection

The objective is to gather more resources than the other team within the time limit. Resources can be gathered by capturing them up and scoring them to an allied base; each resource scores one point. Bots respawn when destroyed in this mode.

Domination

The objective is to capture and hold more bases than the other team within the time limit. A base is captured by moving a bot into short range. Points are scored if the enemy does not recapture the base or places a bot within short range. Additional points are scored for every ally within a friendly base. Bots respawn when destroyed in this mode.

Elimination

The objective is to destroy more bots than the other team within the time limit. This mode has the simplest rules, but the hardest execution. A game is evaluated as a draw if no team could destroy more bots than the other team after the time limit. The shield or health state of bots is not relevant to this objective. Destroyed bots do not respawn in this mode.

Health, shield and regeneration

Based on the bot class all bots have a certain amount of health and shield. The shield absorbs damage before you take any damage to your health, and can regenerate after the bot isn't damaged for over 3 seconds. Any damage taken to your health is permanent. A fully destroyed shield regenerates in 3 seconds for any bot.