[SOLVED] Tiled map generator problems

[furi]

*fixed*
by myself. ...
Despite the fact that the generator isn't necessarily the cleanest, best-looking one ever, I got it done. That's an accomplishment quite big for me.

[kikito]

You have had lots of issues with tiles lately.

I can't debug your code just now, but I'm going to leave my tile tutorial link here in case it helps you:

https://github.com/kikito/love-tile-tutorial

It handles the things you are trying to do (tiles encoded inside a multi-line string) in a very straightforward way.

Regards!

[furi]

You have had lots of issues with tiles lately.

I can't debug your code just now, but I'm going to leave my tile tutorial link here in case it helps you:

https://github.com/kikito/love-tile-tutorial

It handles the things you are trying to do (tiles encoded inside a multi-line string) in a very straightforward way.

Regards!

Hey, thanks. I'll look into it.

EDIT: Oh, yeah, by the way: It's not necessarily drawing the tiles that's the problem. It's generating them accordingly.

You see...

Code: Select all

#####
#...#
#...#
#...#
#####

this? This is a 5x5 block. I have to generate maps that contain randomized 5x5 blocks (check the "grids" table above) that fill up the map. With the linear way text works, though, it's a real hassle.

[kikito]

I think you might be using the wrong tool for the job.

Strings are easy to edit, but difficult to work with. Specially in Lua.

Tables are easier to work with, but difficult to edit (or I'd say less easy to modify than strings).

Solution: Put your data into strings, but transform it into tables as soon as it leaves the "editable zone". If you need to, transforming a table into a string isn't that complicated (using table.concat really helps there).

[furi]

I think you might be using the wrong tool for the job.

Strings are easy to edit, but difficult to work with. Specially in Lua.

Tables are easier to work with, but difficult to edit (or I'd say less easy to modify than strings).

Solution: Put your data into strings, but transform it into tables as soon as it leaves the "editable zone". If you need to, transforming a table into a string isn't that complicated (using table.concat really helps there).

I'll try. I'm not the most experienced with tables, though. Thanks, anyways.

EDIT:

Code: Select all

gen={};
mapg2=string.gsub(mapg,"\n","");
x = -1;
for s in mapg2:gmatch"." do
	x = x + 1;
	y = muldown(x,mapx/5);
	for yy=0,4 do
		for xx=0,4 do
			table.insert(gen[y*5+yy],x*5+xx,grids[s+0]) --[y*5+yy]
		end
	end
end

Table expected, got nil.
I'm really not sure how to fix this.

[tentus]

I think you might be using the wrong tool for the job.

Strings are easy to edit, but difficult to work with. Specially in Lua.

Tables are easier to work with, but difficult to edit (or I'd say less easy to modify than strings).

Solution: Put your data into strings, but transform it into tables as soon as it leaves the "editable zone". If you need to, transforming a table into a string isn't that complicated (using table.concat really helps there).

I'll try. I'm not the most experienced with tables, though. Thanks, anyways.

EDIT:

Code: Select all

gen={};
mapg2=string.gsub(mapg,"\n","");
x = -1;
for s in mapg2:gmatch"." do
	x = x + 1;
	y = muldown(x,mapx/5);
	for yy=0,4 do
		for xx=0,4 do
			table.insert(gen[y*5+yy],x*5+xx,grids[s+0]) --[y*5+yy]
		end
	end
end

Table expected, got nil.
I'm really not sure how to fix this.

Shouldn't gmatch be a function?

Code: Select all

mapg2:gmatch(".")

In general, I would advise being internally consistent with how you use string functions. If you use mapg2:gmatch(".") in your for loop, it would generally be a good idea to also use mapg2=mapg.gsub("\n","") two lines earlier, just so that you don't confuse yourself down the road. Hope that makes sense.

Also, s+0 is kinda odd, you can just use s.

[bartbes]

Shouldn't gmatch be a function?

Code: Select all

mapg2:gmatch(".")
--is equal to
mapg2:gmatch "."

[tentus]

Shouldn't gmatch be a function?

Code: Select all

mapg2:gmatch(".")
--is equal to
mapg2:gmatch "."

Huh, I did not know that. Is gmatch "." equivalent to gmatch"." ? (His does not have the space yours does).

[bartbes]

Yes, whitespace barely plays any role in lua's syntax.

Anyway, let me explain this trickery: when there's a single argument, and that argument is a literal of either a string or a table ("literal table" meaning {stuff}, not a variable name), the parentheses aren't needed. (so, ipairs{1, 2, 3} is valid as well).

[tentus]

Yes, whitespace barely plays any role in lua's syntax.

Anyway, let me explain this trickery: when there's a single argument, and that argument is a literal of either a string or a table ("literal table" meaning {stuff}, not a variable name), the parentheses aren't needed. (so, ipairs{1, 2, 3} is valid as well).

Good to know! Man, I'm learning all kinds of stuff today.

So in the case of a two argument function (if he hadn't used mapg2: but instead gone with string. ) the trickery wouldn't have worked, right? And I assume that the same trick doesn't work with boolean or number arguments, since you didn't list them?