LoginLogin
Might make SBS readonly: thread

PRG Shuffle

Root / Submissions / [.]

h267Created:
Download:N324DEZD
Version:1.08Size:6.58 KB
LATEST VERSION: v1.08 A kind of bad app that will mess up a programโ€™s data. Why? For fun! Itโ€™s not my fault if the programs it outputs are NSFW.

Instructions:

1. Download this program. 2. Copy any programs and their resources into to corruption folder, or vice versa. Larger programs and files are harder to corrupt, but usually get better results than smaller files. 3. Run the Corrupter. 4. Read the warning. Know that you are not guarunteed to generate a stable/working program everytime. 5. Type in the name of your file. Don't type in "PRG" or "DAT." That is covered for you. NOTE THAT DAT FILES WITH TWO DIMENSIONS DO NOT WORK YET. 6. Type in the corruption factor - the probability that a value encountered while parsing will be corrupted, represented as a percent. 7a. [DAT ONLY] Choose the range of values to inject. For example, if you typed in 255, the corrupter would put in different values from 0-255. Different ranges work for different files. 7b. [PRG ONLY] Choose your corruption stability. 1 is for people who want no errors, but corruptions are often boring. Way to many stability checks lol. 2 is average in stability. You will get some crashes, and some things that won't be corrupted, but you can get away with some good corruptions without too many errors. I reccomend mode 2. 3 is for people who like errors; there are no stability checks. Good luck getting anything to run here. If you do somehow get lucky, which you won't, you will get some really good corruptions. Type in the number, or just press enter Lumage to go for the one you were going to choose anyway, mode 2. 8. Watch the program corrupt stuff. Larger files take more time. Some areas have more values than others. It usually never takes any longer than ten seconds. 9. Choose whether to overwrite the original file or not. If you choose no, type in the filename that you desire, without the PRG or DAT prefix. If you choose yes, you CAN'T GET YOUR ORIGINAL FILE BACK. 10. [PRG ONLY] Your program will automatically run. It may crash, and then you will get mad and throw your cat across the room. Please do not do that. This is why I reccomend EDIT mode. (You should fiddle-faddle with the corruption percentage and also hope RNGesus does things in your favor.) 11. If you get a good corruption that you like, you're free to rename OUTPUT into anything else so it doesn't get overwritten and you can share it with your friends. 12. Hide in shame

Notes:

CHANGLOG: v1.0: Initial Release v1.01: Tiny Hotfix -Modes 1 and 2 no longer break DEF statements. v1.02: Hotfix -Labels are no longer corrupted. v1.03: Hotfix -Sprite management numbers are no longer corrupted. v1.04: Hotfix -Option strict is option ded. Programs won't freak out over undefined variables. v1.05: Hotfix -Option strict detection more accurate and doesn't delete other lines of code. v1.06: Minor Content Update -Fixed option strict deleting other lines of code for real this time lol. -Removed unused code. -Added DAT file corruption. More stable than PRG corruption and have lots of data to corrupt. -Added the option to overwrite the file that you corrupted. v1.07: Hotfix -Added ability to specifiy the filename of the output. -Got rid of more unused code. -Further improvements to overall stability and other minor adjustments to enhance the user experience. v1.08: Hotfix -Minor text fixes -Option strict is completely deleted instead of being commented out FUTURE PLANS: -Make a REAL TIME corrupter -Data chunk corruption method -GRP corruption -Proper MML corruption -Corrupting Strings -Further improvements to overall stability and other minor adjustments to enhance the user experience -Jump off a bridge

Replying to:Sam
I tried your corruptor. It crashes on line 2. I look at the code: ACLS was replaced with AC'S. What the heck? lol
Any time I corrupt a program, the thing that causes the most errors is when a variable has a number in it and your corruptor changes it. For example, in many programs, there's B2=BUTTON(2), and the corruptor changes the 2 in B2 for a random number.

