The oscillating field of view thingy makes my heard hurt But what should I do? Remove the oscillation effect. In real life the field of view does not change if your character does not move. The way you implemented this is seriously strange, I have never seen it before. I guess you aim for a"to...

The oscillating field of view thingy makes my heard hurt

I read somewhere that it was faster if you assigned variables then called them as opposed to just calling them. I don't know if it's true or not, or if it even really impacts it that much, but... :P Assigning the table to a variable is completely pointless here and only makes your code more verbose...

Instead of creating a separate thread I will ask a very related question here. Imagine I have something like this: A = {B, C, D, a, b, c} B, C and D being tables themselves and a, b and c being strings and numbers, all of them only referenced by A. Will the garbage collector correctly get rid of th...

Updated my customized SciTE to the newest version and made minor configuration changes. Keywords are no longer in bold and the fold margin background color was changed. I also made an additional color theme because I wanted a change. The new theme is called Nightshade and is based on IntelliJ's Drac...

I have always used one big texture which contains the characters in all colors. You can easily calculate which part of the texture to blit with the variables being the character code and the color id. Looks like this in my current code: self:DrawTile( self.drawColor * self.tileset.dimensions.width +...

You can easily test whether the GC is the issue or not. Just add.. collectgarbage("stop") .. to love.load(). Personally I cannot reproduce the issue, with or without the GC running. The game runs at 996-1000 FPS all the time if vsync is turned off and no game will ever run faster. I think ...

The most important thing is to organize you code into modules instead of randomly stuffing the global namespace like you do currently: http://lua-users.org/wiki/ModulesTutorial Don't use globals in general unless you have a damn good excuse i.e. your variable declarations should almost all start wit...

There are quite a few reasons to use them. * Handling side effects E.g. Character.Damage = function(self, damage) self.damage = self.damage + damage if self.damage > self.health then self:Die() end Game.charactersDamagedThisTurn:Add(self) etc.. end * Implementing attributes whose effective value is ...

Looks nice!

No frame rate issues at all. I get ~500 FPS with Löve (64-bit Windows) and ~400 FPS with Löve+LuaJIT (32-bit Windows).