this post was submitted on 12 Oct 2024
37 points (87.8% liked)

Nintendo

18465 readers
29 users here now

A community for everything Nintendo. Games, news, discussions, stories etc.

Rules:

  1. No NSFW content.
  2. No hate speech or personal attacks.
  3. No ads / spamming / self-promotion / low effort posts / memes etc.
  4. No linking to, or sharing information about, hacks, ROMs or any illegal content. And no piracy talk. (Linking to emulators, or general mention / discussion of emulation topics is fine.)
  5. No console wars or PC elitism.
  6. Be a decent human (or a bot, we don't discriminate against bots... except in Point 7).
  7. All bots must have mod permission prior to implementation and must follow instance-wide rules. For lemmy.world bot rules click here

Upcoming First Party Games (NA):

Game | Date

|

Mario & Luigi: Brothership | Nov 7 Donkey Kong Country Returns HD | Jan 16, 2025 Xenoblade Chronicles X: Definitive Edition | Mar 20, 2025 Metroid Prime 4 | 2025

Other Gaming Communities

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
37
TAS Explained: Super Mario Bros. 3 in 0.2 seconds (www.youtube.com)
submitted 1 month ago by [email protected] to c/[email protected]
12 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 9 points 1 month ago (2 children)

My brain was wondering how a video of only 0.2 seconds would work. Can you even say an entire word in that time? And how is that enough to explain all of Super Mario Bros. 3 TAS?

I was kind of disappointed to see the video lenght makes sense, and my brain was just not awake yet.

[–] [email protected] 4 points 1 month ago

Hah. I thought the opposite. "A video about a speedrun that short is gonna have to be really long".

[–] [email protected] 4 points 1 month ago

Don't know if you ended up watching it, but effectively they're able to randomly execute code during the loading screen using a bug caused by audio generation vs controller polling. So by using TAS tools they can spam the controller to cause an audio bug that let's them jump to executing code from Ram that they are able to manipulate using controller inputs.

TLDR: Using a bug in the audio processing, they can use controller inputs to write arbitrary code that jumps them to the end of the game.