[Wow. Some actual information from me. Enjoy! Or at least pretend to enjoy!]
Making a tileset
Before your tileset becomes an actual tileset you have to draw it. But it’s not that easy of course, there are several guidelines that newbies and masters alike must keep in mind:
Tilesets have to be 320 pixels wide.
No more; no less. JCS will give you an error when you try to compile the tileset if it isn’t 320 pixels wide.
Each tile is 32 pixels by 32 pixels.
Surely you have used JCS before.. if you didn’t: Go use it and become a master at it!! ;) When you are making a level and are picking something from a tileset, each block you take is called a tile. They measure exactly 32×32 pixels.
Tilesets should be a multiple of 32 pixels tall.
If you know just about any mathematics, you should have noticed this: If the tiles are 32 pixels tall, then the height of the tileset must be a multiple of 32. If it isn’t (I.E. 300 pixels tall), then JCS will automatically delete the bottom pixels untill it is the next lowest multiple of 32 (In this case the next lowest is 288. That means the bottom 12 pixels will be deleted!!).
The image must be in 256 colour.
For gameplay performance and other reasons, the image must be in 256/8-bit colour/indexed mode/paletted, etc… This means you can use up to 256 colours in your tileset. However… many of these colours cannot be customized to suit your needs.. but we’ll get into that in more detail later.
Any colour in palette positions 0 or 1 is transparent.
If colour #0 is black, than all pure black you draw will become transparent!
The top-left tile will automatically be made transparent!!
Do not put anything (useful) in the top-left tile, for it will automatically disappear once compiled!!
Save your images in you “Jazz2/Tiles” directory
This is where JCS looks for the files. It should be self-explanatory.
1024 tiles is the max in v1.23.
You can only have 1024 tiles in your tileset. I’ll take a look at this next week probably when I expand on this article. I believe 1.24+ (TSF or higher) can handle 4 times this amout: 4096!! However… do not compile your tileset in TSF unless you absolutely have to. It’ll save the community a headache or two. ;)
To walk through, or to walk into/walk on? That is the question which is answered by masks.
Masks are the optional part of making a tileset, but it won’t feel right if you don’t have one.
There is a simple way to make a mask:
-Save your tileset as a different name (i.e.: mytileset_mask.bmp).
-Erase (colour over with colour #0 or #1) all stuff you want to be able to walk through (like a flower or a rock or something).
-Smooth it out! Bumpy/rolling ground is okay, and even adds a higher sense of realism to your tileset. But jagged edges are a big no-no. The player will get caught in them and make (that part of) your tileset unuseable!
If you do not use a mask
If you don’t use a mask, then all non-transparent stuff in your tileset will be masked because you’ll have to use AUTOMASK. The only times you should use automask are:
-When you’re beta-testing your UNFINISHED tileset
-If all tiles in your set are smooth
-There are no tiles that you want the player to be able to walk through.
If you want to use automask, then I can’t stop you. But try to make a mask anyways. :p
I’ll probably take a couple bits of info here and go in deep. Maybe even have some images if I can get Fquist to add that feature! ;)
Eat your lima beans, Johnny.