Not Stopping in Time

Jump to navigation Jump to search
Revision as of 19 May 2013 at 08:31.
The highlighted comment was created in this revision.

Not Stopping in Time

I recently tested reading hard-coded SAG lengths from a String table in EpeeistMicro. In theory, it should be more precise, and therefor more effective than Skilgannon's method. The problem is, against bots that aim using linear targeting and fire power 2 bullets, EM doesn't stop in time and gets hit.

I calculated that a 56 pixel length would move for 12 ticks, and would therefor be completely safe against guns that fire power 2's, which take 14 ticks to cool in between shots.

What did I do wrong?

Thanks

    Sheldor (talk)04:51, 19 May 2013

    Hi mate. Sounds like you are to close to the other bot. The closer you are, the less dodge moves you get. For your example you only have 12 ticks at a distance of 168.

      Wompi (talk)06:14, 19 May 2013
       

      There are 3 things I can think of:

      • Range, as Wompi already mentioned, could be a factor.
      • Perception delay, your perception of opponents firing lags 1 or 2 ticks and then the move starts a tick after that, so maybe 2 or w ticks there.
      • Firer inaccuracies. The firer may have a bug (delay as above, firer's movement etc) which causes it for fire slightly differently from what you expect.
        Nz.jdc (talk)09:31, 19 May 2013