I'd say we got a lot done as a group! I think there's some numbers that didn't get added in, but as a group, we wrote over 400 lines of code, completed/fixed 4 features/bugs, made 14 commits, created 13 classes, made 4 art assets, and unlocked at least 4 achievements.

Of course, those numbers don't really mean that much; it's just a fun way to see that stuff actually happened in our game development stories last night!

So congrats and thanks to everyone who participated!

So it seems like it might be kind of fun to put our numbers in the Google Doc Spreadsheet linked below to track our numbers.

https://docs.google.com/spreadsheets/d/1IqSW0kAbs0Yieu6sK3ND0h_QB92Yr8dLJSCwywMJBCs/edit?usp=sharing

Let me know if you're having problems accessing it.

We can perhaps put some target goals in there as well, though it's hard to pick realistic numbers. So I think we either pick completely arbitrary numbers and just roll with it (who cares if we're way off—it's just for fun) or wait until we're an hour in and then multiply by 8 or something. Thoughts?

If you want to join, but need us to shift things by a few hours, I think we're all open to that.

It's also long enough that if part of the time is too early/late for you, you can always leave early or join late!

The idea would be to spice things up from another normal day/night of programming, by picking some target goals or numbers for things we want to work on to accomplish as a group (working on our own projects).

For instance, we could say "We're going to try to write 1500 lines of code tonight as a group, fix 10 bugs, add 10 features, and make 30 commits."

The numbers are all measured collectively as a group (though I could be talked into splitting into two teams and competing or something) so it would add a sort of cooperative feel to this month-long challenge. We could probably all drop our numbers into a shared Google Spreadsheet. (The numbers above are picked out of the air. We'd pick our own numbers together as a group.)

The numbers, of course, would be adjusted based on how many people are doing the coding marathon and how long we decide to do it for. (Though in my head, I'm imagining like an 8 hour overnight thing or a 12 hour day-long thing.)

We could either arrange it for Friday/Saturday overnight, Saturday/Sunday overnight (all-night code marathons are where the good stuff is!) or we could to a Saturday-long coding marathon.

If we all lived nearby each other, I'd totally buy us pizza and turn it into a party…

This could be a good opportunity for people who have gotten derailed by something in the first half of the month (or newcomers) to get back on track, or for others to get a little speed boost heading into the second half of the month.

If this doesn't interest you, no worries. Just do your normal game development. If it interests you, let's start formalizing some plans!