Stop and Go

From RoboWiki
Jump to: navigation, search

I haven't looked at the code, but my guess is your distancing is trying to get away too quickly/steeply, so you sometimes aren't moving a big enough angle laterally to get out of the way, especially with smaller bullet powers.

The other thing might be that you have false bullet detections.

Skilgannon (talk)09:47, 8 April 2019

Hmm, I tried moving around with the movement lateral angle set to 0.3, 0.4, and 0.45, but it didn't seem to do any good. However, I did notice that every so often, Basilisk didn't move when a bullet was fired. I think I will tackle that problem when I have more time this weekend =) Also, it seems my robot gets rammed a lot more often then Cotillion and EpeeistMicro. Against Dalek, approximately every 10 rounds Dalek runs into him, but Cotillion and EpeeistMicro never seem to have this problem. Maybe I'll add some anti ramming code later =) Thanks for the help!

Slugzilla (talk)01:14, 9 April 2019

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.

Dsekercioglu (talk)04:53, 9 April 2019
 

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

The action you have requested is limited to users in the group: Users.


You can view and copy the source of this page:

Return to Thread:Talk:Basilisk/Stop and Go/reply (5).

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?

Dsekercioglu (talk)14:07, 9 April 2019

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!

Slugzilla (talk)21:20, 9 April 2019
 

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)21:25, 9 April 2019

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.

Dsekercioglu (talk)21:35, 9 April 2019

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)22: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)04: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)21:34, 10 April 2019
 
 
 
 
 
 
 
Personal tools