This topic is for the purpose of discussing #6497: Aglar, MESHUGGAH & Riyan's NES DuckTales in 06:43.49

Link to video Temp encoding, potato quality If i hanen't permisson to upload the temp encode, i will delete it

That screen wrapping is really fun to watch! Yes vote.

Wow, amazing find! Good job Riyanoid! I will definitely look into this in the following days to make sure everything is done as fast as possible.

Love it, an easy Yes from me

Nice TAS. Always cool when something new gets found after such a long time. But I would like more detail on that wrap bug. Why does it work?

But I would like more detail on that wrap bug. Why does it work?

I'll do my best to explain how the wrap works though I'm not too sure either how it works as I wasn't the one to find it.

I'm going to take a guess that this has a similar cause to the Controller 2 effects seen in Mega Man 3. Both games were developed by Capcom around the same time, so it would make sense to assume the same root cause.

Which would be... a developer cheat code used for testing and debugging purposes left inside incidentally. IIRC in Mega Man 3 the P2 pad can alter gravity of the player amongst other possibilities, which is against the rules.

If it’s not an intended cheat code can it really be classified as a cheat? I though we only banned them if they were intended by the devs.

I don't think screen-wrapping is an intended thing. But the setup for it could be intentional, which can only be found out by reading the game code.

Informations so far (edited): - Just like we guessed it, from tcrf ducktales nes Holding Up on the second controller while falling into a non-lethal pit wraps Scrooge to the top of the screen. This is likely a debugging leftover that developers forgot to remove. - Works as long as no U+D or L+R is pressed. This is because the game filters the inputs (always sanitize your inputs as well). Subroutine $C1AB - Checking up to 5000 frames (second level start) with different button combinations, I didn't saw anything else. Comparing the two different trace log: Pressing Up on 2nd controller where otherwise screen would wrap

A:04 X:00 Y:00 S:BD P:nvUbdIzc   $E70B:A5 17     LDA $0017 = #$08  ;P2 pad Up button (3rd bit)
A:08 X:00 Y:00 S:BD P:nvUbdIzc   $E70D:29 08     AND #$08         ;comparing with $08 (3rd bit)
A:08 X:00 Y:00 S:BD P:nvUbdIzc   $E70F:D0 07     BNE $E718        ;branch not equal to zero
A:08 X:00 Y:00 S:BD P:nvUbdIzc   $E718:60        RTS (from $E354) ;ready to jump to developer code

edit2: According to "Infidelity's Dissection of DuckTales ROM", right after this the scrolling parameters gets updated $2F: horizontal/vertical scroll direction 00=up, 04=down Not pressing Up on 2nd controller where otherwise screen would wrap

