Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit)

Well, as long as the width is divisible by 4, you can cut it in a grid. Which is the case here. I didn't find the one you mentioned that is 161px X 85px, which one is that?

On my side, all of their widths are multiples of 2, so they are divisible by 4, hence usable in a grid system.
The pack provides the sprite only, not sprite sheets, or atlases. The sprite sheet creation is to be handled on your side, maybe the unity tool is not a good fit with the Magicavoxel exports, there surely are other tools out there for sprite sheet creation.

Maybe that can help : 

Here's how Unity's default sprite slice handles all the road chunks: https://imgur.com/a/NRp4YxM

You can tweak it so it includes a larger border, but then you have gaps between your tiles you have to hack around.

More importantly, there are inconsistencies in size even among things that should be on the same grid. For example the sidewalk_chunk is 89 pixels tall when sliced to remove all transparency. This has the same not-divisible by 2 issue, but it's also 4 pixels taller than the road chunk. So putting them on the same grid doesn't work well.

I understand, but the sprites that get eported out of Magicavoxel seem to not be usable directly with the Unity sprite tool. That's the thing. So you need to do the sprite sheet by yourself, using another tool/method, or find a way to use it as is.

Yep, understood, and appreciate the quick responses.