Posts Tagged ‘warmup ld23’

Problem with Links in warm-up game page

Posted by (twitter: @caranha)
Sunday, April 15th, 2012 6:28 pm

To the powers that be :-)

The link to the author’s journal in the warm-up page is broken – It is pointing to the “ld22” category, which is pointless for people who are participating for the first time, or who for some reason skipped ld22.

I suggest that you change the link from:



I’m all warmed up now! :-D

Posted by (twitter: @caranha)
Sunday, April 15th, 2012 7:48 am

Yay, finished my warm-up game, and managed to refresh my mind about the basics of setting up a new game with Java + Slick2D.

You can see my entry here. It is a simple horizontal scrolling shooter, but I managed to remind myself of all the basics, like loading sprites, moving them, having multiple states for menu, game modes, pausing, game over, etc; loading and playing sounds, and some basic event and collision handling.

For some reason, my web applet is not working on my linux boxes – may be a problem with 32/64 bit libraries, I don’t know, and I can’t see any debugging messages :-( The fat jar works fine though. Any other linux-ers who could try my applet would be very appreciated! (applet works fine on windows).

Also, can anyone suggest me a program/tutorial/example about how to make music for a game? That was my weakest point last LD, and I would love to improve that this time around.

See you next week! 😀

Second Ludum Dare, Go!

Posted by (twitter: @caranha)
Saturday, April 14th, 2012 7:58 am

Wow, next week already? Awesome.

To be quite honest, I mostly slacked since my last LD :-( I had these huge plans, see: improve my game, write a text window library, create a small “evolutionary garden”. And all of that got lost in the shuffle :-( That is what happens when you don’t have deadlines.

<3 LD48

Well, so for this LD I will try to get right what I got wrong last time. I will use Slick2D again, but now I won't have to learn the library from zero :-). I have written a small todo list, and tomorrow I will go through it for the warm-up, to make sure that all is working kinda all right for the dare.

Also, I am in a new apartment, and with a much improved setup if compared to last time:

My work setup for LD23

The down side is that now I’m on the GMT+9 timezone, which means the LD will start 10AM on saturday, and end on 10AM on sunday – so I won’t get much in term of last time additions… but at least I will begin with full speed on the first day.

Also, on LD22 I managed to get 10th place community due to my reviews. So I got a reputation to uphold!!! :-) It will be quite a bit harder this time, since now I got a full time job, so I won’t be able to dedicate entire days for reviewing, but I will see what I can do.

GL HF everyone!

Warm Up Weekend!

Posted by
Friday, April 13th, 2012 6:07 am

I’m going to be spending a few hours livestreaming my warm-up for LD, so if you’re interested in watching drop by and make sure to hit “Follow” to be alerted when I go live.  I expect I’ll put in a bit of time tonight (around 7-9 EDT), plus a few more hours on Saturday and Sunday.  Note:  My channel is primarily for gaming and there will likely be a sizeable audience and a good chance that I’ll also be doing some Let’s Play.

I figure that the best way to do the warmup is to random from 1-100 and get a theme from the list at — but since I don’t want to spend a full 48 hours I’m going to roll ahead of time so I have a chance to think a little before I dive in.

Roll Result = 46.  Theme = “This is your dungeon”.

Interesting.  I always love roguelikes and even old-school text adventures, so that gameplay screams out right away.  But the “your” part of the phrase is making me think that maybe the player should have some ownership of the dungeon.  Should I be looking to Dungeon Keeper for inspiration?

I have several hours to think before I can even start programming, so it’ll be interesting to see where my brain goes.  (Programming Language: I want to do a web app with lots of server-side stuff in Ruby on Rails.  Front-end will be HTML/JS.)


[cache: storing page]