function my_func(someArg) local someArg = someaArg or 'someDefaultValue' end I think you mean someArg instead of some a Arg :) Am I right that the first version should use local, but not the second? You don't need to declare the local in the first example. In fact some languages (like Python I thin...

it would be nice if Love let us change that like it's possible with Box2D You can't change most of Box2D's constants without rebuilding the entire library. Over the years I've noticed that you don't really need to change those constants 99% of the time. In general, 8 vertices is a lot for a convex ...

I would humbly point out that if your game is going to be as complex as you've described, tile transitions are going to be your least worry.

I think your general approach is too complicated. I would suggest getting your mind off the project for a few days and coming back to it with a fresh look. First off, if this is supposed to be a prototype, you should focus on the gameplay instead of the rendering implementation. Second, I'm not sure...

Interesting results. I do have a couple of criticisms however: for n=1,cycles do local test = CLASS.test This is an extra assignment which is not present in the "localize_method_no" test. I would change it to: local test = CLASS.test for n=1,cycles do - Strangely, custom unpack function is...

I understand. It's faster but not so fast that you have to care unless you're doing lots of calls to the same function in one specific place. Yep, for example: for i = 1, 100 do love.graphics.print(i, i*10, 10) end Would be slower than: local print = love.graphics.print for i = 1, 100 do print(i, i...

I think you mean: The biggest performance drop in Lua that I've noticed is from creating unnecessary tables (for example in a loop) that get destroyed right away.

I noticed this when porting some code from the AGen engine.
Happens with integers as well as floats.

Check it out, I have a new demo of the AI system. The demo is a simple Asteroids-like game. The arrow keys move your little ship and Z shoots. Enemy AI code: local hit = ai:Sequence ( false ) hit:Push ( ai:ReceiveMSG ( "shot" ) ) hit:Push ( ai:MoveTo ( x, y ) ) local goal = ai:Parallel ( t...

Hey, that's pretty cool, tentus. However, I left a bug in the code while porting it to Love2D. In theory, map sizes should be power of 2 + 1 (513x513 instead of 512x512). Notice the commented assertion: --local pow2 = (nw - 1)/2 --assert(math.floor(pow2) == pow2) Also, the displacement variable (dis...