1. last week

    A Future of many days. A Server which holds the ongoing rhyme.

    A rhyme which in this day and age, with the old exposing, shows that the same rhyme loses its interesting chime.

    With the crunching enzyme action of slowing, the prime of activity of factions and normal play looking grime.

    While it appears to be only a matter of time, us, the Operator, acts as a waiter.

    To serve and cater... a series of codes and ciphers that will freshly paint us, factions, and the server, to tickle your minds and be in your favor.

    For the dawn of something in the distance, the existence of such will be brewing.

    Happy cracking! ( Not spam! )

    ~ Sincerely, the Operator.

  2. wow, i'm not smart enough to crack it but you seem pretty cool. hope someone cracks it soon

  3. on it

  4. Well, "=" in the end makes me think that top layer is base64 code.
    Decoder gives me this

    @0 䠰 `0 %࠰줁࠰셁࠰ࡰ셁ࡠ 䡰 0 䠰 %`0 %࠰ ࠰쥁࠰腁ࡰ셁ࡠ 䡰셁0 ࠰ `0 %࠰ $࠰쥁࠰ࡰ셑ࡠ 䠰 0 䠰 `0 %࠰줁࠰쥁ࡰࡰ ࠠ 䡰 䀰 䠰 %`0 %࠰섁࠰셁࠰ࡰ셁ࡠ 䡰 0 䡰 `0 %࠰ ࠰쥁࠰腁ࡰ셁ࡠ 䡰셁䀰 ࠰ `0 %࠰ ࠰쥁ࡰ腁ࡰ셁䠠 䠰 0 䠰 `0 %࠰ ࠰쥑࠰ࡰ ࠠ 䡰 䀰 䠰 `0 %࠰ $࠰셁࠰ࡰ셁ࡠ 䡰 䀰 䡰 `0 %࠰ ࠰쥁࠰ࡰ셑ࠠ 䡰 %0 ࠰ `0 %࠰ ࠰쥁ࡰ腁ࡰ셁䠠 䠰 0 䠰 `0 %࠰ ࠰쥁࠰ࡰ ࠠ 䡰 䀰 䠰 `0 %ࡰ ࠰셁࠰ࡰ셁ࡠ 䡰 0 䠰 %`0 %࠰ ࠰쥁࠰腁ࡰ셁ࡠ 䡰 %䀰 ࠰ `0 %࠰ ࠰쥁ࡰ腁ࡰ셁䠠 䠰 0 䠰 `0 %࠰ ࠰쥁࠰ࡰ ࠠ 䡰 䀰 䠰 `0 %ࡰ $࠰셁࠰ࡰ셁ࡠ 䡰 䀰 䠰셁`0 %࠰ ࠰쥁࠰腁ࡰ셁ࠠ 䡰셁䀰 ࠰ `0 %࠰ $࠰쥁࠰腁ࡰ셁䠠 䠰 0 䠰 `0 %࠰ $࠰쥁࠰腁ࡰ ࠠ 䡰 䀰 䠰 `0 %䠰 ࠰셁࠰ࡰ셁ࡠ 䡰 0 䠰셁`0 %࠰ ࠰쥁࠰ࡰ셁䡠 䡰 0 ࠰ `0 %࠰ $࠰쥁ࡰࡰ셁䠠 䠰 0 䠰 `0 %࠰섁࠰쥁࠰ࡰ ࠠ 䡰 䀰 䠀

    Tried de(re/en)code with multiple text codes (like utf-8), got out nothing readable.

    And here i stuck.
    Because i'm not familiar with any coding standarts, i would've done dozens of encoding with multiple codes, binary, ASCII, hex, etc, adding some distracting data, false leads, changing languages, etc.
    And i expect everyone else to do so.
    Thus, there's a fton of ways this could be originaly encoded. Need help from someone with experience.

  5. Edited last week by deyahruhd

    @Nestacdo Well, "=" in the end makes me think that top layer is base64 code.
    Decoder gives me this

    It's not base64, there's 3 equal signs being used as padding. you can only have 0, 1 or 2 on the end.
    also, the length of an encoded base64 string must be a multiple of 4, since it converts 4 base64 digits into 3 bytes. the string given has a length of 1741 which isn't a multiple of 4

    that could possibly be because Operator accidentally put some extra padding characters but 0, 1, or 2 is standard and a direct consequence of how the encoding scheme works

    what i noticed immediately is that there is a 8 character "phrase" repeated throughout the string but some letters are changed between each

    to break it apart and demonstrate:
    YDCM JAGA and so forth. i split it into groups of 4 digits since four base64 digits = 3 bytes
    the left column definitely show some kind of similarity, the right column seems to be random but there may be something there since, to be perfectly honest, i kept seeing the phrase "GAY" and "GEY" repeating over and over and over (GA and GE come from the right column pretty much always)

    my first guess is that there's probably some preprocessing we have to do to this string

  6. ^

  7. Jeez I can't make this shit up XD

  8. here is a hint

    Zkdw qxpehu wdnhv derxw vlawhhq vhfrqgv wr frxqw wrr?

  9. That looks like a ROT cipher to me

  10. The hint decoded is:

    "What number takes about sixteen seconds to count too??"

  11. @rnc2011 The hint decoded is:

    "What number takes about sixteen seconds to count too??"

    Depends on how fast one counts, I counted to 70

  12. Edited last week by Abbasilol

    @rnc2011 The hint decoded is:

    "What number takes about sixteen seconds to count too??"

    Sixteen lol? lets say we found the number then wat, hmm.

or Sign Up to reply!