What you'll need
1. The corruption program itself. You can get it here
). There's also a Vinesauce specific version of the program which can be downloaded through this topic
. It features more descriptive buttons for new corruption users as well as a few noncritical bells and whistles. This guide was made for the old corruption program, but most of what I'm saying is relevant to the newer corrupter as well.
2. Emulators: One for each system you intend to corrupt for. The NES emulator of choice is nestopia
3. Roms: On your own for this one. You know where to look.
-------------Quick start guide
1. Download and unzip the required files
2. Run the corrupt.exe (if you get a security warning, don't worry about it)
3. Fill in the three topmost fields with where you downloaded the files to, the emulator, and the rom in that order.
4. Set start to a value between $1000 and $F000
5. Set end to a huge number, then find the actual end of file from the prompt
6. Select Every ____th Bytes and put in a number somewhere between the low 500s and the high 3000s
7. Select Add ____ To Bytes and put in the value 2
8. Press Go and play!
9. Mess with either Start, Every ____th Byte, or Add ____ To Bytes to search for corruptions
-------------Indepth UI guideTop half
Toolbar: Simple stuff here, File only lets you exit and save and load allows you save particularly cool corruptions, only ten slots though, so taking screen shots during corruption binges is recommended.
Change directory to: Sets the base drive or folder where all other files are found. If you're unsure of where you're storing everything you can just leave it to the C drive, there's no penalty to under defining this besides having to search harder when setting the next two fields
Run emulator: Set this to your emulator of choice. Note that some emulators interpret roms slightly differently, and can lead to inconsistencies in corruptions. If your unsure if you're using the same emulator as the streamer, just ask.
Corrupt this rom: Using a different version of a game is a surefire way to make corruptions not work on the stream, once again if you're not sure if you're matching up, ask the streamer. Usually the version being used is the "U" version, but this isn't a hard and fast rule.
Create now: Creates the corrupt rom without playing it. This is useless for streaming.
Start: The start is how far into the rom the first corrupt takes place. Because every other value depends on this varying the start range you can use this to find new corruptions easily, though it isn't the most often used way of doing this. It isn't a good idea to start corrupting a rom right at 0, as most roms would have data that identifies them as roms there. This field is hexadecimal, so you can also use ABCDEF in addition to 0-9 here.
End: The end is where the corruption stop. Because nothing else depends on this it's a crappy way to change corruptions. You can actually set the end to the very last bit of the rom, just put an absurdly large value for the end and the corrupter will tell you where the actual end is. It's also hexadecimal.
Change range by: This value changes how much pressing the little +/- signs change the ranges. This is NOT a hexadecimal field.
Auto End: This changes the end to be one "Change range by" distance from the start. It's fairly useless.
Change ALL bytes: This is going full retard. you never do this, it will NOT work.
Every ____th Byte: This chooses which pieces of the file you're going to mess with. The smaller this number the more often a byte will be corrupted, and consequentially how many bytes are corrupted overall. Setting this too high will make corruptions boring, setting this too low and corruptions will be just too messed up to even run. The sweet spot for NES games is around 800 and for SNES games it sits near 2200. This isn't a perfect rule though. Not hexadecimal.
Byte 0 after Byte AND Mask: No idea how this works. Wizardry.
Shift Right: This takes the value for the corrupted byte from a normal byte to its right. This value can be negative to draw from the left instead. Since you won't really know what values your taking unless you've memorized the friggen machine code the specifics don't really matter. Not hexadecimal.
Corrupt bytes with...
*Random Bytes: Bytes selected just get some random garbage replacing them. This changes every time you corrupt the rom, so you can't use this to share corruptions with others.
*Byte Range: It's like random with a limited range, but it's still impossible to reproduce. There's one exception, and that's when the range is zero bytes (like $50 to $50) because then every byte is replaced with the same value.
*Looping Sequence: It doesn't work, don't try to use it.
Add to byte: Modifies the original byte by the number specified. You can make this number negative to reduce the original byte instead. Even adds are usually more stable than odd ones, and positive ones are usually more stable than negative ones. The most usuable add to is usually 2. Adding 0 will do nothing obviously.
GO: Launches the emulator after corrupting the rom
Auto: Seems to do the same thing, just use GO
-------------FAQDoes using Corrupt ruin my roms?
No, corruptions are made to a temporary copy of your rom, the original is not maimed.What can I Corrupt?
Theoretically? Anything. Just be aware that the more complex the file becomes the more likely you are to break something that bricks the file. Start with NES and work your way up from there when you feel more confident.What do I do when I find a corruption I want to share?
Take a snapshot (PrtSc) and edit it down to the window in photoshop OR write down the following numbers from it: Start, End, Every ____th Bytes, Shift Right (or) Add to.I tried to start up Corrupt.exe and it said I was missing files!
Newer versions of Windows do not come installed with several files Corupt.exe requires to run. A simple google search can find downloads for them, but for your safety only install them directly from Microsoft sites. Note that the program will usually require more than one missing file, but will only tell you of one missing file before closing so you may have to download several. There are also links to these files within this very topic if you don't feel like googling.I'm switching from Corrupt.exe to the Vinesauce corrupter or visa versa, will the corruptions be the same?
They will be as long as you're sure the numbers are imputed correctly.I found a corruption I wanted to share but when I gave it to someone else to run it didn't do the same thing!
You are probably using a different version of the rom than who you're sharing with. While outwardly similar different versions of a rom might have wildly different code, meaning that it would respond differently to the same corruption.
-------------TroubleshootingThe emulator doesn't boot when I try to make a corruption!
No corruption would ever make the emulator fail to boot entirely, as the emulator has to boot before it can read any rom. Check to make sure the path for the emulator is set properly. It should point to the same .exe file you click when you want to use the emulator normally. If it is, check to see if the emulator works on its own, something may be wrong on that end.The rom never plays!
Make sure the rom path is set right, be sure it's actually pointing at the ROM and not the save data file. If you are having trouble telling the two apart, the save data is the smaller of the two files in nearly all cases. If you've tried this it's entirely possible that you are corrupting too much. Push the start value higher and raise the "Corrupt every ___th byte". Consider making the add field 1 or 2 to being with, as small incremental changes tend to play better with roms sometimes.The rom hangs immediately/very quickly!
This is normal! Any corruption that targets the whole file will have an effect on things like menus and intro sequences too, if this change breaks the logic of the rom, it will usually freeze up, If you feel this is happening too much to you, take steps to reduce the level of corruption you're attempting (see last question). Additionally creating save states on a clean rom and using them in the corrupted rom can be used to sometimes bypass broken intros/menus.