This was odd. I could have sworn my brute forcing algorithm covered every possible permutation based on the mission details. I designed it entirely around the possible given keyspace. But for some reason, when I tried it at HTS, it would either succeed extremely quickly or completely fail. I didn't even know there was a problem until I actually attempted the mission at the site. Everything seemed to work perfectly with the example images I used to construct it. Did anybody else have this problem?
On a side note...
edilVin wrote:By value range, do you mean visible ASCII chars? if so, in which order should I put them together? if you can say it
You'll know you've got the correct data as soon as you see it. As far as getting that data, Defience covered the details a few posts up. If you're getting incorrect results, you might try making sure your loops are nested properly, and ensure they're reading the data in the correct X to Y order. It's a pretty common mistake.