(01-19-2012, 01:18 AM)AceInfinity Wrote: Yeah lol, anything over 5 dramatically increases the # of possibilities I can imagine. If you read through all my posts in this thread though you should be able to find the password based on what i've said though :) I practically gave the password away between the posts i've made haha.

(01-19-2012, 01:18 AM)AceInfinity Wrote: Yeah lol, anything over 5 dramatically increases the # of possibilities I can imagine. If you read through all my posts in this thread though you should be able to find the password based on what i've said though :) I practically gave the password away between the posts i've made haha.

That is not the point as I have already got the key from the hints.

Yeah lol, I did mention that as well :) But as long as someone understands what i've posted, the key is pretty easy to find!

Maybe it was required as this program is not as easy to solve without reverse engineering

The idea was nice, even if it had millions of solutions (over 18873 by just limiting the poll with only distinct ASCII codes from 81 to 116: AceQRSTWYq, AceQaikrs, AceReflos, AceSadlst, AceTVlnst, Acebefhim... just to name a few).
The fix posted ruined that by revealing both parts in plain text. 9 out of 10 people should try out the obvious...
How about something like:

(02-14-2012, 04:16 PM)bobdynlan Wrote: The idea was nice, even if it had millions of solutions (over 18873 by just limiting the poll with only distinct ASCII codes from 81 to 116: AceQRSTWYq, AceQaikrs, AceReflos, AceSadlst, AceTVlnst, Acebefhim... just to name a few).
The fix posted ruined that by revealing both parts in plain text. 9 out of 10 people should try out the obvious...
How about something like:

To reiterate:
Those alternative solutions apply to the original which I suspect it only differs in && str2_ == "Reboot".
That difference, altrough it fixes the error, makes it far worst than the original in terms of... challenge.
I've only wanted to restore that to it...

(02-14-2012, 07:51 PM)bobdynlan Wrote: To reiterate:
Those alternative solutions apply to the original which I suspect it only differs in && str2_ == "Reboot".
That difference, altrough it fixes the error, makes it far worst than the original in terms of... challenge.
I've only wanted to restore that to it...

You did not even bothered to read those lines of code change.

Because i've already posted this challenge some time ago, if I were to change it, how does that make it "fair" for any new attempts on this particular challenge? If you want to create a challenge, post one :)

There's absolutely no sense in changing the one that already exists halfway through when people have already solved it. New people aren't attempting to solve the same challenge if I change it drastically, so even the new patch was just a quick fix.