We delimit messages between processes with the '\n' character. Python changes this to '\r\n' on windows. So the message "Done" will show up as "Done\r" when the environment reads it in. So far, this has not conflicted with our parsing. I want to be aware of this. I cannot find a good way to fix this.

When I run a game (settings: "30 30 DebugBot.exe StillBot.exe"), the StillBot loses a ton of strength (255 -> ~100) during the first move and then starts behaving normally. Additionally, the amount of strength lost depends on the defense_bonus - with a higher defense_bonus, it loses comparitively less strength.

• not clear that you can move the timeline back and forth
• bottom chart truncated

URL = http://halite.io/website/game.php?replay=1475691303-670599101.hlt

Happened while running a 60 by 60 game. The running the environment from the exe in the debug folder. Ran the C++ Random example bot from a Visual studio. Ran the python example bot from cmd. the C++ bot was player 1. Haven't since been able to replicate the bug. This may be due to the randomness of the two AIs that were being run.

Page header is green.
Notification color is green.
Not very user-friendly.

Usually:

• yellow for warning
• red for error

We should probably include a couple of bots in each starter package. I was thinking of a random bot, a basic bot, and an expansion bot. Right now we just have a random bot.

Need to make sure this is true for all cases (such as ais on different computers).
I need to fix this. This is here to remind me.

Hey guys,

FYI, the current master branch has some serious issues that were causing me to tear my hair out this weekend. Messages are received inconsistently, even with -t enabled. (On an ubuntu machine). Just warning you so you make sure to QC it thoroughly before releasing.

Best,
Chris

There is a massive amount of copied code in the halite folder.

builds haven't been updated for months

Really small maps and games produce non-functional files.

• email to acknowledge a bit has been submitted
• email to acknowledge the bot has been compiled successfully
• email when games I have been played

You want people to come back to the platform.
Give them a reason to do so.

• Creation of 120 users
• Make sure autoscale works
• Check that pagination is good
• Check that db latency isnt too bad (would result from manager stress)
• Check manager latency

Probably best done with an electron wrapper around the web visualizer

https://developer.github.com/v3/oauth/

Need to implement the docker sandbox used on https://github.com/HMProgrammingClub/NYCSL

In thee Java API Networking Class, to exit on error, we do this in one of our methods:
System.exit(1);
return null; // the java compiler is stupid.
Is there a prettier way? The compiler makes us put a return statement even though we are exiting.

• Record what games each worker is running
• Finish writing up bad bot section

Opening an issues b/c there is a lot of stuff here

• Reshoot quickstart video
• FAQs
• Make game spec more visual
• Emphasize dev lifecycle in quickstart spec
• Strategy spec that goes over things that are always good and some avenues for exploration
• Better sections (Advanced section for IO spec)
• Add python and c++ code to spec

Documents to Rewrite

• Game Spec
• Contest Spec
• Visualizer Spec
• Quickstart
• ML tutorial

• Compile bot, update source, update status, update history
• Run game with bots, update trueskill, update stats

Is there a better alternative?

• Ensure that worker has posted the results to right game, alert us if hasn't
• Ensure that worker isn't running games super quickly (indicates taken over and manipulation of rankings in progress)

I took out the FTGL text rendering, since it's another library to deal with and it's not really universally supported anymore (It's been finnicky on my laptop).
I rewrote our text rendering in straight OpenGL with FreeType2.
The text rendering works perfectly, except for two things:

1. It adds about 20 milliseconds onto the time for rendering. Not a huge amount, but significant enough to bother me, and I don't see why it should take so long, given that all it has to do is draw a couple of Quads to the screen.
2. Every ~30ish frames, the Visualizer lags in a very noticable way. It averages about 750 milliseconds on the lagged frames, whereas it averages 20-50 (depending on map and game size) on other frames. I have no idea what's causing that.

• submit file and not folder
• submit using the correct file name

The info appears in the email message you get with a bot submission error. This is too late and frustrating. It should appear sooner. Create a dedicated page for bot submission.