Voted! Good luck~

I quite like it, but I'd also like to see mouse sliding. It's certainly a more intuitive mechanism.

Optional representation allowed through sprite.setUpdate. sprite:setUpdate(function(shape) love.graphics.setColor(255, 0, 0) shape:draw 'fill' love.graphics.setColor(255, 255, 255) end) This will create a red collision polygon under the sprite. This allows for full customization of the collision box.

I only enabled the collision polygons visibility for a demonstration. If you actually use Sprites, the collision polygons are invisibile.

Ah ha! That looks much more accurate. I've also gotten it to work in ISO. That is the resulting collision polygon.

Was having trouble navigating through your source code, so I made a little mockup. It's not using ISO, but it shows my idea. Use the arrow keys to move and ESC to quit. I put it in, however in sprites whose width is greater than their height, the collision area is way too large. Here is the commit .

Collision detection is in ISO (complements to HardonCollider). Line 81 and 120 in this file decides what portion of the sprite is checked for collision. Right now it is using the entire sprite, but I'm interested MarekkPie's solution if you'd like to implement it.

MarekkPie wrote:I don't know if you want to to the full size on the sprite. The "grounding" part was to try and coincide with the z-indexing of an isometric map, since it's more representative of their place on it.

Then how much of the sprite should detect against collision?

I'll likely end up using HardonCollider and represent each Sprite with a rectangle of its dimensions. Sounds simple enough

From what I can remember about the isometric games I played (read: Diablo II), they seemed to using a ground-based ellipse to test collisions against. Since your viewpoint is high enough, you can probably skip the ellipse math and just use a circle. From there, you may be able to skip keeping the c...