For a sine wave I think it'd be better to do it based on the time the bullet has been alive on the screen, not its x/y position. This is because you might have the bullet travel on a line, at a specific angle (ie. think a boss shooting sine wave bullets, directed at player's current position, from w...

Generally any time a bullet is updated (whether it's done by some object maintaining the bullets, or each bullet being its own object and updating independently), you simply apply the desired change in angle each game tick for a given bullet. How you go about doing that is up to you and your code.

If you can spawn a bullet that might swerve or curve, in a radial, sine wave or whatever other manner, you're basically already done. Next you just have to spawn a bunch of them at different positions, angles and timings. You could do reusable functions by hand for each pattern, enemy or boss type (...

Another approach I suppose would be to use stencils, but ultimately using shaders would be the better option.

This is a little issue that can happen with a fair few physics implementations that do not correctly handle "gliding" along the surface where multiple collision boxes might meet. I've had this exact thing happen with bump.lua, though you seem to be using box2d (love.physics). In principle,...

Automatically detecting quads in an arbitrary image like you're asking is possible (assuming you don't take "detect rectangles of certain color" approach with an image like darkfrei's post above), but it would have couple major limitations: (1) The quads would simply grab the optimum recta...

You're necroposting in a thread from 2014, so it's unlikely you'll get an answer from them. Basically thoughm you'll have to find out how to whitelist the .dll on your system. This help thread from Microsoft's support forums probably has steps for you to follow, assuming you are on Windows 10.

Consider the following as its own code, separate from the code you've been posting. testTable ={ { {x=1,y=1}, -- A {x=1,y=2}, -- B {x=1,y=3}, -- C {x=1,y=4}, -- D } } -- assign A and B to temp1 and temp2 temp1,temp2 = testTable[1][1],testTable[1][2] -- assign temp1's value to temp3, they now both re...

Assuming that at the time of the assignment, temp1 points to A, and temp2 points to B, then in the testTable A's position is overwritten by B. This does not mark A for garbage collection, because temp1 still holds onto A. After that when you modify temp1 (assuming it still holds A, and hasn't been r...

You're welcome, but I have to point out that these two lines are not equivalent: testTable[temp1.x][temp1.y] = temp2 temp1 = temp2 The first one reassigns whatever temp2 is holding into testTable[1][1] (basically replacing "A" with whatever temp2 holds). If that position contained a table,...