A:04 X:00 Y:00 S:BD P:nvUbdIzc   $E70B:A5 17     LDA $0017 = #$00
A:00 X:00 Y:00 S:BD P:nvUbdIZc   $E70D:29 08     AND #$08
A:00 X:00 Y:00 S:BD P:nvUbdIZc   $E70F:D0 07     BNE $E718
A:00 X:00 Y:00 S:BD P:nvUbdIZc   $E711:AD 40 06  LDA $0640 = #$E4
A:E4 X:00 Y:00 S:BD P:NvUbdIzc   $E714:C9 E0     CMP #$E0
A:E4 X:00 Y:00 S:BD P:nvUbdIzC   $E716:B0 01     BCS $E719
A:E4 X:00 Y:00 S:BD P:nvUbdIzC   $E719:A4 F1     LDY $00F1 = #$04
A:E4 X:00 Y:04 S:BD P:nvUbdIzC   $E71B:C8        INY
A:E4 X:00 Y:05 S:BD P:nvUbdIzC   $E71C:C4 2A     CPY $002A = #$07
A:E4 X:00 Y:05 S:BD P:NvUbdIzc   $E71E:F0 1D     BEQ $E73D
A:E4 X:00 Y:05 S:BD P:NvUbdIzc   $E720:A5 F2     LDA $00F2 = #$00
A:00 X:00 Y:05 S:BD P:nvUbdIZc   $E722:10 04     BPL $E728
A:00 X:00 Y:05 S:BD P:nvUbdIZc   $E728:A9 00     LDA #$00
A:00 X:00 Y:05 S:BD P:nvUbdIZc   $E72A:85 F2     STA $00F2 = #$00
A:00 X:00 Y:05 S:BD P:nvUbdIZc   $E72C:A5 29     LDA $0029 = #$01
A:01 X:00 Y:05 S:BD P:nvUbdIzc   $E72E:29 01     AND #$01
A:01 X:00 Y:05 S:BD P:nvUbdIzc   $E730:AA        TAX
A:01 X:01 Y:05 S:BD P:nvUbdIzc   $E731:BD 3E E7  LDA $E73E,X @ $E73F = #$1F
A:1F X:01 Y:05 S:BD P:nvUbdIzc   $E734:85 26     STA $0026 = #$1F
A:1F X:01 Y:05 S:BD P:nvUbdIzc   $E736:A9 04     LDA #$04
A:04 X:01 Y:05 S:BD P:nvUbdIzc   $E738:85 16     STA $0016 = #$00
A:04 X:01 Y:05 S:BD P:nvUbdIzc   $E73A:4C 78 E8  JMP $E878
A:04 X:01 Y:05 S:BD P:nvUbdIzc   $E878:A5 7B     LDA $007B = #$00
A:00 X:01 Y:05 S:BD P:nvUbdIZc   $E87A:F0 10     BEQ $E88C
A:00 X:01 Y:05 S:BD P:nvUbdIZc   $E88C:A5 F2     LDA $00F2 = #$00
A:00 X:01 Y:05 S:BD P:nvUbdIZc   $E88E:D0 52     BNE $E8E2
A:00 X:01 Y:05 S:BD P:nvUbdIZc   $E890:A5 F3     LDA $00F3 = #$07
A:07 X:01 Y:05 S:BD P:nvUbdIzc   $E892:29 01     AND #$01
A:01 X:01 Y:05 S:BD P:nvUbdIzc   $E894:F0 4C     BEQ $E8E2
A:01 X:01 Y:05 S:BD P:nvUbdIzc   $E896:A5 16     LDA $0016 = #$04
A:04 X:01 Y:05 S:BD P:nvUbdIzc   $E898:4A        LSR
A:02 X:01 Y:05 S:BD P:nvUbdIzc   $E899:4A        LSR
A:01 X:01 Y:05 S:BD P:nvUbdIzc   $E89A:29 02     AND #$02
A:00 X:01 Y:05 S:BD P:nvUbdIZc   $E89C:AA        TAX
A:00 X:00 Y:05 S:BD P:nvUbdIZc   $E89D:A5 2B     LDA $002B = #$08
A:08 X:00 Y:05 S:BD P:nvUbdIzc   $E89F:5D E3 E8  EOR $E8E3,X @ $E8E3 = #$00
A:08 X:00 Y:05 S:BD P:nvUbdIzc   $E8A2:18        CLC
A:08 X:00 Y:05 S:BD P:nvUbdIzc   $E8A3:7D E4 E8  ADC $E8E4,X @ $E8E4 = #$00
A:08 X:00 Y:05 S:BD P:nvUbdIzc   $E8A6:48        PHA
A:08 X:00 Y:05 S:BC P:nvUbdIzc    $E8A7:65 2D     ADC $002D = #$27
A:2F X:00 Y:05 S:BC P:nvUbdIzc    $E8A9:A8        TAY
A:2F X:00 Y:2F S:BC P:nvUbdIzc    $E8AA:68        PLA
A:08 X:00 Y:2F S:BD P:nvUbdIzc   $E8AB:18        CLC
A:08 X:00 Y:2F S:BD P:nvUbdIzc   $E8AC:65 24     ADC $0024 = #$28
A:30 X:00 Y:2F S:BD P:nvUbdIzc   $E8AE:85 00     STA $0000 = #$00
A:30 X:00 Y:2F S:BD P:nvUbdIzc   $E8B0:B1 20     LDA ($20),Y @ $CE9A = #$08
A:08 X:00 Y:2F S:BD P:nvUbdIzc   $E8B2:C9 FF     CMP #$FF
A:08 X:00 Y:2F S:BD P:nvUbdIzc   $E8B4:F0 2C     BEQ $E8E2
A:08 X:00 Y:2F S:BD P:nvUbdIzc   $E8B6:A5 F1     LDA $00F1 = #$04
A:04 X:00 Y:2F S:BD P:nvUbdIzc   $E8B8:18        CLC
A:04 X:00 Y:2F S:BD P:nvUbdIzc   $E8B9:7D E8 E8  ADC $E8E8,X @ $E8E8 = #$01
A:05 X:00 Y:2F S:BD P:nvUbdIzc   $E8BC:C5 2A     CMP $002A = #$07
A:05 X:00 Y:2F S:BD P:NvUbdIzc   $E8BE:B0 22     BCS $E8E2
A:05 X:00 Y:2F S:BD P:NvUbdIzc   $E8C0:85 F1     STA $00F1 = #$04
A:05 X:00 Y:2F S:BD P:NvUbdIzc   $E8C2:BD E7 E8  LDA $E8E7,X @ $E8E7 = #$E6
A:E6 X:00 Y:2F S:BD P:NvUbdIzc   $E8C5:9D 40 06  STA $0640,X @ $0640 = #$E4
A:E6 X:00 Y:2F S:BD P:NvUbdIzc   $E8C8:84 2D     STY $002D = #$27
A:E6 X:00 Y:2F S:BD P:NvUbdIzc   $E8CA:A5 00     LDA $0000 = #$30
A:30 X:00 Y:2F S:BD P:nvUbdIzc   $E8CC:85 24     STA $0024 = #$28
A:30 X:00 Y:2F S:BD P:nvUbdIzc   $E8CE:68        PLA
A:6E X:00 Y:2F S:BE P:nvUbdIzc  $E8CF:68        PLA
A:DB X:00 Y:2F S:BF P:NvUbdIzc $E8D0:A9 00     LDA #$00
A:00 X:00 Y:2F S:BF P:nvUbdIZc $E8D2:85 4F     STA $004F = #$8E
A:00 X:00 Y:2F S:BF P:nvUbdIZc $E8D4:AD 00 06  LDA $0600 = #$E0
A:E0 X:00 Y:2F S:BF P:NvUbdIzc $E8D7:29 FC     AND #$FC
A:E0 X:00 Y:2F S:BF P:NvUbdIzc $E8D9:8D 00 06  STA $0600 = #$E0
A:E0 X:00 Y:2F S:BF P:NvUbdIzc $E8DC:20 76 C9  JSR $C976
A:E0 X:00 Y:2F S:BD P:NvUbdIzc   $C976:A5 16     LDA $0016 = #$04
A:04 X:00 Y:2F S:BD P:nvUbdIzc   $C978:29 0C     AND #$0C
A:04 X:00 Y:2F S:BD P:nvUbdIzc   $C97A:29 04     AND #$04
A:04 X:00 Y:2F S:BD P:nvUbdIzc   $C97C:85 2F     STA $002F = #$00

