You are calling move() on every card, every frame. Inside that move function, you're checking for mouse collision with the current card and moving it to the mouse cursor if the mouse button is down while the cursor is over the card. You don't have anything in your code to ensure that only one card i...

It's pretty much as you said it, there's no more to it than that: You draw each character with the size, rotation, and position that you want.

Another traditional way to do it is to define the table to be returned at the top and then define the functions you want to export in that table to begin with. This is a bit shorter and saves you from duplicating the names of everything. Perhaps you like the look of that better. local M = {} -- By a...

I'm surprised no one mentioned Gravity Circuit here yet. It's a pretty full-sized platformer made with Löve: https://store.steampowered.com/app/858710/Gravity_Circuit/ The engine is good enough. It's more or less as fast as anything else, and since it's a fairly low-level framework, it basically nev...

It's more of a "framework". There is no built-in scene tree, game objects, draw ordering, GUI system, or anything like that. There are some main lifecycle callbacks (load, update, draw, etc.) and input callbacks, and then various modules with functions to help you do what you want. See: ht...

Here's another demo that actually uses physics bodies.

Aha, I think I see. So it's something like, if you had concentric circles, where the largest overlaps all smaller circles, and you want to know which "ring" a certain object is in. In that scenario it would simply be the smallest circle that the object is still overlapping. You just need t...

Sensor shapes will not cause preSolve and postSolve callbacks, only beginContact and endContact. Also one of the bodies must be dynamic to get any events at all. Other than that, overlapping sensors should work fine. I don't quite understand what you are trying to do from your description, maybe you...

You're welcome. I'm glad that helped.

Take a look at the documentation for love.graphics.newShader again. As the error message says, you need to provide either a "position" function or an "effect" function (or both). You are instead defining two "main" functions in the same string. Additionally, if you want...