One reason would be safety. Lua code would need to be sandboxed, or people sharing modified saves could potentially run untrusted code through them. Right, that's one of the few cases. Controlling the environment (using setfenv) while loading a game might help in situations where additional safety ...

Use Lua ... there's hardly any sane reason not to do so for this kind of data.

Working on a city builder ... and having a shitload load of fun doing so ...

For tilebased levels, have a look at www.mapeditor.org - and IMO the best format is Lua itself, data description is actually the origin of the language.

Since I would've liked to read this when I started out using ads, I will share some of my experience. I currently have an endless runner installed on 3000 devices, from which I play an intertitial ad every 5 deaths, generating from 0.10 to 2.00 USD a day, sometimes it peaks at 4 USD on one day. I'v...

It's a per vertex attribute, so yes, you can use different values for quads in the same batch.

Ah yeah, I just guessed the solution as that was the obvious problem with regards to the height. Here's a kind of "fixed" version that does remotely what you aim for (only quick fixed in terms of, a hacky version to show off how it's basically down, it's not a version to keep building upon...

If you solved your problem with one line of code and you're questioning your solution with 5 lines of text in a forum message I'd say, you've already done a decent job before posting. Seems like you found a solution, it's as pragmatic as possible (which is IMO really good) and there's actually no re...

You just have a typo (I guess) as, in Map:draw you use the height instead of height_size to calculate the yoffset and color gradient of your tiles.

I use a helper function like this in such situations local function loadImageFromPath( filePath ) local f = io.open( filePath, "rb" ) if f then local data = f:read( "*all" ) f:close() if data then data = love.filesystem.newFileData( data, "tempname" ) data = love.image....