-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Java - turnRight
and turnLeft
never stop turning if last function
#23
Comments
You are right @beamer159, This sure sound similar to to the forward/back issue even when they funtion a bit different. I guess I will need to setup some test with various "bots" moving differently, so we can catch these kinds of bugs in the future when doing adjustments. Thank you for reporting this, and keep up the good work. We need to get rid of the "child sickness" in the new version of the game while it is still in "alpha" version. 🙂 |
I can add, that this bug is also present for turning the gun and radar the same way. |
This bug has now been found and solved for both the JVM and .Net version of the Bot API. |
|
Hmm, I am still getting the same behavior.
This program turns indefinitely for me. Additionally, after the bot completes 8 revolutions, it spams this message (I assume) every tick:
Also, same behavior is now experienced for |
Confirmed. This bug was fixed, but was reintroduced when improving/fixing the event queue. I will look into fixing this ASAP. |
Release 0.13.2 should finally fix this issue. I tested it thoroughly for bot the Java and .Net API. 🤞 |
Looks good, thanks |
Version: Java
If the last function called in
run
isturnLeft
orturnRight
, the robot turns and never stops turning. If another function (e.g.forward
) follows one of these two functions, the robot stops turning and performs the next action, as expected.Some thoughts. This is similar to #17, which was recently fixed for
forward
andback
. Now, these two functions are experiencing another issue in #22. When this problem withturnLeft
andturnRight
is looked at, hopefully the solution does not lead to similar #22 issues.The text was updated successfully, but these errors were encountered: