Open dgets opened 5 years ago
Okay so it looks like we've implemented the potential collision detection in analytics.NavAssist.avoid_collision_by_wait()
and analytics.NavAssist.avoid_collision_by_random_scoot()
. This is without having made any modifications, so there are still areas where it needs to be implemented. Nao iz zhe time on Schprockets vhere vhe find zhem.
Places where naive_navigate()
is used (areas where collision avoidance most probably needs to be implemented):
NOTE: There may be instances where there is double processing of safe directions to move; I don't think that this will cause any real issues at this point, however. We've got plenty of processing time to burn here.
Collisions are still happening, although it appears to be happening much less frequently. I think it'd be a good idea to check seek_n_nav.Nav.generate*()
to see if maybe one of those isn't implemented collision detection incorrectly.
This may have just been finally fixed up by the last commit made en route to #59.
Welp, it was not just fixed; there are still collisions taking place between my own ships under control of this bot at times. Something still isn't being done right...
Collisions are still happening; this hasn't been implemented in all places yet. Make sure that potential moves are being stored in the appropriate array, checked, and other moves being selected if applicable. Also make sure that the array will be wiped at the end of each turn.