06-07-2023, 08:54 AM
Yes slicer/atlas spritesheet.
the 2 points that led me to take this decision are that I have had difficult to manage SpriteSheet with different sprites' dimensions.
You need map the spritesheet by a grid, but sometimes larger sprites are not a multiple of smaller sprite and so this way fails.
So it is very difficult loading properly the larger sprites without mapping each single sprite.
The other point is that you can choose and save as single image file only the sprites that you need, or the data of their dimensions so you can load directly them without loading all the sprites that are on the spritesheet.
![[Image: weapons.png]](https://i.ibb.co/f4D6RNx/weapons.png)
Surely if you use a standar spritesheet in which alla the sprites have standard dimensions (all the same dimension for example 32x32, or multiple dimensions of the smaller sprite for example 32x32 , 64x32, 64x64, 128x32,32x128 etc..) you can avoid using this tool if you work better with math calculations.
![[Image: boy-free-sprite-orig.jpg]](https://i.ibb.co/J3RPFqH/boy-free-sprite-orig.jpg)
the 2 points that led me to take this decision are that I have had difficult to manage SpriteSheet with different sprites' dimensions.
You need map the spritesheet by a grid, but sometimes larger sprites are not a multiple of smaller sprite and so this way fails.
So it is very difficult loading properly the larger sprites without mapping each single sprite.
The other point is that you can choose and save as single image file only the sprites that you need, or the data of their dimensions so you can load directly them without loading all the sprites that are on the spritesheet.
Surely if you use a standar spritesheet in which alla the sprites have standard dimensions (all the same dimension for example 32x32, or multiple dimensions of the smaller sprite for example 32x32 , 64x32, 64x64, 128x32,32x128 etc..) you can avoid using this tool if you work better with math calculations.