Again the $’s tell the game to divide these images into frames 3 columns wide by 4 rows tall, in the large trees case they are 160x160 blocks (5x5 of 32x32 pixel squares), and the bottom one is 160x224! (5x7 of 32x32 squares) (yep, you can make them rectangles) (this is particularly helpful so you don’t have to re-save and re-import a map anytime you want to change something) The top image is my $large_tree.png and the bottom one is my $palm_tree.png. Time to get weird.įor my Poison Ivy level I needed some BIG trees to make things look full, but I was also using up a lot of the second layer of tiles to make bushes and stuff, so how am I going to overlay complicated tree tiles over bush tiles? I could do Parallax mapping, OR I could make some funky tree events. Here I’ve blacked out the frames I wasn’t using to help me keep everything in the right frame, and again the grid is set to 32x32 pixels in photoshop, but without the $ in the title the game looks at it as 8 groups of 3 columns and 4 rows of 64圆4 frames. The $ still divides the image into 3 columns and 4 rows of frames for animating purposes, they just happen to be 64圆4 in these images. Now the grid overlay from photoshop is set to 32x32 pixels, but the game doesn’t care about that. Without the $ the game divides the image into 8 groupings of those 3x4 sections, making the image 24 frames by 8 frames. The $ in the title tells the game to divide the file into three columns and four rows of frames. The grid you see over them is from photoshop, they aren’t actually in the file, but it’s useful to see how the game divides them up. These images are the kind you’ll find most of the sprites in VX ace set to. Ok the thing I was originally going to post was actually a confusion on my part between real_x and x in scripting, so let’s ignore that for now and give some visual aids. Just be sure to make it exactly the size or you’ll get animations not working properly. The engine will then change the sheet to fit the 4x2 layout. Thus, if you want to make a sheet of sprites that are a different size than the norm, just make sure to have four instances of animation across and two instances down. It takes the width and says ‘break this into 12 equal parts’ then takes the height and says 'break this into 8 equal parts’ and that’s what gives the cell heights/widths. What this means is that it’s not about the width or height of the cells but that of the sheet. It’s a subtle difference, but it makes things a hell of a lot easier. That is, instead of telling itself ‘this is 32 x 32’ is says ‘this sprite sheet, when divided into four across and two down, becomes a 32 x 32 grid of animations’.

This response from Liberty on the forums explains it better than I can:Īce (and VX) reads sprite sheets without an $ in front of their name as two lines of four animation sets.

Bigger character sprites rpg maker mv