So far I simply have them run one after the other, through four nametables worth of data (16 sets). It looks a bit like this:
Code:
Level1Nametable:
.db $80,$80,$80,$80, $80, $80,$80,$80,$80,$80,$80,$80, $80, $80,$80,$80 ;1-1 (Column set 1)
.db $80,$80,$80,$80, $80, $80,$80,$80,$80,$80,$80,$80, $80, $80,$80,$80
.db $80,$80,$80,$80, $80, $80,$80,$80,$80,$80,$80,$80, $80, $80,$80,$80
.db $80,$80,$80,$80, $80, $80,$80,$80,$80,$80,$80,$80, $80, $80,$80,$80
.db $80,$80,$80,$80, $80, $80,$80,$80,$80,$80,$80,$80, $80, $80,$80,$80
.db $80,$80,$80,$80, $80, $80,$80,$80,$80,$80,$80,$80, $80, $80,$80,$80
.db $80,$80,$80,$80, $80, $80,$80,$80,$80,$80,$80,$80, $80, $80,$80,$80
.db $80,$80,$80,$80, $80, $80,$80,$80,$80,$80,$80,$80, $80, $80,$80,$80
.db $80,$80,$80,$80, $80, $80,$80,$80,$80,$80,$80,$80, $80, $80,$80,$80 ;1-2 (Column set 2)
.db $80,$80,$80,$80, $80, $80,$80,$80,$80,$80,$80,$80, $80, $80,$80,$80
.db $80,$80,$80,$80, $80, $80,$80,$80,$80,$80,$80,$80, $80, $80,$80,$80
.db $80,$80,$80,$80, $80, $80,$80,$80,$80,$80,$80,$80, $80, $80,$80,$80
.db $80,$80,$80,$80, $80, $80,$80,$80,$80,$80,$80,$80, $80, $80,$80,$80
.db $80,$80,$80,$80, $80, $80,$80,$80,$80,$80,$80,$80, $80, $80,$80,$80
.db $80,$80,$80,$80, $80, $80,$80,$80,$80,$80,$80,$80, $80, $80,$80,$80
.db $80,$80,$80,$80, $80, $80,$80,$80,$80,$80,$80,$80, $80, $80,$80,$80
etc.
This was the best that I could figure out since BunnyBoy's code is in a BIN file, and I could not figure out how to view it. In place of having the program load SMBLevel.bin I have it load the above, all the way down to 1-16 (and yes, I know that the last few digits at the end of each pair of lines is thrown out since it only loads 30 as opposed to 32 tiles). The only way to re-arrange the order in this scheme is to re-arrange the sets. I assume that some kind of pointer table could allow for each set to be handled individually, but I am not sure how to load these into a string.