CerealCoders

Participate in CerealCodes at !

[CerealCoders @CerealCoders]

The Cerealcoders are back at Battlecode - hopefully 2024 will be even better than last year! Look out for team introductions coming soon...

[Regression Games @RegressionGG]

Day 37 of AI, Gaming, and Esports

At @MIT's Battlecode this past weekend, @RegressionGG presented a prize for the Best Devlog Series, given to the team who posted the best updates about their experience throughout the tournament. @CerealCoders are the winners of this prize!

[CerealCoders @CerealCoders]

LETS GOOOOOOOOOO

[Regression Games @RegressionGG]

Congrats to @CerealCoders for winning the Regression Games Best Devlog Series at Battlecode 2023! #battlecode

[Regression Games @RegressionGG]

Congrats to @CerealCoders for winning the Regression Games Best Devlog Series at Battlecode 2023! #battlecode

[CerealCoders @CerealCoders]

better and become a cohesive team, learning so much about teamwork and the development process! Thank you to the wonderful organizers of Battlecode and the sponsors for putting together such a great experience! We hope to participate again next year! #battlecode @RegressionGG

[CerealCoders @CerealCoders]

With all but the Final Tournament over (we unfortunately did not make it to the final round of our tournament), let's look back and reflect at our Battlecode 2023 experience! Since it was our first time competing, we had a lot of work cut out for us at the beginning to

[CerealCoders @CerealCoders]

for new ideas and places our code could grow. Through Battlecode, we were truly able to improve our algorithmic thinking and have it take on a new dimension, especially while battling against some fierce competition. Most importantly, we four teammates got to know each other

[CerealCoders @CerealCoders]

Meant to post this a lot earlier, but better late than never 😅
#battlecode @RegressionGG

[CerealCoders @CerealCoders]

VSCode has a great extension to view Java bytecode, which is very helpful in optimizing our usage of it! As we were building more complex robots and algorithms, it became a necessity to use these kinds of tools to help us better analyze our code.

[CerealCoders @CerealCoders]

launcher. Our new carrier code scans its surroundings for launchers and calculates how many turns left it has to live in the worst case. Only if it is completely doomed for the carrier will it unload its materials and attack the launcher.

@RegressionGG #battlecode

[CerealCoders @CerealCoders]

We decided that having our carriers always shoot at the enemy when possible awfully inefficient, since then a single launcher could just cripple our supply chain. Instead, in some cases it may be better to have some carriers continuing doing their original job while ignoring the

[CerealCoders @CerealCoders]

With the qualifying tournaments underway, here are some of the things we tried with our launchers, each of which worked to varying effectiveness! @RegressionGG #battlecode

https://t.co/qi8i548xAW

[CerealCoders @CerealCoders]

With only one and a half weeks left for the high school tournament, we met and restrategized today for our games moving forward! Some of our plans to improve include launcher strategy and scouting, kept vague for security reasons :)

@RegressionGG #battlecode

[CerealCoders @CerealCoders]

To clarify, this is because of the new balance changes, not because our carrier code never worked. It’s important to test code to see how balance changes may break it!

[CerealCoders @CerealCoders]

So it turns out that our carriers actually never collected resources... maybe that's why our ranking kept going down D: It's fixed now, though - this will make a big difference!
@RegressionGG #battlecode

[CerealCoders @CerealCoders]

@whattonamemysel have u followed 🎤🎤🎤

[CerealCoders @CerealCoders]

This is one of my favorite pieces of code due to its simplicity yet effectiveness. It checks if the HQ is surrounded by too many enemy carriers to possibly handle and stops the HQ from spawning anything if this is true, keeping spawned units from getting instantly destroyed!

[CerealCoders @CerealCoders]

Small correction: I accidentally deleted the > sign while taking a screenshot of the code and replaced it with the wrong sign. Here is the corrected code!

[CerealCoders @CerealCoders]

SUMMARY:
@RegressionGG #battlecode

[CerealCoders @CerealCoders]

POST SPRINT THOUGHTS: (a very long thread)
@RegressionGG #battlecode