Replying to:Sam
I tried your corruptor. It crashes on line 2. I look at the code: ACLS was replaced with AC'S. What the heck? lol
Thank you for the bug report. This bug has been fixed (And it won't come back!)

Replying to:Sam
I tried your corruptor. It crashes on line 2. I look at the code: ACLS was replaced with AC'S. What the heck? lol
Sorry, I meant just the AC'S one lol.

I don't understand how to get past the "Inject values" question...

Replying to:Talen
I don't understand how to get past the "Inject values" question...
Sorry. I forgot to update the documentation. Basically, it's the range of values replacing the data point. For example, if you type in 255, the corruptor will replace some values with a random number between 0 and 255.

I just corrupted F-Neko at 100% and values at 500, and there was no corrupion at all, tried a few more times but different % and value, same results.

Replying to:Talen
I just corrupted F-Neko at 100% and values at 500, and there was no corrupion at all, tried a few more times but different % and value, same results.
Well, you can always try to corrupt the tons of DAT files available. More patches will be made to make programs more corruptible while maintaining their stability. EDIT: You shouldn't be using that for PRG files, only for DAT files.

Just curious, how exactly does this work? I've thought about making a sort of corrupted before that would do things like look for variables and then swap them, change certain numerical values, swap strings, etc. Is this similar?

Replying to:mystman12
Just curious, how exactly does this work? I've thought about making a sort of corrupted before that would do things like look for variables and then swap them, change certain numerical values, swap strings, etc. Is this similar?
I went the simple route, just look for numbers and change them. Of course, this led to a lot of errors. So I had to add a bunch of "safety checks" to skip over sensitive numbers. I was thinking of using the variable concept that you described in the upcoming Real Time Corruptor, which, if everything goes to plan, will come out next week.

What happens if you corrupt the corrupter and then have the corrupted corrupter corrupt a program? O.o

So... Any bugs to report? I've been having a lot of trouble with the new corruption method, so development is kind of stopped. Any errors or anything that you've been getting?

Replying to:h267
So... Any bugs to report? I've been having a lot of trouble with the new corruption method, so development is kind of stopped. Any errors or anything that you've been getting?
Nothing that I noticed, except that text gets moved off the screen sometimes. But you might have already fixed that in the latest version. I don't have the latest version. :/

Is there ANY way to uncorrupt a file? I accidentally corrupted my well worked on game and I don't want to lose all of my work. Please help.

Replying to:Alphadog_Games
Is there ANY way to uncorrupt a file? I accidentally corrupted my well worked on game and I don't want to lose all of my work. Please help.
"9. Choose whether to overwrite the original file or not. If you choose no, type in the filename that you desire, without the PRG or DAT prefix. If you choose yes, you CAN'T GET YOUR ORIGINAL FILE BACK."

Replying to:Alphadog_Games
Is there ANY way to uncorrupt a file? I accidentally corrupted my well worked on game and I don't want to lose all of my work. Please help.
Check @BACKUP.PRG

Replying to:Joshuawl
What happens if you corrupt the corrupter and then have the corrupted corrupter corrupt a program? O.o
Corruptception

Replying to:Joshuawl
What happens if you corrupt the corrupter and then have the corrupted corrupter corrupt a program? O.o
Im going to try that right now.

I entered the key and still got v1.0.6. Did you forget to update it? ๐Ÿ˜†

Replying to:HTV04
I entered the key and still got v1.0.6. Did you forget to update it? ๐Ÿ˜†
Maybe Emojis should be banned.

Replying to:HTV04
I entered the key and still got v1.0.6. Did you forget to update it? ๐Ÿ˜†
Please update this then. I wants to corrupt more programs ๐Ÿ˜ข.
Never Never. These beautiful unicode characters shall live forever mwahahahahahaahhaaha. ๐Ÿ˜ญ๐Ÿ˜’๐Ÿ˜ญ๐Ÿ˜จ๐Ÿ˜ข๐Ÿ˜ค๐Ÿ˜ด๐Ÿ˜ค๐Ÿ˜ค๐Ÿ˜ช๐Ÿ˜ญ๐Ÿ˜ฑ๐Ÿ˜ข๐Ÿคค๐Ÿ˜‘๐Ÿ˜ฏ๐Ÿ˜ช๐Ÿ˜ญ๐Ÿ˜ฏ๐Ÿคค๐Ÿ˜ฆ๐Ÿ˜ฆ๐Ÿ˜ฆ๐Ÿ˜ฐ๐Ÿ˜ถ๐Ÿ˜ช๐Ÿ˜ซ๐Ÿ˜ช๐Ÿ˜ซ๐Ÿ˜ซ๐Ÿคฅ๐Ÿคง๐Ÿค”๐Ÿ˜‘๐Ÿ˜‘๐Ÿคง๐Ÿคข๐Ÿคง๐Ÿ˜ท๐Ÿ‘น๐Ÿ˜ฎ๐Ÿ˜ˆ๐Ÿ˜ˆ๐Ÿ˜ˆ๐Ÿ˜ต๐Ÿ‘น๐Ÿ˜ฒ๐Ÿ‘บ๐Ÿ˜ฒ๐Ÿ‘บ๐Ÿ‘ป๐Ÿ‘ป๐Ÿค–๐Ÿ˜บ๐Ÿ˜ธ๐Ÿ‘Š๐Ÿป๐Ÿ‘Šโ˜ ๏ธโ˜ ๏ธ๐Ÿคž๐Ÿ’๐Ÿ‘จ๐Ÿฝ๐Ÿ‘จ๐Ÿฝ๐Ÿ‘ฉ๐Ÿผ๐Ÿ‘€๐Ÿ‘จ๐Ÿฝ๐Ÿ‘จ๐Ÿฝ๐Ÿ‘จ๐Ÿ‘ฉ