Thread history
Time | User | Activity | Comment |
---|---|---|---|
No results |
It will be cool to see DrussGT #1 in GigaRumble be threatened as we kick BulletShielding-susceptible bots off from the top30 :P
There are 4 bots vulnerable to BulletShielding present: Phoenix (#16), Chalk (#21), CassiusClay (#22) and Seraphim (#27). They earn their presence as they kick a lot of butts. But you are right, DrussGT only clings on the first place due to its Bullet Shielding. Diamond on the other hand does not use it.
Yeah, sure they do, but these are bots we can probably assume that won't receive new updates, so they will be BulletShielding-susceptible forever and, let's be honest, they will eventually be kicked off from top30. Maybe it will take very long, but they will. And of course, they will be kicked from top30 in part because of the legacy they left behind :P
And just to clarify, I would love to be wrong about those bots not receiving updates :P
To effectively BS, you have to shoot the other bullet out of the air. So you have to exactly know where the other shoots. If the enemy moves, it will aim directly at you, but fires the next tick. Or maybe they compensate, but still they will not fire from the exact place they interpolate. Some bots just spin their radar and shoot whenever they see someone. Only good bots will fire really exact, and only they will be vulnerable to BS. When BulletCatcher came around in 2009, the actively developed bots took their countermeasures. Only a slight deviation from the 'ideal' angle is enough to let a BS miss. DrussGT tries to shield against a few different firingmethods, before it decides to fall back to its native gun and movement.