If you guys don't like endless arguments over linguistic philosophy and game mechanics that nobody in the argument even uses, what are you doing here?
Kinda funny that in this debate both Aaron and Dif turned up after being absent for ages. I guess it's nostalgic or something.
Define "code", I think this is close to the centre of the disagreement.
"Activate Order 66" isn't a coded message, though. Not in the way that something passed through ROT13 is a coded message. It's a message written in unscrambled plaintext that just refers to some totally different document. The argument here is that it isn't code.
It won't give you either of those things, because that's not a ciphered message. It means *exactly* what it looks like it says: Upon receiving this message, execute Order 66. It's just that you don't know what Order 66 is. That's not code, that's just knowledge you don't have. If you DID know what Order 66 was, the message would still just mean "execute Order 66."
To me, a code is something that replaces words in order to prevent people who don't know the code from understanding what you're saying.
I actually quite like the definition you get when you google code definition, so I don't think I'm being weird about this. "a system of words, letters, figures, or other symbols substituted for other words, letters, etc., especially for the purposes of secrecy." suits me just fine.
Anyway, saying word X instead of word Y is the ur-code. The basic code. The code that you don't even have to invent. If you can't handle that, how can you handle any code? And isn't this the very definition of "the signals in a coded exchange"?
The Order 66 example is interesting because, if the code used the same words with a non-code-related intention, I don't think the Charm would work.
Answers (you get):
1. "execute Order 66"
2-4: per the text of the Charm, you get the full text. Depending on the nature of the game and the communication (including length), I might discuss giving the PC just clues as to the nature of the book/some tool they might want to solve it.
5. "kill them."
6. They can see the ROT13 cypher, but their intuition is that there's some deeper message buried in there, but they can't explain why or what it is (possibly have them make a roll off here v. some static difficulty or the writer of this plan's stats, akin to the Letter-in-a-Letter use)
1. "Execute Order 66".
2. "This is a coordinate system likely for a book cipher and you own the book. The plaintext message is as follows."
3. "This is a coordinate system likely for a book cipher and these are the relevant details that can help you find which book."
4. Cracks the message (I assume you're talking RSA, and I assume you have the public key).
5. "Kill them", but if I had the time I'd also generate a bunch of other valid strings that could be generated from applying different simple decryption algorithms to the string. I'd put "Kill them" at the top of the list as vastly most probable. I will also not tell the player which "them" the recipient is supposed to kill.
6. Same as above, but I'd throw in "There's something hidden in here I don't have the secondary information to understand because (side channel leakage, whatever), it probably doesn't mean just that. I should probably thoroughly scour this room with my Investigation Charms.".
1-5, I get where each of you is coming from.
6, though...you are deliberately rewriting the Charm here, right? Because the Charm as written is totally all-or-nothing. As I said before it's a code-ignoring Charm rather than a code-breaking Charm. It's not written to give you the ROT13 meaning on a message that wasn't ROT13'd. Whether DSE succeeds against the OTP or fails, I don't see any way for "browse ciphered manuscripts as though they were in the original language" to give you insight into a cipher that wasn't used but could've been.
I'm not saying there's anything wrong with changing the Charm's effect; god knows I've rewritten more than my share of Exalted. But that is what you're doing, right?
Questions for you:
-What would you have the Charm do on messages in foreign languages.
-What would you have the Charm do where there are ambiguous meanings—it passed through a chain of three proxies, each of whom thought it was for something different, before coming to you.
-What would you have the Charm do if it tells the person to consult a 20 volume manuscript and take the option said manuscript recommends, if that results in very specific tactical suggestions (e.g. the person is saying, in effect, 200+ different if/then options).
Edit:
-What would you have the Charm do on a message that says "build a crossbow" where the reader has no idea how to make a crossbow. Does it given them step-by-step instructions? Does it tell them what kind of wood to use?
edit: I just noticed that "in its original language" implies that if you don't understand the original language, you still don't understand the message. Hmm. Thoughts?
Okay, a question for you: do I get the entire contents of that shelf in the Imperial taxman's office when I read the memo telling Accountant Alex to study it?
My reading is that the "original language" specifically excludes foreign languages from the effect of the Charm. Sure, a language is kind of like a code, but the Charm's not meant to do that.
In the case of multiple proxies, I'd say the Charm lets you understand the intent of the one who actually wrote the physical message in front of you.
I don't think the Charm can be used to compress information through book references. However, if the book references are being used as an obtuse way to hide the actual meaning of the message, that meaning is revealed. But of course the meaning can't be much longer than the message.
For similar reasons, the Charm does not explain how to make a crossbow.
I think this all follows naturally from the conceptual perspective I laid out earlier. You get what the message "really means", and all attempts to obfuscate that meaning are defeated. But if something isn't an attempt at obfuscation, the Charm doesn't do anything with it.
It's pretty weird that the Charm can give different results from the same message, but as your answers showed that's pretty unavoidable. And I think my interpretation makes it more feature than bug, by using it to get around chicanery. Kind of a Judge's Ear Technique situation, come to think of it.