PRG Shuffle
Root / Submissions / [.]
h267Created:
Download:N324DEZDVersion: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.
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.
No problem! Really easy to fix! A hotfix should be coming out for that in the next ten minutes.
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:numberor 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 STRICTon. 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!
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.
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: