ANORGRAM HINT.

[+Burton wanderers]

Is there any rule preventing a cache owner using anograms as an additional hint, that is just mixing the lettres of the hint words around ! thanks. (traditional cache) or other type.

[+Great Scott!]

There are no rules against using anagrams in hints.

[+ventura_kids]

We don't have any rules.....we only have guidelines.

 

Mix em up if you want.....it's just a hint.

If a searcher wants to find the cache, they should use the coordinates

[+Burton wanderers]

We don't have any rules.....we only have guidelines.

 

Mix em up if you want.....it's just a hint.

If a searcher wants to find the cache, they should use the coordinates

 

Too many caches go straight to the hint before searching, spoling the fun dont you think? thanks for above reply.

[+fegan]

Too many caches go straight to the hint before searching, spoling the fun dont you think?

I have three caching partners who do the same thing...drives me nuts.

 

Since many paperless devices decode the hint automatically, I write my hints backwards.

[+uxorious]

You don't even have to add hints. If it bothers you some people use them, don't give them.

 

However, if a person is new they would be the most likely to need a hint, and the least likely to be paperless. It is already hard enough to decode the hint in the field, why make it harder?

Just my take on this.

[+flask]

you'll have better luck using anagrams if you spell the words in the hint correctly.

 

you should have someone proofread for you.

 

 

when i want to read the hint, i do not wish to have it be another level of puzzle. if you do not wish to provide hints, fine.

 

either give hints or don't. i don't want to have to sort through cute little puzzles or backwards writing to get the hint. if i need the provided hint, i just want to read it.

 

 

if you have a problem with people using the hint, don't give one.

 

if i see a cache with cutesy obscured hint, i don't wait until i'm in the field and need a hint to read it; i read it before i even leave the house.

 

if your intent by obscuring the hint is to try to control WHEN i use the hint and make me look first, your little control issues are actually having the opposite effect.

[+Harry Dolphin]

And then you have some annoying people who put their hint in backwards! Seems popular in North Carolina and Tennessee (not to mention Florida). Then there was the one cacher who coded his hint in ROT13 (or whatever ROT we use here.). That was actually pretty funny once I figured it out.

Answer: Nope. No rules against anagrams.

[+flask]

And then you have some annoying people who put their hint in backwards! Seems popular in North Carolina and Tennessee (not to mention Florida). Then there was the one cacher who coded his hint in ROT13 (or whatever ROT we use here.). That was actually pretty funny once I figured it out.

Answer: Nope. No rules against anagrams.

 

huh?

 

if you take something in ROT13 and put it in ROT13, you get plaintext. so his hint was already decoded?

 

or just backwards?

[+Arrow42]

And then you have some annoying people who put their hint in backwards! Seems popular in North Carolina and Tennessee (not to mention Florida). Then there was the one cacher who coded his hint in ROT13 (or whatever ROT we use here.). That was actually pretty funny once I figured it out.

Answer: Nope. No rules against anagrams.

 

huh?

 

if you take something in ROT13 and put it in ROT13, you get plaintext. so his hint was already decoded?

 

or just backwards?

 

It would look plaintext on the cache page if you didn't have it decodded... but it would be codded on the GPS or when you use the "decode" link.

[+Curioddity]

Put the hint in Morse Code.

 

Pete the Troublesome

[Keystone]

Hide your cache in a ravine. Then your encrypted hint text would be a ROT-13 palindrome.

 

ravine ==> enivar

 

Palindromic hints. THAT takes skill.

[+Chrysalides]

Since many paperless devices decode the hint automatically, I write my hints backwards.

Actually, the hints in the GPX are not encoded. The application / device will need to explicitly encode the hints.

 

If you want it to be rot13 encoded under all circumstances (even on the web page), put it inside the square brackets already uuencoded. No more one click decoding on the web page, and device will show it encoded.

 

For example, if you want to say it is magnetic, it'll look like this:

 

Additional Hints (Decrypt)

[zntargvp]

 

Clicking on decrypt will still show zntargvp, since text inside the square brackets are not touched when encrypting / decrypting.

 

Personally, I think it is annoying, but as cache owner you should be able to decide how you want to present hints - or even not give hints.

 

Oh, for hints, anything goes (as long as it is printable in the first place). Just ask yourself if it would annoy you if you see it in a cache you're searching for.

Edited September 19, 2009 by Chrysalides

[+Harry Dolphin]

Then there was the one cacher who coded his hint in ROT13. That was actually pretty funny once I figured it out.

 

huh?

 

if you take something in ROT13 and put it in ROT13, you get plaintext. so his hint was already decoded?

 

or just backwards?

 

Decoded, the hint said: HIDE8. But what you are looking for is the sign that reads: UVQR8.