Hi! GitHub : https://github.com/Felix-Du/Controllers.lua Download : https://raw.githubusercontent.com/Felix-Du/Controllers.lua/master/controllers.lua ReadMe : https://github.com/Felix-Du/Controllers.lua/blob/master/README.md So, this is a small project I've worked on, and I'm at this point where it ...

His version is 0.9.0:

somebodyelse wrote:

Code: Select all

function love.conf(t)
    t.identity = nil                   -- The name of the save directory (string)
    t.version = "0.9.0"                -- The LÖVE version this game was made for (string)
    [etc.]

Azhukar wrote:No.

Ok, sure, if you don't plan on putting a level editor or custom levels or anything like that, it's a fine option.

Try this:

You can directly load lua files and use those as data storage. main.lua local level1 = love.filesystem.load("level1.lua")() print(level1[2][1]) --prints 2 level1.lua: local leveldata = { {1,1,1,1}, {2,0,0,1}, {1,1,1,1}, } return leveldata Bad idea. If the user download the file from an un...

Yeah, the wiki method is way better than shaders here: It's faster and more reliable.
And to do a circular gradient, you can generate an image that look like a "ball" with imagedata:mapPixel(), then draw it where you want.

But selecting good algorithms before implementing things has nothing to do with optimizaiton. It has to do with a f-ing common sense. Well, yeah, I agree. While spritebatching boosts up your rendering and it's a common practice to use it, LuaJIT is a big time tradeoff stuff, You mean the fact that ...

His point was that the FPS you gain when optimizing aren't worth being done at the beginning of the development. Having a fun, polished but slow game is better than half a tech demo that run fast but not very polished and fun. If you really want to optimize, then you can use things like LuaJIT or Sp...

Cool.
The main window need a scrollbar. And progress bars for downloads!