Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(+2)

I think this is a good tutorial. I appreciate the shoutout to palettefade. I may do some poking around later to make sure the col module routines play nice with how palettefade does things, I think they SHOULD but I can't check at the moment. The col module definitely looks handy!

I also think the explanation of the palette and how it's laid out is handy, since I have seen people get confused about how the patterns and colours relate. One thing that's been unclear to me is the difference between pattern 1 and pattern 47, since they're both solid black. The explanation of the difference between pattern 0 and 32 was handy, but I'm guessing it works a bit different since there's no "one is transparent and one isn't" difference with the blacks.

Another thing I found was handy was the explanation about how animated patterns work. I am wondering though, is it possible to use two colours in an animation sequence? The example just sets it to a solid colour, but you could do some simple colour animations if you could have it cycle.

(+2)

There isn't really an observable difference in the behavior of patterns 1 and 47 apart from the fact that 1 is "a texture" which can be inverted and 47 is a "a color" which cannot. I suppose it's sort of a puzzling appendix from a certain point of view. Pattern 47 cannot be selected to draw with manually in either color or 1-bit mode; the "white" swatch on the toolbars normally selects pattern 0, but in "Transparency Mask" mode the same swatch is pattern 32, while erasing or right-click fills still produce pattern 0.

It is entirely possible to use multiple solid colors in animation sequences. I demonstrate this in the demo clip of the AnimEdit contraption; I'll add a brief note to make this clearer.

(+1)

I remember when I was writing the crossfade function in palettefade I was kind of trial-and-erroring it a bit in terms of seeing if white and black would come out as 0 and 1 or 32 and 47, since I was having to do pixel by pixel stuff when comparing the two images - worked fine in the end though. Good to know the internal logic!