The screenshot you're looking at is me testing 2 different things. I chose this stage (I didn't make it, BTW) because it had an animation short enough that I only had to code things for 3 images. One of them I'd use with Ghost of Starman (sequentially showing/hiding BG images to make an animated animation) and the other is the heated room effect from Metal Pirates Room, which was originally coded to work with a tiled BG from
Cathedral Entrance (it was the first room I saw from
Business Center ). This stage was one of the worst things I could've chosen to test this effect on, BTW. Because the other animation I added is barely noticable due to the BG layer changing between the 3 images.
Spoiler: I'll stop there for now and show/tell you something else interesting: (click to see content)
Here's what I've learned about how to code these kinds of effects (thanks to Samchay's stage):
1. If you can reposition the camera or BG layer to see the movement pattern, great. Otherwise, you'll have to go find addresses that affect the BG tiles and mess around with them until you can hide a column of tiles. This is so you have something to compare against what you've done, because coding multiple lines and having it not match up sucks ass (I know. Man, do I know).
2. You'll need to put a RAM watch on the X position of 1 to 3 lines. If the movement pattern's a simple one, you'll be getting your position values from the 1st line (I suggest starting at the furthest point left or right in the movement. It's less confusing). If the value jumps to the F0/F000 range after decreasing to 00/0000, you should either make the value display as signed or make a mental note that FF/FFFF = -1, FE/FFFE = -2, etc.
3. The 2nd and 3rd addresses are to help you figure out how much the animation is offset for each line. Example: For the Action 1/1st line, positions 0 and 1 are 3 frames (I set it up as 6 1 frames). For Action 2/the 2nd line, it's now position 1 with 2 frames, and position 2 with 2 frames, which means the animation you're coding gets offset by 4 for each line. So you'd have to cut/paste 4 lines from the top of your list to the bottom of each subsequent copy/paste as you work your way down the rows of lines.
4. Did I mention timings? You'll also be getting those after you get all of the positions the line can move to. The safest method is to not worry about condensing the list of positions/timings and do a bunch of 1 frames, though sometimes they're set up in a way you can actually condense it all. Recording macros in Notepad++ will make this process easier for you.
And about that other thing: There was a dual-meaning behind that hint. The first was you noticing I altered the image through comaparing the two. The second? You literally being able to see what it is by using both images.
