11
Given the output of the cop's program (o
), the byte-count (n
) and the number of unique bytes (c
) used, come up with a corresponding piece of code that is n
bytes long with c
unique bytes which matches the cop's output o
.
This is the robbers thread. Post solutions that you cracked here.
The COPS thread is located here.
Robbers should post solutions like this:
#[Language], `n` Bytes, `c` Unique Bytes (Cracked)[Original Link to Cop Thread]
[Solution]
(Explanation)
Rules
- You may not take any input for your program.
- The program must use at least 1 byte, but cannot exceed 255 bytes.
- The output itself is also limited to 255 bytes.
- The program must have consistent output results when executed multiple times.
- If your submission is not cracked within 7 days, you may mark it as "safe".
- When marking it safe, post the intended solution and score it as
c*n
.
- When marking it safe, post the intended solution and score it as
Winning
- The uncracked post with the lowest
c*n
score, wins the cop's thread. - Whomever cracks the most wins the robbers thread, with earliest crack breaking the tie.
- This will be decided after 10 safe answers, or a few weeks.
Caveats
- If you feel cocky, you may tell the user the algorithm using a spoiler tag.
Note: Also, please remember to upvote cracks, they're usually the impressive part.
You know all the predefined literals... I don't... It wasn't exactly the same as I had, but it was of course the product of
'double'
. :) – Stewie Griffin – 2017-11-10T10:16:19.020@StewieGriffin Ah, I see, so you used something like
1X%p
. Actually I only know a few predefined literals. I brute-forced with9:"@X1pD
changingX
and1
– Luis Mendo – 2017-11-10T10:32:23.610