Stop and Go

The code seems identical but I have noticed some randomized direction change in Basilisk. It might also be that it gets activated when it's not supposed to.

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?

The randomized direction change is only supposed to be activated when its using random movement, but I'll add some print statements to make sure. Thanks!

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 =)

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.

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?