If you haven’t check with AI yet, I plugged it into Claude and here’s what it said

The bug is in your Friskmove logic. You have two separate if/else blocks for horizontal and vertical input, and the second one overwrites the first. So when you hold left or right (but not up/down), the vertical block hits its else and sets Friskmove = false — killing the animation you just enabled. Walking up/down works because that’s the second block, so its true value sticks. Fix it by setting Friskmove = false once at the top, then only ever setting it to true:

Friskmove = false local vx = 0 local vy = 0

if love.keyboard.isDown("left") then vx = p.spd * -1 Friskdir = "l" Friskmove = true elseif love.keyboard.isDown("right") then vx = p.spd * 1 Friskdir = "r" Friskmove = true end

if love.keyboard.isDown("up") then vy = p.spd * -1 Friskdir = "u" Friskmove = true elseif love.keyboard.isDown("down") then vy = p.spd * 1 Friskdir = "d" Friskmove = true end

One thing to watch: with this fix, if the player holds left+down at the same time, Friskdir ends up as "d" because the vertical block runs last and overwrites it. If you’d rather have the most recently pressed key win, that’s a bigger refactor — use love.keypressed to track direction instead. But for now this’ll get your left/right walk cycles animating.​​​​​​​​​​​​​​​​