Ludum Dare 32 — April 17th-20th, 2015 — Theme: An Unconventional Weapon

chromenopePSA: As of Chrome 42 (Released April 14th), NPAPI plugins are disabled by default! That means Unity Player, Java, and Silverlight games will not work in the Chrome browser! That said, Flash in the Chrome browser continues to work fine (PPAPI).

To Developers: Consider using HTML5 and WebGL instead. Having troubles with the export? Don’t worry. See Ports below.

To Players: A workaround is to enable NPAPI plugins in your Chrome settings. Click or Copy+Paste this URL in to a tab:


As of September 2015 however, this option will no longer be available.

Other browsers (Firefox, Internet Explorer, Safari) and Flash are unaffected, but FWIW there is no Unity Player or Silverlight for Linux.X

Back to Browse Entries


by arteiro69 - Jam Entry

What if you're walking on the street and alien pursue you???
Everything can happen!

Downloads and Links




Liam :D says ...
Apr 21, 2015 @ 8:35pm

Are you only providing the source code? Can you not build the game and provide an already built exe file? I mean I'm seeing a lot of c++ files in there, and I'm guessing that's a visual studio project file... at the top of Visual Studio, there's a drop-down box. Select "distributable" or something (defaults to "debug") and build. It should create a "dist" directory. Just zip the files in there and upload those.

yuigoto says ...
Apr 25, 2015 @ 1:54am

I'm a beginner in every possible way, but I can at least provide some analysis about your game and the way you did things.

I've opened up the file and found lots of "hidden" files, with only a win executable for the game as the visible one. This can make things quite confusing for people so, while distributing your game, try to separate source code and executable, as it makes it easier for the general player to download and play it.

Tthe idea is quite a crazy one and the weapons are really unconventional, and that's good, but needs refinement. Also, looks like you mixed some graphics/audio assets from other people/sources in the game. When you do it, Ludum Dare says you should opt-out from these categories to avoid problems.

Also, the game needs a description. How to play it, how to use the weapons, what are the weapons? People from other countries might not know what a TCC is (in Brazil, the "TCC" is the equivalent of "Course Completion Assignment" in college) so try to find an equivalent description to help people understand the game and what you mean with the game.

And, one last note: check "Content Rating". Some people might find some of the weapond quite offensive, so you should warn everyone who plays your game, ok?

It's an unusual idea, but you should look at some details before publishing the game, or these details might hold you from being able to publish it. Ok? Anyway, congrats on finishing and publishing! ;)

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]