Fun. I do like how you hide your data. That's a track I've been exploring - hide the data well, and then try to write obfuscated code to decrypt it.

The heavy-hitting obfuscators here could give you more advice, but something I'm just learning now is more misdirection. A stage magician learns not only how to palm an object well, but also how to direct focus to something else while doing it. After working through your spacing, alternate quotes, and use of a confusing variable, you still have well hidden data but it can be worked out. If there was more in there that looked important but wasn't it would add another layer.

Two ideas along that range would of been calls that seemed to to important but wereent, and extra, false, characters in your character list.

Of course, I'm still struggling to do something like that in the first place. 8) Don't take this as a critism - I liked it quite a bit. Just sharing my thoughts as I work towards better obfuscations myself. Other good tricks to hiding would include functions that can take a different number of arguments then normal. For example, split can take a limit as a third parameter - imagine using that to weed out false data which would otherwise mess up your data order from the sort.

Hope these comments have been useful. I like it, ++.

=Blue
...you might be eaten by a grue...