“Code” is often a catch-all word in puzzles. A more useful question is what you need to do with the message: replace letters, rearrange them, or read a different set of symbols. Look at the rule and the key, rather than relying on the name alone.
Compare three operations
| Method | What happens to MAP | Key or convention | How to reverse |
|---|---|---|---|
| Caesar | PDS | Shift 3 | Subtract 3 from each index |
| A1Z26 | 13-1-16 | A = 1; hyphen-delimited tokens | Look up each number |
| International Morse | -- .- .--. | Spaces separate letters | Look up each Morse token |
A letter transformation
MAPCaesar; shift 3PDSCaesar replaces each letter with another letter chosen by a shift. A1Z26 writes alphabet positions as numbers, and Morse writes characters as dots and dashes. The A1Z26 and Morse tools here use fixed charts, with no secret key to choose.
What do you need to decode a message?
- Which alphabet or character set is supported?
- Does a key select the mapping, or is the mapping fixed?
- Which separators mark characters and words?
- Are spaces, punctuation, or letter distinctions removed before the operation?
- What exactly can decoding recover?
Use precise instructions in a puzzle
Give your solver enough information to get started. For an A1Z26 puzzle, say “A = 1; hyphens separate letters; / separates words.” For a Caesar exercise with a known key, give the shift and state whether the task is to encode or decode.
In its narrower historical sense, a code can use a codebook to replace whole words or phrases. The tools here work with letters, pairs, grids, and written symbols instead.
Try a quick comparison
A puzzle gives 13-1-16 and supplies an A1Z26 chart. What extra key is needed?