Are you sure about that, Xgoff? I use #table all the time, and have never had any behavior like that. I thought that ipairs always behaved exactly the same as #table in regards to sequential numeric indices and nils.

Numeric for is faster than ipairs, so I'd suggest using it in time-critical code (ie., inside love.update and love.draw), but elsewhere, ipairs is fine.

You definitely don't need a semicolon to have multiple statements on one line. Lua simply ignores the symbol. It's allowed only because some programmers are so used to using it. Lua doesn't care about whitespace, and in fact, you could put the entire program in one obscenely long line if you really ...

Our project is coming along nicely. (That's 42 FPS on a netbook) http://dl.dropbox.com/u/3713769/temp/crystals.b.1.png We've got working physics, some graphics and particles, asteroids which break apart when damaged, ships with multiple turrets, and AI-controlled skirmishers. It doesn't yet have sou...

Very easy to do. All you need is a variable for keeping track of which way you're facing. Personally, I'd keep animation state as a variable, too, and save yourself some code. Try this: require 'AnAL' ---- function love.load() love.graphics.setBackgroundColor(255,255,255) imgIdle1 = love.graphics.ne...

So far, I've found the following Box2D crashes in Love: - Creating bodies within the scope of a collision callback - Unknown crash using world:queryBoundingBox, in the following code: shoot = function(self) self.shootTarget = nil local x,y = self.b:getPosition() world:queryBoundingBox( x-400,y-400, ...

I turn to Audacity for most of my sound-manipulation needs, since it's free, open-source, and small. There may be a better/faster/more-convenient one out there, but Audacity can do more than convert, which comes in handy. If you use Linux, chances are you already have it installed.

Personally, I'd recommend using libraries. They save you from having to re-invent the wheel, solving boring problems when you could be learning by solving important, game-making problems. I suppose it would be a good exercise to do it your own way once or twice, but you could probably also learn a l...

Issue You've got code checking the keyboard in two different places. In one you check "if left then ... elseif right", and in the other you "if right then ... elseif left", which is producing your weird behavior. Since you set the variables "moving" and "direction...

Well, you can use that in all sorts of ways. You just pass the coordinates, width, and height of two squares, and it will return whether or not they overlap. You can use that in an if statement to do stuff (like triggering an event, collision, removing one, whatever). I'll give you an example which ...