View source for Talk:Phantom

I've played around a fair bit with adding random factors to my surfing. (Very, very carefully - you don't want to sacrifice super effective bullet dodging vs weaker guns.) It seems like there has to be something there! But I never got it to outperform my non-randomized version. Will be cool to see what you come up with.

Edit: Might be more accurate to say I've played with adding it to my Flattener.

Yeah, my attempts always did worse as well.

I still feel like there's more potential for randomness in surfing than has been seen in use to-date. Specifically, I have plans I've yet to try regarding what I'd call an "obsucated goto" movement to be used as part of surfing. Despite efforts I've heard of thus far being unsuccessful I have a feeling that against the strongest targeting systems out there, a well-designed "pure random" movement with "obfuscated goto paths" (important!) might at least perform around the same as surfing/flattening systems.

Well, none of my efforts have been seen in use because I didn't release any of them. :-) But I've tinkered quite a bit, so it's not for lack of trying.

The idea I thought had the most promise involved generating a completely new/random movement profile every time you get hit. Also tried instead/also a new profile every X ticks, or every time a wave passes, or modeling those random stats in a fair number different distributions (flat with flat juice to super spiky), and in various mixes of random + normal flattener. I guess it's possible some of those would've helped against certain bots, but my testing on this is usually restricted to 2-3 strong bots, since the only improvement I'd really care about is beating DrussGT without sacrificing too much vs Shadow/XanderCat. ;)

Well, I'm far less experienced than you guys are. It might not go too well. What I was thinking was that Phantom would track the bullets as precisely as possible, then find a random angle, velocity, and distance to escape them. Sounds a bit like a flattener. Or maybe it will just do BasicSurfer or BasicGTSurfer movement until it dies, then switch to flat movement. Anyway, Phantom may not ever get released. It sounds like implementing this type of movement is pretty difficult.

The weakness with deterministic movements is your opponent can reverse engineer it, then create a specialist gun which would use your own deterministic movement to predict with near 100% accuracy where to shoot.

Random movement is a more conservative strategy which still perform okayish even if someone tries to use a specialist gun against it.

But since no one is trying to create specialist anti-surfer guns in the rumble right now, deterministic movements tend to outperform random movements overall.

Specialized guns can be complex and costly (in terms of development and testing). But it's true that if you had a copy of the enemy robot's movement code and added all its data up exactly the same way it does (during battle) that you would perfectly be able to predict its movement if it doesn't use any kind of random mechanism.

But with even a slight error, the difference will grow exponentially, since essentially robocode robots are very complex systems to which the theories of chaos theory definitely apply.

Actually, you can't perfectly predict enemy movement even if you have their exact stats and prediction setup because you see their movements a tick later than them. It is probably enough to thrash them pretty thoroughly, but it won't be perfect.

My take on why random surfing hasn't worked out well is because of the same reasons that make a classic Raiko-style random movement not work out as well as surfing: where you currently are affects which locations are reachable. Flattening takes this into account, particularly with 2-wave surfing where you can plan to get to those far-out GFs. Using purely random GF selection will mostly result in GFs you can't reach, or if you try to scale it to where you can reach it will end up being susceptible to statistical analysis from overlaying lots of movements in a classic anti-random-movement style.

My addendum on why random surfing usually hasn't worked out so well also has the following point: In the cases where you scale your random range to where you can reach, there's an additional problem, which is that to my knowledge almost all attempts at such have used a simple goto method or orbit to get to the next GF that was selected, which potentially gives away information about where they were trying to get for that wave earlier than it strictly had to. I suspect that if one adds some smart randomization the timing/velocity/heading during the path used to get to the chosen GF, the result will be blurred as far as the usual statistical analysis is concerned.

Edit for more specific example: If one is using a traditional "orbit until selected GF" method for instance, as soon as you're stopped or begin to decelerate, you've given away exactly where you intend to be for that wave. How early the signal is given away varies depending on how far that GF is from where you ended up on the prior wave, but either way it adds clarity to statistics of where you'll be on future waves. The idea is to add uncertainty to that signal, instead of giving them absolute certainty about where you'll be in a few ticks.

Why would being one tick late stop you from perfectly predicting their movement?