Announcement
Collapse
No announcement yet.
Rumble Bot [Development Progress]
Collapse
X
-
Originally posted by TheRigger View PostWhen you read the image, read it once and save. Then get the pixels you need off of that, much faster.
For your information it does do that. It only take 1 screenshot per move. The reason you think it is slow is because I added a wait to allow for the ball to get to its location. Without the wait it will sometimes send two balls to the same place.
Comment
-
This looks nice! I'm no coder so no criticism from me unlike ^ :P all I know is it looks difficult so good job and I want this for myself!Holden's Vouches | Skype: Holden92x
Comment
-
Originally posted by TheRigger View PostCalculate the distance and the speed at which balls move.
Wait the exact time + random milliseconds.
GG.
Congratulations - Looks a lot better from when "you" showed me it last week.
Comment
-
Since I've made a rumble bot that does well in Sea Battles, here's some tips:
1) You can determine whether or not you can make a move based on whether both fists have a ball attached to them. The next one won't appear until the board has settled.
2) You've got to make charged attacks if you want the bot to be any good in a Sea Battle. There's no telling if you'll get any sprinkles.
3) Rumble's collision sucks. Deal with it.
4) Did I mention that Rumble's collision sucks?
5) If you're going to make a Rumble bot, go the full mile and have it auto team. Otherwise, you can't call it Rumbling.
6) Rumble's collision really, REALLY sucks.
7) The barbarian king has a different background. Either handle it or be prepared for people to whine about it not working.
That's about all I can think of off the top of my head. Oh, wait, one last thing...
Rumble's collision sucks.
Comment
Comment