Yeah but what does this check actually trigger? I doubt they explicitly make you screen-wrap, there should be some missing check somewhere.

What I don't understand about the possibility that this is actually an intended function accidentally leftover by developers is why they made it so you have to be OFF a rope/vine (in free-fall) to make Scrooge zip to the top of the screen. From a testing standpoint, it would have been just as beneficial to have the zip occur while simply climbing down off the bottom of the screen via a rope as it would be to occur during free-fall. If this on-rope option was also done, why only take one of the possibilities out of the game code before release? It's hard for me to believe that it was meant as a developer tool. I think we're missing something here. Is the RAM value at $0017 ONLY for storing controller 2 input, or do other things change it in the game code?

I think there is a misunderstanding about the purpose. It isn't about "allow screnwrapping", it is about "allow falling through the bottom of the screen". As I posted above with my 3rd edit, the values around 0x0020 ~ 0x002F is used for scrolling stuffs. Here's from Infidelity's research (Note: these are not 100% accurate!)

Attempts, not 100% sure $20 - $21: Low/High byte pointers to individual level screen presets $2C: Tells you what screen your on in current scroll. (MAKES NO SENSE!!! IF YOU GO LEFT IT"S ALL SCREWED UP :() $2B: How many screens in current scroll ?? might not be??? $2D: what screen id your on ($20099 is the new location for which screen id to start on when you enter a new level. BUT, if you go to a screen preset on a different scroll, there's some glitches) (STILL GLICTHES NO MATTER WHAT) $2F: Horizontal/Vertical Scroll Direction 00=UP 04=DOWN $39: Status of Scrooge 00=Walk 01=Jump 02=Pogo 03=Climb 04=Wack Cane OK, If you change what screen id your on in $2D, you have to also match the current screen number your on in $2C. EXAMPLE: The Amazon, Start out with 2F in $2D, that's the far end of the 1st scroll above ground. If you start to move left, you'll notice the screen gets messed up. But, if you put 08 into $2C, then move left, everything will work correctly

New, up to date informations about effectiveness of P2 U: (edit: Thanks feos for helping in what to really test!) 1. Requires a vine on the bottom of the screen If there is no vine on the bottom, you just die. Examples: Amazon 1st row last screen, climbing down to lowest row. Moon 2nd screen: https://imgur.com/a/jIkJy62 It doesn't matters if you climbed and jumped off from a vine previously. 2. Can be done in any X pos as long as you are on the same screen as the vine If there is a vine on the bottom, you can go to the top of the screen after falling down from any X pos Example: Amazon 2nd row last screen, two vines: https://imgur.com/a/qLn2sJe If there is no vine on the bottom on the screen you are trying to do this, you will die. Example: Amazon 3rd row last screen (to the right) has a vine, while the next screen on the left has a pit. Example: Himalayas top row first screen (from the left) has a vine, while the next screen o nthe right has a pit. This can be proven with cheating your X pos to FF on Amazon 3rd row next screen. 0x0720 = FF (You can't do this otherwise, because both examples have a wall you need to get around but our Y position falls drastically, leaving us no time to get back to the "vine screen" Regarding "make the game easier": A: f15140 Himalayas 2nd row most left screen It has a snowball falling down from the top. Using this trick let's the player skip that obstacle. The previous TAS takes dmg from it and then climbs through it while invincible. B: f24660 Final climbing race against the boss While we are already much faster since we start with boosting off the bat, it further helps to close the gap.

[13:31:12] <feos> https://i.imgur.com/kzQVHPF.gif looks like a debug feature [13:31:24] <feos> meant to be used to test screen scrolling

The movie is now will be obsolete soon: Link to video WIP, it's not perfect yet.

1. Requires a vine on the bottom of the screen If there is no vine on the bottom, you just die. Examples: Amazon 1st row last screen, climbing down to lowest row. Moon 2nd screen: https://imgur.com/a/jIkJy62 It doesn't matters if you climbed and jumped off from a vine previously.

A rope/vine does not have to be on screen. I just tested in the Himalayas in the long multi-screen drop by freezing the value at 0x0017 (p2 up press), and it appears to work for any pit that would otherwise scroll the screen down. In other words any pit that simply isn't a death pit. The following is 13 ticks of the in-game timer, and I didn't start this until Scrooge was already a couple screens below the rope at the top of the world.

I think there is a misunderstanding about the purpose. It isn't about "allow screnwrapping", it is about "allow falling through the bottom of the screen".

As it's only possible where screen scrolling would normally occur when Scrooge falls off the bottom of the screen, the effect of the feature would actually be best described as "preventing screen scrolling, but only while Scrooge is falling (not climbing) through a gap that would otherwise initiate screen scrolling." If it was simply about enabling falling through the bottom of the screen and being sent to the top of the screen; it would be a desirable testing feature for ANY pit, not just the non-death/scrolling pits. Regardless of whether the purpose is to prevent scrolling or to allow warping Scrooge to the top of the screen, the other question is why program it to only work when he's falling and not while climbing down the ropes that initiate scrolling? It's this last part that I think I struggle with most in believing this was an intended feature. Why prevent scrolling only when falling in these few instances where it's a not a death pit, but not prevent scrolling when Scrooge is on a vine/rope? It seems a VERY limited feature to have specifically programmed, even for testing purposes. The only reason I can see this being the case is to specifically test the scrolling initiated when climbing down a vine. Another reason why this wouldn't be a very good debug feature is the cases where using the feature can result in Scrooge being out of bounds. The feature would only have helped testers in very few situations and would have made testing more tedious in others by getting them out of bounds and forcing them to either reset the console, manually re-position Scrooge, or somehow find a way back in-bounds in order to continue testing intended game features. Testing is about breaking a game....not trying to figure out how to get back to normalcy from a broken game state. Other considerations: 1) This may be a leftover feature that originally had an intended in-game purpose, but that reason was removed from the final product. Thus this feature may not a debugging leftover, but an unused feature. 2) This was a debug feature, but only part of the code for that feature. Meaning that what we're abusing isn't how the feature was intended to be used. This would mean that this submission is a valid use of this button combination/effect; abusing poor programming (or more accurately, poor removal of programming) to yield a result unintended by developers in normal play. I just feel that the presence of this one snippet of assembly code that shows how the effect happens (skipping the code for screen scrolling) is not enough evidence to claim that this particular effect was intentionally included as-is for developer testing purposes. If we had further evidence (for example, something published from any of the developers or Nintendo itself) claiming it was an accidental leftover, we could disallow use. But as we have no other evidence beyond this four line assembly code snippet, we can't make that assumption.

I'll need to read the manual, and look for other P2 input checks in the code.

I'm really curious about this glitch/feature so just in case it helps anything... 1)The manual says nothing about the Player 2 controller. 2) I did a bit more testing on the code at $E70D that reads 0x0017. The following code snippets are traces of $E70D and following being executed. The code is executed every frame that Scrooge is in free-fall, not just when screen transitions are happening or when he's falling through non-death gaps.

f570    $E70B:A5 17     LDA $0017 = #$00                             A:04 X:00 Y:00 S:BD P:nvUbdIzc 
f570    $E70D:29 08     AND #$08                                     A:00 X:00 Y:00 S:BD P:nvUbdIZc 
f570    $E70F:D0 07     BNE $E718                                    A:00 X:00 Y:00 S:BD P:nvUbdIZc 
f570    $E711:AD 40 06  LDA $0640 = #$9B                             A:00 X:00 Y:00 S:BD P:nvUbdIZc 
f570    $E714:C9 E0     CMP #$E0                                     A:9B X:00 Y:00 S:BD P:NvUbdIzc 
f570    $E716:B0 01     BCS $E719                                    A:9B X:00 Y:00 S:BD P:NvUbdIzc 
f570    $E718:60        RTS (from $E354) --------------------------- A:9B X:00 Y:00 S:BD P:NvUbdIzc 
f570    $DB6F:A5 6C     LDA $006C = #$00                             A:9B X:00 Y:00 S:BF P:NvUbdIzc 
f570    $DB71:D0 36     BNE $DBA9                                    A:00 X:00 Y:00 S:BF P:nvUbdIZc 
f570    $DB73:A9 06     LDA #$06                                     A:00 X:00 Y:00 S:BF P:nvUbdIZc 
f570    $DB75:20 DE FF  JSR $FFDE                                    A:06 X:00 Y:00 S:BF P:nvUbdIzc 
f570    $FFDE:85 E7     STA $00E7 = #$06                             A:06 X:00 Y:00 S:BD P:nvUbdIzc 
f570    $FFE0:AA        TAX                                          A:06 X:00 Y:00 S:BD P:nvUbdIzc 
f570    $FFE1:9D E5 FF  STA $FFE5,X @ $FFEB = #$06                   A:06 X:06 Y:00 S:BD P:nvUbdIzc 
f570    $FFE4:60        RTS (from $FFDE) --------------------------- A:06 X:06 Y:00 S:BD P:nvUbdIzc 
f570    $DB78:20 00 80  JSR $8000                                    A:06 X:06 Y:00 S:BF P:nvUbdIzc

f573    $E70B:A5 17     LDA $0017 = #$08                             A:04 X:00 Y:00 S:BD P:nvUbdIzc 
f573    $E70D:29 08     AND #$08                                     A:08 X:00 Y:00 S:BD P:nvUbdIzc 
f573    $E70F:D0 07     BNE $E718                                    A:08 X:00 Y:00 S:BD P:nvUbdIzc 
f573    $E718:60        RTS (from $E354) --------------------------- A:08 X:00 Y:00 S:BD P:nvUbdIzc 
f573    $DB6F:A5 6C     LDA $006C = #$00                             A:08 X:00 Y:00 S:BF P:nvUbdIzc 
f573    $DB71:D0 36     BNE $DBA9                                    A:00 X:00 Y:00 S:BF P:nvUbdIZc 
f573    $DB73:A9 06     LDA #$06                                     A:00 X:00 Y:00 S:BF P:nvUbdIZc 
f573    $DB75:20 DE FF  JSR $FFDE                                    A:06 X:00 Y:00 S:BF P:nvUbdIzc 
f573    $FFDE:85 E7     STA $00E7 = #$06                             A:06 X:00 Y:00 S:BD P:nvUbdIzc 
f573    $FFE0:AA        TAX                                          A:06 X:00 Y:00 S:BD P:nvUbdIzc 
f573    $FFE1:9D E5 FF  STA $FFE5,X @ $FFEB = #$06                   A:06 X:06 Y:00 S:BD P:nvUbdIzc 
f573    $FFE4:60        RTS (from $FFDE) --------------------------- A:06 X:06 Y:00 S:BD P:nvUbdIzc 
f573    $DB78:20 00 80  JSR $8000                                    A:06 X:06 Y:00 S:BF P:nvUbdIzc

Both these tests were done with no ground gaps visible on screen during a jump. The code is not executed while Scrooge is in the rising portion of the jump, but triggers as soon as he starts his descent. 0x0640 is Scrooge's position on screen. When falling in a death pit, he dies when 0x0640 is approximately equal to a hex value of D9. Thus he never gets to the value of E0 needed to trigger the code here:

f570    $E714:C9 E0     CMP #$E0                                     A:9B X:00 Y:00 S:BD P:NvUbdIzc 
f570    $E716:B0 01     BCS $E719                                    A:9B X:00 Y:00 S:BD P:NvUbdIzc 

This makes me wonder if the death pits have a hitbox of sorts. If so, i'm curious if finding a way to clip through a normal floor would allow for this P2 UP thing to skip other areas of the game because the clip through the floor may not hit a death-gap hitbox. Ultimately the main thing that holding UP on controller 2 does with this above code is skip the portion that looks to see if Scrooge is crossing the bottom limit for a screen transition. The reason he appears at the top seems to be a simple RAM rollover from 255 to 0. It still seems to me an odd thing to have intentionally coded only for these non-death gap situations. Based on all this, it seems quite different than the gravity altering of MM3 mentioned above. Another interesting thing I discovered while testing this: If there is a ledge at the top of the screen where Scrooge reappears after falling through the floor, Scrooge can jump back up out of the bottom of the screen and out of the pit (again, likely just RAM rollover from 0 to 255). If he enters the free-fall portion of the jump while below E0 threshold, he'll immediately trigger the screen transition (assuming UP has been released on P2 controller). The transition will not occur while he's rising up out of the pit as the code at $E70D won't be executed until Scrooge is in free-fall. I haven't had a chance to look through a complete disassembly of the code to see if any other reads of P2 controller happen. EDIT: Another minor bit of info. Cheating in a higher screen Y-position value into $E715 causes screen transitions to occur when Scrooge is higher from the bottom of the screen. Too high of a value can cause weird effects.

Only in the Prototype version of the game, on the P2 pad pressing A+B at the same time turns Scrooge invincible. (edit: death pits are still death pits in this mode) Gif: https://imgur.com/pYrhu75 edit4 or whatever, trace logs: Pressing A+B on P2 pad, only the differences:

A:04 X:04 Y:00 S:BF P:nvUbdIzc $DB96:A5 15     LDA $0015 = #$C0  ; load P2 input
A:C0 X:04 Y:00 S:BF P:NvUbdIzc $DB98:C9 C0     CMP #$C0   ; check P2 pad being A+B (7th and 6th bit)
A:C0 X:04 Y:00 S:BF P:nvUbdIZC $DB9A:D0 04     BNE $DBA0
A:C0 X:04 Y:00 S:BF P:nvUbdIZC $DB9C:A9 FF     LDA #$FF
A:FF X:04 Y:00 S:BF P:NvUbdIzC $DB9E:85 75     STA $0075 = #$00
A:FF X:04 Y:00 S:BF P:NvUbdIzC $DBA0:A5 AC     LDA $00AC = #$00

...

A:00 X:04 Y:00 S:BD P:nvUbdIZc   $E3DC:A5 75     LDA $0075 = #$FF
A:FF X:04 Y:00 S:BD P:NvUbdIzc   $E3DE:F0 23     BEQ $E403
A:FF X:04 Y:00 S:BD P:NvUbdIzc   $E3E0:30 21     BMI $E403
A:FF X:04 Y:00 S:BD P:NvUbdIzc   $E403:A6 39     LDX $0039 = #$00
A:FF X:00 Y:00 S:BD P:nvUbdIZc   $E405:BD 12 E4  LDA $E412,X @ $E412 = #$34

...

A:00 X:05 Y:04 S:BD P:nvUbdIZc   $800A:05 75     ORA $0075 = #$FF
A:FF X:05 Y:04 S:BD P:NvUbdIzc   $800C:F0 08     BEQ $8016
A:FF X:05 Y:04 S:BD P:NvUbdIzc   $800E:AD 00 06  LDA $0600 = #$A0
A:A0 X:05 Y:04 S:BD P:NvUbdIzc   $8011:09 02     ORA #$02
A:A2 X:05 Y:04 S:BD P:NvUbdIzc   $8013:8D 00 06  STA $0600 = #$A0
A:A2 X:05 Y:04 S:BD P:NvUbdIzc   $8016:A0 04     LDY #$04
A:A2 X:05 Y:04 S:BD P:nvUbdIzc   $8018:84 97     STY $0097 = #$7C
A:A2 X:05 Y:04 S:BD P:nvUbdIzc   $801A:A5 7F     LDA $007F = #$FF

...

A:02 X:00 Y:0D S:BB P:nvUbdIzC     $8123:F0 07     BEQ $812C
A:02 X:00 Y:0D S:BB P:nvUbdIzC     $8125:A5 95     LDA $0095 = #$D5
A:D5 X:00 Y:0D S:BB P:NvUbdIzC     $8127:4A        LSR
A:6A X:00 Y:0D S:BB P:nvUbdIzC     $8128:4A        LSR
A:35 X:00 Y:0D S:BB P:nvUbdIzc     $8129:B0 01     BCS $812C
A:35 X:00 Y:0D S:BB P:nvUbdIzc     $812B:60        RTS (from $80B8) ---------------------------

Not pressing A+B on P2 pad:

A:04 X:04 Y:00 S:BF P:nvUbdIzc $DB96:A5 15     LDA $0015 = #$00
A:00 X:04 Y:00 S:BF P:nvUbdIZc $DB98:C9 C0     CMP #$C0
A:00 X:04 Y:00 S:BF P:nvUbdIzc $DB9A:D0 04     BNE $DBA0
A:00 X:04 Y:00 S:BF P:nvUbdIzc $DBA0:A5 AC     LDA $00AC = #$00

...

A:00 X:04 Y:00 S:BD P:nvUbdIZc   $E3DC:A5 75     LDA $0075 = #$00
A:00 X:04 Y:00 S:BD P:nvUbdIZc   $E3DE:F0 23     BEQ $E403
A:00 X:04 Y:00 S:BD P:nvUbdIZc   $E403:A6 39     LDX $0039 = #$00
A:00 X:00 Y:00 S:BD P:nvUbdIZc   $E405:BD 12 E4  LDA $E412,X @ $E412 = #$34

...

A:00 X:05 Y:04 S:BD P:nvUbdIZc   $800A:05 75     ORA $0075 = #$00
A:00 X:05 Y:04 S:BD P:nvUbdIZc   $800C:F0 08     BEQ $8016
A:00 X:05 Y:04 S:BD P:nvUbdIZc   $8016:A0 04     LDY #$04
A:00 X:05 Y:04 S:BD P:nvUbdIzc   $8018:84 97     STY $0097 = #$7C
A:00 X:05 Y:04 S:BD P:nvUbdIzc   $801A:A5 7F     LDA $007F = #$FF

...

A:00 X:00 Y:0D S:BB P:nvUbdIZC     $8123:F0 07     BEQ $812C
A:00 X:00 Y:0D S:BB P:nvUbdIZC     $812C:A0 00     LDY #$0

edit5: $0015 (0x0015) is the address for storing P2 pad first. This lasts for a frame. Later this gets copied to $0017. 0x0075 gets changed to FF which is the "invincibility status". anything other than 0 makes Scrooge flicker and invincible. setting 1 also changes the music, but it's set to 0xFF, which has the "no music change, invincibile" state. Enabling this cheat (0x0075 = FF) will make I guess the very first object to have this property. since the title screen are objects as well, they will flicker (and be invincible :) ) on the published released ROMs as well.

screen wraps look cool, well done

Duck Tales, Wanpaku Duck Yume Bouken (UNI) Avoid falling from upper stages (added 29.03.14): During the game, only bottom levels of the stage are deadly if you fall into the holes. When falling from the upper levels, you just moving to the lower ones. To avoid falling from the upper levels and loop back from the top of the screen, hold Up on controller 2 while falling.

Red means "cheats are unique, not listed on any site". UNI means "unique cheats". The way he finds those is by scanning ROMs for what input they read. And it seems in the official release there's only this one check left. And the prototype apparently has more. PS: http://www.thealmightyguru.com/Games/Hacking/Wiki/index.php?title=DuckTales

If it was simply about enabling falling through the bottom of the screen and being sent to the top of the screen; it would be a desirable testing feature for ANY pit, not just the non-death/scrolling pits. Regardless of whether the purpose is to prevent scrolling or to allow warping Scrooge to the top of the screen, the other question is why program it to only work when he's falling and not while climbing down the ropes that initiate scrolling? It's this last part that I think I struggle with most in believing this was an intended feature. Why prevent scrolling only when falling in these few instances where it's a not a death pit, but not prevent scrolling when Scrooge is on a vine/rope? It seems a VERY limited feature to have specifically programmed, even for testing purposes. The only reason I can see this being the case is to specifically test the scrolling initiated when climbing down a vine.

Debug leftover means that most debug features were removed before release, but not all of them, since humans tend to miss things. As the prototype shows, there were more. I think similar branches were added to other places related to pit falling. And since Asm is quite a messy language, you can only hardcode or copy-paste things in. Then when you feel like removing the extra checks, you do a text search and edit those checks out one by one. And then you miss a few, which is why debug leftovers even exist.

Another reason why this wouldn't be a very good debug feature is the cases where using the feature can result in Scrooge being out of bounds. The feature would only have helped testers in very few situations and would have made testing more tedious in others by getting them out of bounds and forcing them to either reset the console, manually re-position Scrooge, or somehow find a way back in-bounds in order to continue testing intended game features. Testing is about breaking a game....not trying to figure out how to get back to normalcy from a broken game state.

Getting into walls is quite obviously a part of game development and testing. I don't think screen-wrapping was used explicitly for that, because it could be coded to happen more easily for the purpose of testing. But I think it's obvious that this one feature we have here wasn't the only one added just to test scrolling and nothing else was ever tested in a similar way.

1) This may be a leftover feature that originally had an intended in-game purpose, but that reason was removed from the final product. Thus this feature may not a debugging leftover, but an unused feature.

