Hi, I’m new.
I basically have no gamedev experience except opening Unity a couple of times. I rely on my C# skills (I’m a TA in a basic C# course) and Google (hopefully they have all the answers). My tactic is to “keep it simple”. I will probably start with squares and circles…
Beverage of choice will be coffee.
As promised: Squares and circles, and as a bonus it’s in the desert. I think I just got the hang of it now. I started out with some input problems (google wasn’t very helpful), and then I had some problems with my timber disappearing when I added the textures. To summarize: The game will probably be really dull, but the coffee tastes great 
This will be my second entry. My first try ended badly after laying sick in bed all Sunday. This time I feel fine.
I’m in the middle of my exams this semester and I should be studying this weekend. Therefore I have decided to make a game as an exercise using the techniques that will be tested in the exams. A couple of those techniques are finite-state machines and multi-threading. I have yet to decide whether I will be making a game in Unity or just a console game.
You chose “one room” and this triangle has its own tiny room. At least it doesn’t have claustrophobia.
My tiny room with the triangle just turned into snake. I was building some other features and it just happened, let’s call it a bonus (not a bug/setback).
Sorry for the extra mouse cursor. Let’s call it a bonus
It’s 23 minutes until deadline and this is me throwing in the towel for LD37.
Concept: Maze puzzle game where you make your own maze following a story. The game starts out with a small empty room that is expanded and built by tearing down walls, and pushing blocks into different spots.
Goal: Making a game. Also I’ve mainly used LD37 to exercise for my semester exams coming up this week with the subjects multi-threading and finite-state machines.
Tool: JetBrains Rider (buggy as hell) with .NET Core console application
State of the game: Unplayable/Too short (The base of the game is implemented, I just didn’t get around to using it.)
I started out just typing code before having a concept. Never again! (Just maybe sometimes) I have deleted and rewritten so much code, and the last hours was full of small and fundamentally bad bugs because of this.
The weekend was absolutely “NOT WASTED”. The game has half a billion unique threads that goes all over the place. All of them with a lesson.
The game has a shaky mode for earthquakes that I used way too many hours implementing, just fiddling with how the tiles were placed. It could easily have been done just by using 15 minutes thinking instead of coding. It was in the graphics I lost.
TLDR:
Most important lesson learned: Make time for pen, paper and planing.
Success: Yes!
8/10 would LD again.