-- Axis aligned bounding box(AABB) collision -- Returns true if the rectangles overlap function aabb(x1,y1,w1,h1, x2,y2,w2,h2) return x1 < x2 + w2 and x1 + w1 > x2 and y1 < y2 + h2 and h1 + y1 > y2 end -- Same thing, but o1 and o2 are tables containing at least x, y, w, and h function aabb2(o1, o2)...

After countless times of trying to reinvent the wheel I tried a few libraries, but couldn't settle on anything. Right now I'm using Nuklear, it's an immediate mode GUI so it's a little different, but I like it.

Bare minimum could be something along the lines of:

Trainsported was a cool game that used programmable AI to complete challenges or "battle" your trains online. I highly recommend checking it out.

Lua is all about tables. Put the touch events into a table and tinker from there... local touches = {} function love.touchpressed(id, x, y, dx, dy, pressure) local t = { id = id, x = x, y = y, dx = dx, dy = dy, p = pressure } table.insert(touches, t) end local lg = love.graphics function love.draw()...

AFAIK you can put whatever you want in the folder with the LOVE exe and it will be included in every project you make, so long as you require it. I'd avoid this though because when/if you want to share your creations, you'd have to copy the files into your project directory before you zip it up or n...

The problem lies in the hardware.

I'm not entirely sure with pairs/ipairs(I try to avoid it anyways (If I recall, in terms or speed it goes: pairs -> ipairs -> numeral iteration) ), but you shouldn't remove table items inside an iteration, unless you are traversing backwards. -- It would be fine for things like: for i, e in ipairs(e...

I got it... The problem was that after a bullet hits an enemy, the bullet is removed, but you didn't return from the loop after. So the next iteration it uses the next enemy but the bullet is already gone. Replace the loop with this: (also removes the need for the nope variable) for i=#bullets,1,-1 ...

The forum offically broke...