Stop and Go
Sounds like some bugs or missing factors in the enemy energy tracking.
I don't think so, it both counts hit bullets and energy gains in the bot. Maybe try printing different movement modes on the console to see if they are being switched abnormally?
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!
As long as you are checking if delta energy is between 0.1 and 3.0 there shouldn’t be any problems. I think that your current system of upgrading enemy energy is working but I’m not sure.
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 =)
You do not have permission to edit this page, for the following reasons:
You can view and copy the source of this page.
Return to Thread:Talk:Basilisk/Stop and Go/reply (11).