LÖVE

ivan wrote:Hi Lord Uber Dowzen.
Like coffee pointed out your topic title is a bit imprecise.
"Save system" usually refers to loading and saving user preferences, hiscores and progress.
What you're designing in this case I would call the "level file format".
A while ago a wrote someting you mind find useful:
http://love2d.org/forums/viewtopic.php?f=4&t=3323
It basically shows you how to save tilemaps as an ASCII file which is (usually) easier to edit than lua tables or serialization.

ivan wrote:Hi Lord Uber Dowzen.
Like coffee pointed out your topic title is a bit imprecise.
"Save system" usually refers to loading and saving user preferences, hiscores and progress.
What you're designing in this case I would call the "level file format".
A while ago a wrote someting you mind find useful:
http://love2d.org/forums/viewtopic.php?f=4&t=3323
It basically shows you how to save tilemaps as an ASCII file which is (usually) easier to edit than lua tables or serialization.

miko wrote: You can also study the sources of BoxBreaker:
http://love2d.org/forums/viewtopic.php? ... 7&start=20

coffee wrote:Your tile engine code needed a bit of work so I accidentally started organizing and improving (I think).

But then when I tried to load a full map table I noticed that you were table addressing and drawing the map at 0,0 and not at 1,1 ( natural starting value assigned on tables). So that complicated a lot my plans and I wanted to modify/adjust ALL your engine but neither I had more time neither this is my project and can't take you the pleasure of you doing it. ;D

So anyway take a look (or not) of the things I changed trying to improving it.

What I did:

- Changed placement of degug info from above map
- Instead of hardcoding 16 everywhere I created tileWidth and tileHeight
- Organized your code a bit creating some functions
- Instead of moving camera the hardcoded 8 pixels altered to tileWidth,tileHeight
- Added Wheelmouse to change the tile value

What I think you should continue to do:

- Adjust all your engine to work with map table starting at 1,1. That means start for cycles at 1 and adjust calculations and drawing to something like x*tileWidth-tileWidth, y*tileHeight-tileHeight.
- Load a full table "map = { values }" in map.lua directly instead of assigning piece by piece like you were doing.

Ahh... In map.lua you hadn't to map[0] = { }, map[1] = { } because you already were doing that to all rows in main.lua. I removed that lines in map.lua and you can see no need of do that...

So take a look too of Ivan and miko tutorials proposals and keep working. We are here to continue to help.

LuaWeaver wrote:It does not owrk. You never opened the file, and when I alter the code, so that file=love.filesystem.newFile("map/map2.lua"), and then I use file:open("w") file:write(strg) it returns with the erorr "File not open". Sorry, it doesn't work, and I can't fix it.

map = {
	{ 4, nil, 9, 9, 9 },
	{ 9, 9, nil, nil, 9 },
	{ nil, 9, nil, nil, 9 },
	{ nil, nil, nil, nil, nil },
	{ nil, nil, nil, nil, nil },
	{ nil, nil, nil, 9, nil },
	{ nil, nil, 9, nil, 9 },
	{ nil, nil, nil, 9, nil },
	{ nil, nil, nil, nil, nil },
	{ nil, nil, nil, nil, nil },
	{ nil, nil, nil, nil, nil },
	{ nil, nil, nil, nil, nil },
	{ nil, nil, nil, 9, nil },
	{ nil, nil, nil, nil, nil },
	{ nil, nil, nil, nil, nil },
	{ nil, nil, nil, nil, nil },
	{ nil, nil, nil, nil, nil },
	{ nil, nil, nil, nil, nil },
	{ nil, nil, nil, nil, nil },
 

Taehl wrote:Using nil will also make the # operator not work the way you want it to.

That being said, I personally like using nil for non-tiles, but I also use it with careful numeric "for" loops instead of pairs or ipairs.

miko wrote:

Taehl wrote:That being said, I personally like using nil for non-tiles, but I also use it with careful numeric "for" loops instead of pairs or ipairs.

Me too. Nil frees memory, all the other values are stored in memory. With large maps, it can make a difference - not only such a code takes less memory, but also is faster - there is no additional object which garbage collector traverses when trying to free resources. Still, for practical situations the difference is really small, so this is not critical anyways.