Rubygame 2.4 released; Project seeking new maintainer

I have two major announcements related to Rubygame:

  1. Rubygame 2.4 is now available
  2. I'm stepping down from my position as project maintainer

First, the happier news. Rubygame 2.4 is, finally, done. This release contains the much-anticipated event handler system, which allows you to define how your objects respond to events (e.g. keyboard presses, mouse clicks, and even your own custom, gameplay-related events) in a dynamic, object-oriented way. I'm very proud of this system, because it is flexible, extensible, and powerful, yet at the same time easy to use and made of very simple parts.

Rubygame 2.4 also includes a new suite of event classes for keyboard, joystick, and mouse input, and all the other things. They are a full replacement of the older events, and I strongly encourage you to upgrade your games to use them (use EventQueue#enable_new_style_events to do that).

This release also includes a patch to enable key repeat, contributed by Roger Ostrander (atiaxi), and several bug fixes. See the NEWS file for the full details. Downloads for Rubygame 2.4 are available at Rubyforge. Precompiled gems for Windows and Mac are not available as I'm writing this, but I'll post them at that same spot as they are sent to me. (Hint, hint.)

Now then, the more serious news.

After 4 years of off-and-on work on Rubygame, I have finally decided to step down as project maintainer altogether. From my vantage point, this is long overdue. Anyone reading this blog over the past 8 months can see the reason why I'm stepping down: I just don't have the time, energy, or motivation to be a reliable maintainer anymore.

So, Rubygame 2.4 will be the last release of Rubygame I make, but I hope not the last release of Rubygame ever. There are plenty of ideas on the ROADMAP, and the Git repository has a lot of code in the dev-3.0.0 and old-3.0.0 branches that could be cleaned up and released.

But the project needs a new maintainer with the time, enthusiasm, and experience to keep it moving forward.

If you're interested in being that person, please send me an email: jacius at gmail.


max submitted a comment on #

All joy on the 2.4 release vanished on hearing that you are stepping down. I understand you can’t do this anymore. I hope someone does take this up and keeps the fires burning.

Thanks for everything. :-) and good luck!!!

max submitted a comment on #

ok.. me again :-) .. the download links don’t work.. i get a 404 when i click on either .bz2 or .gem download in

can you check this?

Kiba submitted a comment on #

Does that mean we can expect a game from Jacius soon?

max submitted a comment on #

ooohhh.. now there’s a nice thought!! :-)

John Croisant submitted a comment on #

@max: The downloads on Rubyforge are working for me, please try them again. If they’re still not working for you, you can download the release from

atiaxi submitted a comment on #

I know all to well what you’re saying - I’m going through exactly the same time and energy constraints working on my own game - so I can’t in good conscience badger you to keep working. However, the same reasons that let me personally understand what you’re going through are the reasons I’d make a poor full-time Rubygame developer myself.

What I’d like to see instead is a Rubygame maintainer. That is, someone who merges bugfixes in and little else, someone who maintains what’s been done so far.

2.4.0 is complete enough for me to write a (huge) game based on it, and so far there aren’t any functionality holes in the library that prevent me from doing so. I get all the power of SDL, all the niceties of pygame, plus I get to do it in Ruby. Where Rubygame is, right now, is a perfect stopping point for development. All we need at the moment is someone to merge bugs in. (And that seems a much less daunting task to me than spearheading the next generation of Rubygame)

My point is: You’ve done a good job. Rubygame is an excellent library. You deserve your rest :)

Beoran submitted a comment on #

Actually, after thinking about it, perhaps atiaxi’s idea is the most feasible for now. The users of Rubygaeme can make a maintainers committee that just bugfixes and adss andy missing functionality. Then, I will keep my wild and crazy ideas for a separate project of my own.

markus submitted a comment on #

Somewhat sad to see you leave, but I can understand you completely. Unfortunately I still lack the C knowledge to really maintain such a big project (and rubygame is quite big by now)

I believe what we as users should do is to continue to keep the project as such alive. It does not really need fancy new additions as such for one guy alone to maintain at all. Jacius was pretty much alone in pushing rubygame forward. I of course hope that the work was not all lost.

We still have to catch up a bit with pygame in terms of playable games.

I guess if we as a user community can keep the project in healthy shape for some time, we might have demonstrated that we can maintain the project on our own already.

And for new ideas we can find other ways, rather than putting all the work on one guy alone.

PS: I still think there should be an add-on project for rubygame, one with ready-made, component widgets which can be used in a game rather easily. They do NOT need to be perfect, they just should make it easier for casual player to develop i.e. simple games with writing too much code.

ElCuGo submitted a comment on #

I sometimes wish that days lasted 25 hours, I can really understand you. I hope you don’t step out of Ruby development completely though.

Have something interesting to add to the discussion? Email your thoughtful comments to