Level 24

I've solved the maze and taken l__s. I've tried various stuff with the resulting path, but all it looks like is a map of Mars... Should I continue trying searching for dimensions, or is it simply irrelevant that 44622 is not a prime?

BTW: Let me express my utter joy in this challenge. After discovering this site the days of my paternity leave just fly by

I've solved the maze and taken l__s. I've tried various stuff with the resulting path, but all it looks like is a map of Mars... Should I continue trying searching for dimensions, or is it simply irrelevant that 44622 is not a prime?

I was barking up the completely wrong tree. To answer myself, It is irrelevant that 44622 is prime.

Hi,

I've solved the maze (three different ways, until I was able to get good l___s!), now I'm stuck with what those l___s tell me. I can see headers, but like ibis said, I can't process this data with either python or non-python tools. Do I need to do something with this file, or have I got a corrupt one if I can't just do-the-obvious?

Thanks in advance,

Ciaron.

[mjpieters]

I'm stuck with what those l___s tell me. I can see headers, but like ibis said, I can't process this data with either python or non-python tools.

As rspyc said earlier in this thread, you only need about half of what you found..

I'm stuck with what those l___s tell me. I can see headers, but like ibis said, I can't process this data with either python or non-python tools.

As rspyc said earlier in this thread, you only need about half of what you found..

I've already gotten rid of about half - my file is 22090 bytes. I'll go and check what I've done...

Update: Solved! It pays to be a bit more discriminating about what you get rid of and what you keep.

I can't work out what to remove from the file of length 22090...

I can't work out what to remove from the file of length 22090...

i would say: "it is the gods' colour. You will need their help today."

I can't work out what to remove from the file of length 22090...

i would say: "it is the gods' colour. You will need their help today."

If you have a file of length 22090, think of which types of byte this misses.

To answer myself, It is irrelevant that 44622 is prime.

I disagree on two counts:
a) Its primeness is relevant
b) It isn't prime

drigz:
well, 22090 isn't the magic number...
i suppose, you got it from top to bottom, and you had the number 44622;
then, take a close look at the *original* picture itself. things aren't just black and white...

That was fun!

This challenge took about 8 hours longer than it should have, because I was using Windows XP, which added native support for this file format. Both the XP support and the normal Python module recognized the file type, but were unable to correctly handle trailing data. Perhaps the tools on other OS or third-party tools are more flexible, reporting errors rather than choking.

On the plus side, I gained some familiarity with Idle's debugging tools, and even crossed the line to hack into a library module to make it noisier but less discriminating. I might be a step ahead now for a future challenge...

I'm still stuck on this one. I have a 22090 byte file and I can see that it's 'broken' in the hex editor but I don't understand how to fix it. I know the gods' color as well. What little thing am I missing?

Its not just red or black its both

EDIT: Solved. Finally. It showed that due to a bug in my A* implemetation, the only way I could find a way through the maze was by walking the walls. I deleted my actual posting, as the only thing it could possibly have caused is further confusion.

Hm... Seems that I'm a year or two too late.