51–60 of 66 posts
Earlier quoted context omitted.
I find it so funny that somethings coded can crumble if a single bit is out of place, and others are like "No file there, no problem!"
That's kinda what happens with DNA -- a random mutation will make the resulting organism 'incompatible with life' -- or it will create a change that gives a huge advantage for survival.
If you put tape on cartridge pin #14 of NES Platoon (or other bad connection), the game will boot to a glitched version of the ending, thus making it a zero-second speedrun. Pin #14 is the CPU R/W pin, and if it's not properly connected, the game will be unable to write to the MMC1 mapper to perform bank switching. Platoon happens to be programmed in a way that address 0x8000 of every bank is an entry point that will…
Really stretches the definition of speed run. If I record the game to VHS, and fast forward to the end, does that count?
If you put tape on cartridge pin #14 of NES Platoon (or other bad connection), the game will boot to a glitched version of the ending, thus making it a zero-second speedrun. Pin #14 is the CPU R/W pin, and if it's not properly connected, the game will be unable to write to the MMC1 mapper to perform bank switching. Platoon happens to be programmed in a way that address 0x8000 of every bank is an entry point that will…
Really stretches the definition of speed run. If I record the game to VHS, and fast forward to the end, does that count?
If you put tape on cartridge pin #14 of NES Platoon (or other bad connection), the game will boot to a glitched version of the ending, thus making it a zero-second speedrun. Pin #14 is the CPU R/W pin, and if it's not properly connected, the game will be unable to write to the MMC1 mapper to perform bank switching. Platoon happens to be programmed in a way that address 0x8000 of every bank is an entry point that will…
Really stretches the definition of speed run. If I record the game to VHS, and fast forward to the end, does that count?
That is not a core tenant of speed running. Software preservation is completely separate from speed running.
>a core tenet of speedrunning is preserving old games, not destroying them. That is not a core tenant of speed running. Software preservation is completely separate from speed running.
https://www.speedrun.com/pencil?h=In_Real_Life-Drillless-10_...
(Not to mention hardware preservation is separate from software preservation and hardware preservation is rarely referring to pencils.)
Similar thoughts on things like shiny hunting in the Pokemon community.
If you put tape on cartridge pin #14 of NES Platoon (or other bad connection), the game will boot to a glitched version of the ending, thus making it a zero-second speedrun. Pin #14 is the CPU R/W pin, and if it's not properly connected, the game will be unable to write to the MMC1 mapper to perform bank switching. Platoon happens to be programmed in a way that address 0x8000 of every bank is an entry point that will…
Really stretches the definition of speed run. If I record the game to VHS, and fast forward to the end, does that count?
Speed running is so bizarre to me, the rules seem so arbitrary. I struggle to see how any form of hardware level modification that results in a meaningful deviation in the behavior of the game would be allowed. At that point what's the difference between smudging your disk and using a GameShark, etc? Similar thoughts on things like shiny hunting in the Pokemon community.
> While SHiFT insists that the method of smudging your disc will give you enough time in a lag to beat the SpongeBob game, he adds a clear caveat that it's not worth the risk of permanently damaging your game or original Xbox console How would reading a scratched/dirty disc permanently damage a console? That seems like a very bad issue for a device expected to read frequently swapped discs.
The disc's spin pretty fast, I could see someone smudging the disc too heavily with a substance that might fling off