;taken from prg011.asm

;(My notes) XY position placement data. These are used to mark where the Airship lands on the map. Note: BOTH ground and sky portions of W5 use the same map. 

;(My notes) Airship is stored and buffered in VRAM as OAM. There are three separate ship attributes which can be called at random as to where the ship will go. After 5 movements, the ship stays in place.

MAT_Y_W5A:	.byte $80, $80, $40, $80, $40, $80	; World 5 Airship Y Set 0
MAT_Y_W5B:	.byte $40, $80, $80, $60, $40, $20	;                   Set 1
MAT_Y_W5C:	.byte $60, $40, $20, $60, $40, $20	;                   Set 2

MAT_X_W5A:	.byte $A1, $61, $C1, $A1, $C1, $61	; World 5 Airship X Set 0
MAT_X_W5B:	.byte $C1, $61, $A1, $80, $80, $20	;                   Set 1
MAT_X_W5C:	.byte $80, $80, $20, $80, $80, $20	;                   Set 2

; Map_Airship_Trav selects which world/set to use
; Map_Airship_Dest selects which index within to use (0-5)

MAT_X_W5A:	.byte $E1, $61, $C1, $E1, $C1, $61	; World 5 Airship X Set 0
MAT_X_W5B:	.byte $C1, $61, $E1, $80, $80, $20	;                   Set 1
MAT_X_W5C:	.byte $80, $80, $20, $80, $80, $20	;                   Set 2

;Do you see the three $E1 on the first two lines??? They were originally $A1. Wow...

PRG003_B1D7: ;bubble OAM
	; Bubble appears at Y + 3
	LDA <Objects_Y,X
	ADC #$03
	STA SpecialObj_YLo,Y
	LDA <Objects_YHi,X	; Bug? They don't apply the carry (ADC) here!
	;;;;ADC #$03 ;this is missing!!!!
	STA SpecialObj_YHi,Y

PRG010_CEBF:
	; A Player pressed 'A' but they were not on top of each other, so no 2P vs...

	LDA <Pad_Input
	AND #PAD_A	
	BEQ PRG010_CEE1	 	; If Player is not pressing 'A', jump to PRG010_CEE1

	LDA <World_Map_Tile
	LDY #$0a	; Y = $1A (BUG!  Map_EnterSpecialTiles is much smaller than this, should be $0A!  Causes some bytes used for palette data to be considered!)

;;;;change it to $1A

;;;;;;;;;; Map_EnterSpecialTiles: While the intended function of this LUT works correctly, a bug in the check code examines up to $10 bytes ahead from the actual end of this array. The data is loads is from palette arrays, but treated as tiles, meaning that there's a lot of tiles that will be enterable on the map that shouldn't be. But given the rigid structure of the map, this generally is not a problem, which likely explains why it went undetected despite other bug fixes. Of note, however, are a few tiles that are peculiar that were included in the list such as an alternate coloring of the World 5 spiral castle (never used), a path segment which goes nowhere (??), and perhaps most interesting, the dancing flower from World 4 (!!) It's always possible of course that these were mistakes, leftover from some kind of code/graphics reorganizing at some point, or maybe there really was to be some kind of plant-themed levels.

LoadLevel_LittleCloudSolidRun:
	LDX #$01	 	; X = 1 (use TILE1_JCLOUDSOLID)

	; BUG!! This jump will always fail, dropping into the table below!!
	; The table is misinterpreted as a BIT xxxx instruction followed by
	; a BRK, which triggers the NMI but ultimately is MOSTLY harmless...
	; The return is in the middle of the LDA LL_ShapeDef which is now
	; misinterpreted as an "ASL <$07"... in one trial, I got $CF as
	; the run length!  Big oops there Nintendo...
	BNE PRG014_CFD8		; <-- MISTAKE!! This is never true!  They wanted a BNE!!