Difference between revisions of "Challenge: Shotclocks"

From Gladiabots Wiki
Jump to: navigation, search
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
The challenge is as follows: create a shotclock for counting your own shots. You can count shots exactly, or roughly; you can count them for a single bot class or for all botclasses, the freedom is yours! The most compact, clever, innovative or complete AIs will be featured on this page.
 
The challenge is as follows: create a shotclock for counting your own shots. You can count shots exactly, or roughly; you can count them for a single bot class or for all botclasses, the freedom is yours! The most compact, clever, innovative or complete AIs will be featured on this page.
  
== History ==
+
== The Simple Shotclock ==
  
The Discord has a long history of making shotclocks. The first shotclock that was widely used was developed by Bockwurst, after a binary counter design by Mahrgell and Gilberreke (the game didn't have counters built in at that point). Here's the video that shows it off, for historic purposes (there were changes to the game that make this video largely obsolete now).
+
''Read this first: [[Fire Sustain Guide]]''
  
<youtube>fmdFmiCIaFI</youtube>
+
If you want to make the simplest shotclock there is, you can simply make sure that no shoot nodes are allowed to retarget. Put these in front of your attack module and you'll get a serviceable shotclock. They use the simplified model where Assault shoots for 5, Shotgun shoots for 5, Sniper shoots for 13 and Machine Gun shoots for 38. These timings tend to be "close enough" for most real-world AIs.
  
6 months later, with counters now available, the community set out to make the "perfect shotclock". The effort was spearheaded by Sckuzzle, Gilberreke, ThordanSsoa and many others. The result was the following compact counter:
+
[[File:Shotclock-simple.png|thumb|none]]
  
[[File:Shotclock-gilberreke.png|thumb|none|Compact Counter - Gilberreke's variation]]
+
== Refining ==
  
Skip forward another 6 months or so and Rainin, the best player at the time, made a video about shotcounters, showing off yet another design. This counter seems to be mostly independent, but ends up looking fairly similar.
+
Here's a quick tutorial showing you how to move from [[Fire Sustain Guide|simple sustain]] to more complicated shotclocks.
  
<youtube>Y0cavcMcNK0</youtube>
+
[[File:Shotclock Tutorial.png|thumb|none]]
  
 
== Challenge Submissions ==
 
== Challenge Submissions ==
Line 22: Line 22:
 
File:Shotclock-pege-binary.png|Pege's Binary Shotclock<br>Uses GameAg's binary counter
 
File:Shotclock-pege-binary.png|Pege's Binary Shotclock<br>Uses GameAg's binary counter
 
File:Shotclock-gilberreke-milliseconds.png|Shotclock in milliseconds by Gilberreke
 
File:Shotclock-gilberreke-milliseconds.png|Shotclock in milliseconds by Gilberreke
 +
File:Shotclock-butanium.png|Butanium's millisecond shotclock
 +
File:Shotclock-vvyovx.png|Ally shotclock relying solely on a cache counter and four tags converted to binary for ease of use by vvyovx
 
</gallery>
 
</gallery>
 +
 +
== History ==
 +
 +
The Discord has a long history of making shotclocks. The first shotclock that was widely used was developed by Bockwurst, after a binary counter design by liq3, Bockwurst and Gilberreke (the game didn't have counters built in at that point). Here's the video that shows it off, for historic purposes (there were changes to the game that make this video largely obsolete now).
 +
 +
<youtube>fmdFmiCIaFI</youtube>
 +
 +
6 months later, with counters now available, the community set out to make the "perfect shotclock". The effort was spearheaded by Sckuzzle, Gilberreke, ThordanSsoa and many others. The result was the following compact counter:
 +
 +
[[File:Shotclock-gilberreke.png|thumb|none|Compact Counter - Gilberreke's variation]]
 +
 +
Skip forward another 6 months or so and Rainin, the best player at the time, made a video about shotcounters, showing off yet another design. This counter seems to be mostly independent, but ends up looking fairly similar.
 +
 +
<youtube>Y0cavcMcNK0</youtube>

Revision as of 00:03, 1 November 2020

The challenge is as follows: create a shotclock for counting your own shots. You can count shots exactly, or roughly; you can count them for a single bot class or for all botclasses, the freedom is yours! The most compact, clever, innovative or complete AIs will be featured on this page.

The Simple Shotclock

Read this first: Fire Sustain Guide

If you want to make the simplest shotclock there is, you can simply make sure that no shoot nodes are allowed to retarget. Put these in front of your attack module and you'll get a serviceable shotclock. They use the simplified model where Assault shoots for 5, Shotgun shoots for 5, Sniper shoots for 13 and Machine Gun shoots for 38. These timings tend to be "close enough" for most real-world AIs.

Shotclock-simple.png

Refining

Here's a quick tutorial showing you how to move from simple sustain to more complicated shotclocks.

Shotclock Tutorial.png

Challenge Submissions

Note that these submissions were accepted as is, there might be slight errors, feel free to report them on Discord.

History

The Discord has a long history of making shotclocks. The first shotclock that was widely used was developed by Bockwurst, after a binary counter design by liq3, Bockwurst and Gilberreke (the game didn't have counters built in at that point). Here's the video that shows it off, for historic purposes (there were changes to the game that make this video largely obsolete now).

6 months later, with counters now available, the community set out to make the "perfect shotclock". The effort was spearheaded by Sckuzzle, Gilberreke, ThordanSsoa and many others. The result was the following compact counter:

Compact Counter - Gilberreke's variation

Skip forward another 6 months or so and Rainin, the best player at the time, made a video about shotcounters, showing off yet another design. This counter seems to be mostly independent, but ends up looking fairly similar.