In fact it would probably be smart to upload Bombable to Gitorious or the like so we can more easily invite other developers to help out.
yes, that sounds like a good idea - but please understand that I only suggested that, because of your own schedule. And obviously, we do have a bunch of talented scripters here who know quite a bit of Nasal, and "fixing" an issue is obviously not as complex as developing the whole bombable beast from scratch
Especially, if the source code is sufficiently well-commented and documents known issues/todos/fixmes.
Suggestion: if you could create a corresponding gitorious* project for bombable and upload your latest release, you can add me as another admin, so that I can add others, in case you are not around. Using git would seem like a good idea, because it will also be easier for you to look at suggested changes, i.e. a time-saver (compared to keeping up with the forum and searching for "bombable" here).
I could also help create a bunch of bombable related tutorials to better document its design/internals and lower the entry barrier for new contributors.
*: For some reason, github seems to be more popular among base package developers than gitorious ... maybe because of the issue tracker and workflows ?