Ludum Dare 34 — December 11th-14th, 2015 — Theme Tied: Two Button Controls, Growing

NOTE: Because of the Theme tie, we allowed everyone to pick either Theme. Using both was optional. To keep things simple, there will still only be one Theme category. Every category in Ludum Dare voting is an opinion, so you’re welcome to rate them as you see fit. But we encourage you to be fair in your scores to people that chose only one Theme, and not both.

ALSO: has an experimental game downloader over here. You may find it useful.

Back to Browse Entries

Grow the Tree

by mummelgruf - Compo Entry

Hello everyone,

this is my first LD so far and I haven't done much game development. Hopefully you'll enjoy the game anyway :).

It's written in C#/MonoGame using Visual Studio Community 2015. The assets were made with

The goal is to grow the tree in the center of the screen by pressing the "A" or "S" button. Which button you need to press will be determined by the blue circle that'll randomly spawn every second at one of the four edges of the screen.

Just download the archive via the dropbox link, extract it, step inside the "Grow the Tree" folder and click the LD34.exe.

Inside the "LD34" folder is the whole Visual Studio project with all the assets.

Downloads and Links




gmisail says ...
Dec 14, 2015 @ 1:15am

Very bland; there is a ton of empty space.

djdudes100 says ...
Dec 14, 2015 @ 1:55am

Good try but It doesn't seem to be working :P

Dooskington says ...
Dec 14, 2015 @ 3:19am

Pretty basic.. All that empty space and cornflower blue. At least you used the two themes well. Next time, I would try spicing it up a little bit.

Farelle says ...
Dec 15, 2015 @ 9:37am

I think some feedback would have been nice, like a sound or button flashing, if I succesfully hit it in time.
Also, I couldn't find out if it has a win and loose condition at all, so it's never ending button pressing?
Themes are very clearly visible though!
suggestions: since the buttons were switching position, they would have been nice as the actual christmas decoration :)

mactinite says ...
Dec 17, 2015 @ 7:56pm

Alright, so first off, obviously pretty bare bones, but that is fine. If you want to develop this further (for learning or other reasons) here's what I recommend adding:

Add some button diversity, make each button prompt be a random letter key on the keyboard, and with that make the time the button is up longer.

Add some negative consequences to not pressing the right button, maybe shrink the tree a bit, but not as much as it grows.

Add some animations for response to input, ie make the screen flash red when you hit the wrong key or make the buttons "pop" when you press them.

Add a timer and a way to see that when they grow the tree enough.

Lastly, add a non-static background, maybe a scrolling repeating graphic?

Anyways, you may find that useful, or you may not. Good luck and have fun developing! :)

You must sign in to comment.

Mini Submission FAQ

TEAMS: Teams entering the Jam should pick a single representative to submit your game, or create a team specific account you can share. We currently do not support Team Voting, but sharing an account and together playing and rating games is acceptable.

CAN I ENTER BOTH EVENTS?: You should pick 1 event, whichever you think it’ll do better in. If the idea is strong, and everything plays well enough, you can go Compo. If you’re a perfectionist, and would prefer people to play a more polished game, do the Jam. Historically, more games are entered in the Compo, but with more people and more time, Jam games have the potential to be better (that doesn’t mean they are). Many solo participants do enter the Jam.

If you made 2 games, unfortunately, the website doesn’t support multiple submissions per user. To submit your 2nd game, you will have to make a 2nd account. Only do this if you made 2 games. Alternatively, if one game is better than the other, then consider just entering the better game.

CAN I KEEP WORKING UNTIL THE DEADLINE?: Yes! Immediately after the 48 or 72 hours, we do something called Submission Hour. As the name suggests, it’s an extra hour for you to package, upload, and submit your games. If there were catastrophic issues trying submitting your game, or you misunderstood how submissions work, that’s okay. It happens. We’re flexible. If you need advice, check with the folks on IRC. If you need an admin, get in touch.

CAN I KEEP WORKING ON MY GAME?: Oh definitely! You should! But for the sake of judging, keep the Compo or Jam version around. You can include a link to the Post-Compo/Post-Jam version of your game on your games page, but sure your main links are the original version.

PORTS: Ports to other platforms can be done after the deadline. That said, the sooner you finish your port, the sooner people can play your game, improving your chances of placing in the final results. For best results, provide a Web version of your game, or a Windows version with no dependencies. Also be sure to rate at least 20 games to improve your visibility (Coolness).

MY GAME CRASHES, IS UNBEATABLE, OR I MADE A TYPO: We allow you to fix crashes, win condition, or tiny bugs after the deadline. In a sense, this is like “porting” to support more players. We leave this open to interpretation, but generally speaking your game should be identical to the game you submitted. No new features, just fixing mistakes you should have caught had you been better rested.

MY GAME DOESN’T SHOW UP: If you can’t find your game, it’s usually because the URL to your downloads are missing ‘http://‘. Fix your URLs ( and you will show up. Alternatively, if you just posted it, wait a minute. The cache may not have refreshed yet.

NOT LOGGED IN?: If you get a message about not being logged in, even though you are, it’s because your web browser cached the non-logged in page. You can fix this by either refreshing your cache or clearing your cache. CTRL+F5 in many browsers. Chrome is a bit more work. Press F12 to enable Developer Mode, then you can right click on the refresh button and select “Empty Cache and Hard Reload”. This option is unavailable if you are not in Developer Mode.

[cache: storing page]