LoginLogin

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

Nice

Key isn't working.

Sorry if anyone couldn't download it. It's fixed now.

Sadly I couldn't corrupt anything.

Wah! This is really cool! Good job Tgame! Super Neat!

Replying to:Talen
Sadly I couldn't corrupt anything.
You have to play around with the 3 modes and the corruption percent until you get something you like. Future patches will make this easier.

Breaks DEFs that have numbers in them, please fix

Replying to:Perska
Breaks DEFs that have numbers in them, please fix
No problem! Really easy to fix! A hotfix should be coming out for that in the next ten minutes.

Every time I corrupt something i get a variable error running the output, anyway to fix this?

Replying to:Miopasid
Every time I corrupt something i get a variable error running the output, anyway to fix this?
Uhh... could you be more specific? I may be able to make another hotfix real quick if I find the source of the problem. Also of you set the corruption percent lower it has a better chance of skipping over where the error happens. That is a temporary fix.

Replying to:Miopasid
Every time I corrupt something i get a variable error running the output, anyway to fix this?
When I corrupt a program it shows
Undefined variable in number:number
or any variable error

Replying to:Miopasid
Every time I corrupt something i get a variable error running the output, anyway to fix this?
It looks like you are corrupting a program with
OPTION STRICT
on. This will take a bit longer to fix, but I will work on it.

Replying to:Miopasid
Every time I corrupt something i get a variable error running the output, anyway to fix this?
OK thanks for the answer

Replying to:Miopasid
Every time I corrupt something i get a variable error running the output, anyway to fix this?
Your issue has been patched. Thanks for the bug report!

What is a REAL TIME corruptor? Like, what's the difference?

Replying to:Talen
What is a REAL TIME corruptor? Like, what's the difference?
The program gets corrupted while you run it. Real time corrupting is more dynamic in the fact that variables that would normally only be corrupted once will be corrupted multiple times at certain time intervals to make the corruptions more entertaining.

Every time I go to corrupt, I get a syntax error on line 592 of my game called Lazer Wars. If you need more details, just download Lazer Wars and test it for yourself.

Replying to:Joshuawl
Every time I go to corrupt, I get a syntax error on line 592 of my game called Lazer Wars. If you need more details, just download Lazer Wars and test it for yourself.
Thanks for the bug report. The root cause was faulty option strict testing. Only four characters to find part of option strict wasn't enough. This has been fixed now. The hotfix is coming out right now:

Is this Nick?

I tried your corruptor. It crashes on line 2. I look at the code: ACLS was replaced with AC'S. What the heck? lol