Reminds me of what I was working on

Jump to navigation Jump to search
Revision as of 14 June 2021 at 10:27.
The highlighted comment was created in this revision.

Reminds me of what I was working on

As-described this reminds me of what I was working towards back in 2012 or so for a new movement engine that I never quite completed. I'm not quite sure how far BeepBoop is going with it, but what had started on was intended to have extremely comprehensive coverage of all possible non-redundant paths a bot could be maneuvering. Seeing this page here got me looking at my old backup files. I thought I remember talking about it some on the wiki at least in passing but can't find it. The main thing I remember finding tricky was the optimization required to make it not be absurdly slow, while not compromising on the range of movement options available. Maybe I'll pick that back up again some time.

    Rednaxela (talk)05:40, 14 June 2021

    I remember this, you were discussing using a lookup table but running into file size limits.

    I still want to go back to my idea of surfing future waves, so you don't just control how you react, but also proactively you control what the enemy sees at fire-time. This way you could dynamically 'discover' motion patterns like stop-n-go, which force even linear guns to shoot HOT. I'm sure many other classes of guns have similar weaknesses which we can't see...

      Skilgannon (talk)12:27, 14 June 2021