It looks good. I've some small comments on the player.lua file, which is the one I reviewed.
There is some unnecessary repetition, due to the use of a "magic number" for the current animation. It needs a comment to be understood - the following code repeats several times, changing the image, the number and the comments.
Code: Select all
if self.direction == 1 then --(Direction 1 => still left)
self.image = playerStillLeft
--draw player
love.graphics.draw(self.image, newX,newY,0,spriteScaleX,spriteScaleY,0,0)
end
The images are stored on different variables:
Code: Select all
...
local playerStillLeft = love.graphics.newImage("media/MegaStillLeft.png")
Also, you make a difference between the "standing still" and "running". The former is achieved with a "normal image" but the later needs an "animation". Try not to have these special cases. I mean, use an animation for everything! The still animation can simply be one frame.
Once you do that, you can use a string for the player direction: player.direction = "StillLeft" instead of player.direction = 6 . If also a table for the player animations instead of a bunch of variables, you can get rid of all those ifs:
Code: Select all
...
local playerAnimations = {}
playerAnimations.StillLeft = newAnimation(...)
...
self.animation = playerAnimations[self.direction] ---- > this is the important line
self.animation:draw(newX,newY,0,spriteScaleX,spriteScaleY,0,32)
Also, try to use love.keypressed and love.keyreleased instead of love.keyboard.isDown . The usual way of doing this is by adding specific boolean flags for your player:
Code: Select all
function love.keypressed(key)
if key=="right" then
player.wantRight = true
end
...
end
function love.keyreleased(key)
if key == "right" then
player.wantRight = false
end
end
Use those variables in the rest of the code. Instead of this:
Code: Select all
if love.keyboard.isDown("right") then ...
Do this:
I know this looks cumbersome in principle. The good thing about it is that your player movement code now depends on those variables; it doesn't depend on the keyboard any more! Later, if you want the player to be able to change the control scheme (to use another set of keys, or a joystick) you will not have to meddle with the player movement code at all; just make the joystick or the new keys set the player.WantXXX variables.
Another advantage is that you can use the same code for enemies; you can have a "think" phase where the enemies set their "want" variables - (enemy.wantRight == true) and a "move" phase in which they move accordingly with their desires. You can even allow a second player to move the enemies without much trouble!
So it's a bit more work, but the benefits are huge!
That's all I could think for now. Regards!
, I’ll definitely change the way I address each animation, using a string makes a lot more sense, also, I’ll be using animations for most of the players actions – that’s a good suggestion! 