Yeah, like controlling ducks with the second controller in Duck Hunt.

2) This was a debug feature, but only part of the code for that feature. Meaning that what we're abusing isn't how the feature was intended to be used. This would mean that this submission is a valid use of this button combination/effect; abusing poor programming (or more accurately, poor removal of programming) to yield a result unintended by developers in normal play.

Except the game is checking a very specific input which we're sending, and then it explicitly enables screen-wrap. We can't know developers' intentions, but we can avoid explicit checks by glitching the game. This is why [1627] SNES EarthBound "check glitch" by pirohiko & MUGG in 30:42.12 was accepted:

This run uses a glitch which passes through a debug menu which cannot otherwise (as to our knowledge) be accessed by means apart from external codes. If the debug menu was easily accessed by an internal code, that would be a different story. As it stands, it can only be assumed as part of the glitch process, and it will be allowed. In the apparently non-existent event that such an internal code is found later, the published run will be placed in the impure category and any further runs going through the debug menu will likely be rejected.

The borderline that can be used here is not what something was meant to be used for, but how it's accessed. With SNES Earthbound, the debug menu was meant to be used for cheating during development, and not meant for regular user play. But it's exactly what that movie uses it for! Yet it's allowed because it's accessed through a glitch. There's an argument that debug menu was allowed only because we don't know how to access it without glitching. If that is used as a borderline, then as FractalFusion said it'd put us in an impure situation when a movie gets invalidated after publication. And the problem with this is that for any game we can't be sure that there's no input combination enabling debug features. To be sure, the game code has to be exhaustively analyzed, and we can't afford that. Yet blatantly using cheats or debug features often feels cheap, even via glitching. For example, imagine that you can get invincible for the entire game by entering a code, and you glitch yourself into this mode in level 1, playing the entire game invincible. That insolently violates our guideline about difficulties, so it'd have to be rejected in the end. As for this game, there's no glitching involved when enabling screen-wrapping, and it's a known input combination, and it's clearly not meant for normal play since you only play this game with 1 controller.