It's built on the exact same concepts as Teancum's gun. There's the mod fix I mentioned, a round-by-round storing mechanism, some tweaking on the order of computation (I think it's more correct now), I did 10 rounds of data saving to just get that extra 1% on the /PMCIndex? (I took it out of the dev version of Teancum, because he just couldn't save enough data to make it worth it), but it's still the same pattern-matcher. It still finds patterns in an opponent's movement relative to itself, so it takes it a little longer to get PatternBot, who is completely oblivious to him. He can be somewhat inaccurate if he's never seen the movement from a similar angle before. However he can still score up to a 94% hit rate (95%+ maybe if he has saved data) against PatternBot over 100 rounds. I played with some things to hit PatternBot in the beginning better, but nothing was overly effective, so I scrapped it. The dev version has a bi-directional pattern-matcher, which I took out in this version. The purpose of the bi-directional pattern-matcher was to be able to see if I recognized a pattern that was exactly opposite (negative) of the pattern I'm searching for in regards to LateralVeloctiy? (but the same in AdvancingVelocity). It didn't really help against PatternBot specifically, though, and I probably mis-identified a few patterns with it, too. And it took some overhead to do. The dev version also handles projection into a wall by firing a faster bullet that would be timed to hit my opponent as he hit the wall (for lack of knowledge of what he would do next). In this version, I just broke out of the loop and didn't adjust bullet power. This version is also the king of skipping turns, partially because of the length of patterns I try to match (of course, it's only up to 50). It also uses FloodHT's radar instead of Teancum's real radar. Still interpolates missed scans the same way.
Things that will propagate into the real Teancum:
Things that I probably won't put into the next release of Teancum:
Can you explain how you implemented this? Maybe it can help me or trigger a new approach. thanks -- Loki
Pez, thanks for your suggestion. If i can't solve my problem, maybe i will try a similar approach of storing all info at a certain tick in one object. The advantage is that all related data is always in the same object, the disadvantage is that i can rewrite my pattern matching code and still don't understand what i did wrong... ;-) --Loki