Timeline for Red vs. Blue - Pixel Team Battlebots
Current License: CC BY-SA 3.0
28 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 17, 2020 at 9:04 | history | edited | CommunityBot |
Commonmark migration
|
|
Apr 2, 2015 at 18:16 | comment | added | Etheryte | If it isn't broken, remove the old obsolete comments to reduce clutter. | |
Apr 2, 2015 at 17:50 | history | edited | Ismael Miguel | CC BY-SA 3.0 |
deleted 26 characters in body
|
Apr 2, 2015 at 17:42 | history | edited | Ismael Miguel | CC BY-SA 3.0 |
Last Fix!
|
Apr 2, 2015 at 17:37 | history | edited | Ismael Miguel | CC BY-SA 3.0 |
Last Fix!
|
Apr 2, 2015 at 17:27 | history | edited | Ismael Miguel | CC BY-SA 3.0 |
Last Fix!
|
Apr 2, 2015 at 16:35 | comment | added | Ismael Miguel | @AdamDavis If you need, ask me questions and I will answer. Or set up a chatroom. Imagine Javascript as a C primitive without data types. And you will get there quickly. | |
Apr 2, 2015 at 16:34 | comment | added | Adam Davis | @IsmaelMiguel Nope. I'm hoping to submit one soon as well, but not knowing Javascript is slowing me down. | |
Apr 2, 2015 at 16:29 | comment | added | Ismael Miguel | @AdamDavis I have 4 minutes. Any more ideas? | |
Apr 2, 2015 at 16:27 | history | edited | Ismael Miguel | CC BY-SA 3.0 |
added 453 characters in body
|
Apr 2, 2015 at 16:13 | comment | added | Ismael Miguel | @Calvin'sHobbies I know, I'm making some adjustments. | |
Apr 2, 2015 at 15:42 | comment | added | Calvin's Hobbies | And don't forget about the 6 hour edit limit that you're approaching. (Just in case you didn't see.) | |
Apr 2, 2015 at 15:25 | comment | added | Ismael Miguel | @Calvin'sHobbies Thank you a lot!!! I forgot to put it there. Stressful day at work... :/ | |
Apr 2, 2015 at 15:24 | history | edited | Ismael Miguel | CC BY-SA 3.0 |
added 15 characters in body
|
Apr 2, 2015 at 15:22 | comment | added | Calvin's Hobbies |
@IsmaelMiguel Your try needs a catch block. You are erroring all the time.
|
|
Apr 2, 2015 at 11:37 | comment | added | Ismael Miguel | @AdamDavis The idea is to basically stay still until I can kill someone. And go to his 'blind spot' if he is too close. Basically, this guy can be a good beacon, if someone manages to get a schema to compress it all. | |
Apr 2, 2015 at 11:36 | comment | added | Ismael Miguel | @Nit It will be easy to add info. But it will be hard to process it all in 15ms. | |
Apr 2, 2015 at 11:35 | history | edited | Ismael Miguel | CC BY-SA 3.0 |
added 52 characters in body
|
Apr 2, 2015 at 11:33 | comment | added | Adam Davis | I'm thinking the first few need to be scanners. We only need four to sweep side to side to cove the entire board (32 effective scanning width covers 1/4 of the board). Move side to side, setmsg nearest N bad guys using a binary or compressed string, and either avoid bad guys, or seek and kill bad guys using a reasonable strategy to avoid being killed (never let them get on your corner, nor above or below you?). | |
Apr 2, 2015 at 11:30 | history | edited | Ismael Miguel | CC BY-SA 3.0 |
added 52 characters in body
|
Apr 2, 2015 at 11:24 | history | edited | Ismael Miguel | CC BY-SA 3.0 |
added 52 characters in body
|
Apr 2, 2015 at 11:15 | comment | added | Etheryte | Right, my bad, missed that bit of the spec. In that case I think this is a good start, but others may want to add something. | |
Apr 2, 2015 at 11:14 | comment | added | Ismael Miguel | @Nit We have only 60 bytes.......... I'm trying to recude the 'protocol' | |
Apr 2, 2015 at 11:13 | comment | added | Etheryte | What does was include? I think the data should include both tNear and eNear to allow others to put together a whole picture. | |
Apr 2, 2015 at 11:11 | comment | added | Ismael Miguel | @Nit I agree with you, and that's why I made this choice to use JSON to communicate. I have 5 hours and 22m to make changes. any more ideas? | |
Apr 2, 2015 at 11:07 | history | edited | Ismael Miguel | CC BY-SA 3.0 |
added 1166 characters in body
|
Apr 2, 2015 at 11:05 | comment | added | Etheryte | As someone on the red team, I think one crucial thing we should include is always set a message with your current state and surrounding in some agreed-upon form of an object (this must include what move this was set on, otherwise bots won't know which state is outdated). This will allow other, later bots to be aware of more than their own surroundings, possibly the whole board, and make better decisions. | |
Apr 2, 2015 at 10:34 | history | answered | Ismael Miguel | CC BY-SA 3.0 |