If you want to see love.filesystem at work, you have to put out the .love executable for each OS, and test them. It works differently in development mode.

It's my current gripe, but I just settle with using the defaults and let love2d do all the filesystem work by itself in each OS.

I think moving your "fire bolt" code to love.keypressed function would solve the problem: function love.load() cooldown = 0 end function love.update(dt) cooldown = math.max(cooldown - dt, 0) end function love.keypressed(key) if key == 'space' and cooldown == 0 then player1Bolt:reset() cool...

Since I'm mostly a lonely player, I implemented random-moving AI.

Gonna play it on a machine with audio later... since I couldn't hear the cues, the curse is killing me.

This guy can also show you the ropes.

I found a thread about this.

I'll try the Wayback Machine since only the imgur images are the only survivors of it.

By the behavior that you want. It seems that you're trying to make a "Toolbar Menu" of some sort. It makes sense to imagine those squares as icons.

There are several ways to tackle this: A combination of a State Machine + Making Input Detection Separate from the Animation would be my personal choice. In your case, you seem to have your animation code tied to your Inputs. Try transfering that into the movement code (since that doesn't get affect...

By any chance you mean Mode7?