Difference between revisions of "Chain of Impending Doom"
(Undo revision 26908 by S.H.I.E.L.D (talk)) |
m (Fixed one of the name links.) |
||
| (13 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | http://gametechmods.com/../uploads/images/98894COID.jpg | |
| + | |||
| + | Chain of Impending Doom was a [[SHW]] [[Shell spinner]] entered in [[Clash Cubes]] 2, and widely considered as the [[SFTW]] of the tournament. It might probably the worst SHW shell spinner ever that has ever been revealed to public. | ||
| + | |||
| + | This bot was made by [[Life robot arena2]]. | ||
| + | |||
| + | It weighed only 1092.1, well under the weight limit for the tournament. | ||
| + | |||
| + | The shell spinner is powered by a single perm motor which is more than unsufficient in the Super Heavyweight class (it's not even enough on a HW). This also caused the outer shell to never be able to reach full speed resulting to the bot moving in ever decreasing circles. | ||
| + | |||
| + | With a scattered assortment of random weapons (most of which are really heavy) including a large abundance of Vlad Spikes on one side and even a few random weapons inside the shell, the community was sure this "bot" would lose. | ||
| + | |||
| + | After losing in the Wild Card Bracket of [[Clash Cubes#Clash Cubes 2|Clash Cubes 2]], [[Life robot arena2]] blamed his loss on poor AIing by [[JoeBlo]]. [[JoeBlo]] then organized 3 grudge matches using COID; One against Viper89 and the other with [[TakatsukiYayoi]] which COID lost to both. The final match was revealed to be against none other then Cube From The West. In a hilarious outcome, COID... LOST by immobilization. | ||
| + | |||
| + | If you bother to download the LRA2 bot pack you will see that the COID included is just a heavyweight, even though that is not the one LRA2 entered in Clash Cubes 2. | ||
| + | [[Category:Bots in DSL]] | ||
| + | |||
| + | A rebuild of Chain of Impending Doom built by [[090901]] was entered into the Lightweight division of [[RoboGames]]. When it lost its first match against [[Swarf 2.0]], due to COID turning itself over for being too unstable on one side. Then lost its second match against [[Robotussin']] after the later flipped COID over without COID becoming unstable. | ||
Latest revision as of 04:54, 11 October 2017
http://gametechmods.com/../uploads/images/98894COID.jpg
Chain of Impending Doom was a SHW Shell spinner entered in Clash Cubes 2, and widely considered as the SFTW of the tournament. It might probably the worst SHW shell spinner ever that has ever been revealed to public.
This bot was made by Life robot arena2.
It weighed only 1092.1, well under the weight limit for the tournament.
The shell spinner is powered by a single perm motor which is more than unsufficient in the Super Heavyweight class (it's not even enough on a HW). This also caused the outer shell to never be able to reach full speed resulting to the bot moving in ever decreasing circles.
With a scattered assortment of random weapons (most of which are really heavy) including a large abundance of Vlad Spikes on one side and even a few random weapons inside the shell, the community was sure this "bot" would lose.
After losing in the Wild Card Bracket of Clash Cubes 2, Life robot arena2 blamed his loss on poor AIing by JoeBlo. JoeBlo then organized 3 grudge matches using COID; One against Viper89 and the other with TakatsukiYayoi which COID lost to both. The final match was revealed to be against none other then Cube From The West. In a hilarious outcome, COID... LOST by immobilization.
If you bother to download the LRA2 bot pack you will see that the COID included is just a heavyweight, even though that is not the one LRA2 entered in Clash Cubes 2.
A rebuild of Chain of Impending Doom built by 090901 was entered into the Lightweight division of RoboGames. When it lost its first match against Swarf 2.0, due to COID turning itself over for being too unstable on one side. Then lost its second match against Robotussin' after the later flipped COID over without COID becoming unstable.