Exact path prediction

Jump to navigation Jump to search

Exact path prediction

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Users.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page.

 

Return to Thread:Talk:IWillFireNoBullet/Exact path prediction.

What do you mean by "direct access"? Like to use Robocode's engine during the match instead of writing the prediction?

If you want, the MovementPredictor in Diamond is exactly correct and you're free to use it.

Sounds like you might just need to look at getNewVelocity: https://github.com/Voidious/Diamond/blob/master/voidious/utils/MovementPredictor.java#L125

Voidious (talk)13:55, 20 August 2015

Yep. This is what I meant. Robocode's getNewVelocity is implemented very close to it, and even acknowledges you. But it is unaccessible from the robot. So everyone had to re-implement it.

I wish one have a way to call getNewVelocity directly.

Beaming (talk)22:54, 20 August 2015
 

Oh, and if you mean Robocode source code, I think you would look at RobotPeer.updateMovement: [1]

Sorry, you mentioned not wanting to look at "Robocode sources", which confused me. But maybe you just meant other bots.

Voidious (talk)15:48, 20 August 2015