but it doesn't stop there... you can also set up a __call function in the metatable and then use the table the same way as a function (while still keeping all its other awesomeness): t={} t.note='associative arrays' meta={__call=function(self,x) print(self.note..' and metatables are '..tostring(x)) ...

daveberk: There are a host of other hardware architectures that would be nuked by this (PPC32, PPC64, ARM, etc) - nothing kills portability like hand coded assembly... But the main point stands: the biggest load in most games is already taken by external libraries that would get no benefit from LuaJ...

As far as love goes, it seems almost pointless. Most of the time game speed is limited by the graphics, sound and physics - all of which are provided by precompiled external libraries (SDL, OpenAL, Box2d). LuaJIT gives no benefit at all to this situation. For the tiny fraction of lua implemented gam...

The fine print is quite clear: LuaJIT only works on x86 platforms (because of hand coded assembly).

If this becomes a part of LOVE, it will cut off a significant degree of compatibility...

rofl... I was just so excited that I stopped reading after 'platformer'.

Not looked at 0.6 yet, but (in 0.5 parlance) maybe something like:

another good lua reference: http://pgl.yoyo.org/luai/i/_ You could combat gaps by: 1) making your images overlap a little (so a bit of shift is ok) 2) placing images relative to each other. eg: img1 at img1.x, img2 at img1.x+img1.width, img3 at img1.x+img1.width+img2.width, etc 3) use a package to h...

Opens a black screen that does nothing, will not respond to input.

No errors reported on console, same console output as when I run a working love file (eg no.love).

(running on PPC debian stable, love 0.5)

There are different kinds of cheating in different kinds of game... With a good (read paranoid) client/server system, each client only gets fed data the player is allowed to see, and only supplies the server with each player's commands... all processing/simulation is done (or mirrored) on the server...

The rate of growth is very small when reabsorbing, so if you only do it a bit, you will not notice. I observed the effect by: 0) absorb everything on level 1) zoom around, emmitting lots of bubbles (down to half your size) 2) collect them all again 3) repeat quite a few times ... until ..... 4) even...

Please forgive my bluntness, but for a system like love (which already provides a callback environment), and a language like lua (with coroutines), what is the point of LuaGravity?