03-12-2010, 06:12 PM
I would say that you would need to know what image you would have to load for that level background, foreground, and maybe enemies sprites if you know you won't be going to use every enemies in one level. That way you would see speed gain, which is very important to save when using software acceleration.
How about a double array of tiles that would store your data for that level? I've done that for my "level editor" in my little car game.
struct tile
{
int clipx,clipy,type;
//clip would make you know where to clip in the image file
//type would be similar to what SengirDev suggested
};
And you would make that double array with a pointer on a pointer or using a vector...
**tile a_tile;
But you should def make an editor... Unless you're going to type a thousands of random numbers in a text file. XD
How about a double array of tiles that would store your data for that level? I've done that for my "level editor" in my little car game.
struct tile
{
int clipx,clipy,type;
//clip would make you know where to clip in the image file
//type would be similar to what SengirDev suggested
};
And you would make that double array with a pointer on a pointer or using a vector...
**tile a_tile;
But you should def make an editor... Unless you're going to type a thousands of random numbers in a text file. XD