As I said earlier, however, the bytes are split to accommodate for 2 cells. This would cause problems with our formula as we still wouldn't know which "half" of the byte goes for the cell. Simple solution to fix this is to write a small function to decide whether your column number is odd or even. If it's even, you would take the first "half" of the byte. If it's odd, the second "half". This, of course, depends on your grid and if the column and row values are 0 based or not. You'll have to mess with the odd and even bit to get the correct value for each cell. This can be quite fun to see some of the results when you mess up your algorithm. You get some strange looking images.
Now that you have the offsets, the palette information, and a drawing function, you might be asking yourself what's next? Well, we need to name these bad boys. The pattern name information starts at 822h with the town name. The player name starts at 838h, and lastly, the pattern name starts at 84Ch.
So we have the offset, the palette, the drawing, the name, and now we'll have the pro vs. simple design. This one byte is at 870h in the pattern data. 00 is simple and 01 is pro. A very simple concept.
Here's a little nugget of information courtesy of DsPet. This feature isn't in the current public version of PattView (and I don't intend to add it). It's the stored patterns at the pattern shop. The algorithm used to get to these patterns is as follows:
The patterns are in the standard format (880h bytes), and follow all of the same rules as the above patterns. So thank you, DsPet. Nice little bit of information there.Code:$74060 + $22020 * iPlayer (iPlayer = 0, 1, 2, 3)
PattView Delphi source code, fully commmented, available in the Game-Hackers VIP section!
Also available exclusively in Game-Hackers VIP:
PattViewX
-Completely rewritten PattView release
-User-friendly, compact style
-Now supports 316 patterns, with Able's storage patterns (as opposed to 60 in PattView v2.1)
-New, more accurate pattern rendering
Reply With Quote
