Stop and Go

Jump to navigation Jump to search

Maybe I should move the stop and go into the onScannedRobot event instead of its current goTo void. Currently I am using prevEnergy > enemyEnergy, with enemyEnergy being called every tick and prevEnergy being called right after moving. If I move it into the onScannedRobot event, and use prevEnergy > e.getEnergy(), do you think that would fix some of its problems? Thanks!

Slugzilla (talk)‎22:25, 9 April 2019

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:Basilisk/Stop and Go/reply (9).

Currently I am just checking if the energy drop is greater than 0.1. I'll add a 3.0 segment later to fix that up. By the way, congratulations on Partial getting #23! The race is neck to neck =)

Slugzilla (talk)‎23:34, 9 April 2019
Oops, you might want to use 0.099 < e < 3.01. Sometimes energy 3.0 and 0.1 won’t be detected.
Partial is using Simonton’s PM Gun so there is a lot to improve. You might have noticed its low Pwin. I am prettt sure Basilisk will enter top 20 when the bug is fixed though.
Dsekercioglu (talk)‎05:51, 10 April 2019

Oh sorry, i misspoke. I check if the energy drop is greater than the previous energy, so 0.1 should register. Are you going to add on to the PM gun or maybe try out a guessfactor gun?

Slugzilla (talk)‎22:34, 10 April 2019
 
 
 
 
Retrieved from "http://robowiki.net/wiki/Thread:Talk:Basilisk/Stop_and_Go/reply_(8)#Stop_and_Go_6553"