An impostor among them... 🧐

?"ᶜ2⁶rw¹サ⁶.ᵉ³ᶠ\nナ0ユき⁶.ᵉ「゛\nナ0ユき¹ん⁶.ᵉ³ᶠ\nナ0ユき"

... What's the fewest tokens for a 'game'...?

That's pretty good, @aced ! I found him. Anyone else ?

Gold star for World's Smallest Pico-8 game ! Where's ̶w̶a̶l̶d̶o̶ Impy ?

Thanks! :-)

Here's a slightly harder one ~

?"ᶜ1⁶rw⁶.ᶠ³ᶠ\nナ0ユき¹サ⁶.ᵉ³ᶠ\nナ0ユき¹ん⁶.ᵉ³ᶠ\nナ0ユき"

Does anyone want to break down how this magic code works?

I know that ? is print, and then there's a String which encapsulates the rest of the line, but how this produces the output I can't even fathom or would even know where to refer to.

Hard puzzle indeed, @aced ... yet I see the solution.

A clue. It is not Impy this time.

If anyone wants to know the answer, I'll post a further clue as [hidden].

This game is awesome as no-one can easily read the code to see how to solve the puzzle.

@phil P8SCII Control Codes breakdown:

@Heracleum thank you for your very detailed explanation. I started playing with the code (such as putting different colours in to see the imposter easily).

I don't really understand what the purpose of the ⁶rw is ? It doesn't seem to have any effect (using PICO-8 Education Edition)

If you don't set the wrap border the characters will overflow the screen to the right. Try removing it, you'll see the first row at the top only.

I must be doing something wrong. I tried this (no print border)

?"ᶜ2¹サ⁶.ᵉ³ᶠ\nナ0ユき"

And then this (with the righthand side print border)

?"ᶜ2⁶rw¹サ⁶.ᵉ³ᶠ\nナ0ユき"

For the life of me I can't see a difference

Thanks @dw817, @phil - for your comments.
@Heracleum - thanks for the nice code dissection and using [hidden] tags to avoid the spoiler! 😜

@phil - I've just recently discovered PICO-8. I found the wiki guides really useful for character codes
and the extended print controls.

I use a bash script to convert images to encoded string literals, as part of a larger project I'm working on (http://8x8.me).

PS- I'm excited to see what else the community can create with 2 tokens :-D

@phil re. 'print border'

• Think you've found a bug/ 'feature'. Running the statement from the command line acts differently than running from a program. The command line has line wrapping already set up.

Ahah I actually considered hiding it at first... next thought was: "It takes 5 secs to spot it on the screen and would take a couple minutes to guess from the code breakdown" 😅
But sure, it's hidden now.