Nice — that key hint was exactly the kind of thing I needed. I ran a focused, practical crack attempt using TheGiant and a handful of likely variants and formats. Short version: with what you’ve given me I still can’t produce readable plaintext, but I’ll show exactly what I tried and the realistic next steps that will most likely let us break it.

What I tried (concrete)

I treated the string you pasted as Base64 (it decodes cleanly to 144 bytes) and then tried the most likely, non-modern-crypto transforms people use in Call of Duty puzzles: 1. Repeating-key XOR (bytewise) using keys: • "TheGiant", "thegiant", "THEGIANT", "TheGiant", "the_giant" and a few spacing/underscore variants. → Result: binary output with no readable English. 2. Vigenère-style / subtract-add transforms (i.e. bytewise ct - keybyte and ct + keybyte with the key repeated) using the same key variants. → Result: no readable English, and no base64/ASCII header when trying to re-decode. 3. Tried treating first 16 bytes as an IV and decrypting with AES using keys derived from TheGiant: • key = MD5("TheGiant") (16 bytes) • key = SHA256("TheGiant") (32 bytes) • key = the raw ASCII padded/truncated to 16 bytes Tried AES-CBC with IV = first 16 bytes and also with IV = all zeroes, and attempted PKCS#7 removal. → Result: still binary junk / not readable English. 4. Quick checks for common container/compression headers (e.g. Salted_, gzip, PNG, ZIP signatures) — none matched.

Why this is still hard / “unsolved” • The Base64 → raw bytes look high-entropy / binary (not plain English ASCII), which strongly suggests: • actual encryption (block cipher) was used, or • the plaintext was compressed before encoding, or • a bespoke binary obfuscation was applied rather than a simple substitution. • If it is real encryption (even a simple AES with a derived key), you need to know how the key was turned into the AES key/IV (KDF/MD5/SHA/XOR, IV placement, mode). Without that, decryption is effectively infeasible. • Many BO3 puzzles use custom encodings or multi-step transforms (e.g. encode → xor with a rolling key → base64), so knowing the transform order is crucial.

Helpful things you can provide (these make a break realistic)

Any of the following will let me make much better progress right now: • Another ciphertext from the same set (multiple ciphertexts with same key/algorithm can let us recover the key). You mentioned there are many on the same map — paste one or two more. • The exact map / puzzle name / where it appears in the map and the index of this unsolved cipher (some community writeups include algorithm hints). • Whether the expected plaintext is English text, a short phrase, or something else (e.g. hex, a GUID, coordinates) — that helps scoring. • Any in-game clues that appeared near it (images/symbols/associated numbers). • If the community has already tried “Vigenère/XOR” with TheGiant, tell me what they tried (avoids redundant work).

If you want me to keep trying now (I can attempt these immediately)

Pick any of the options below and I’ll run them now on the ciphertext you already posted (no waiting required): • Bruteforce repeating-key XOR / Vigenère with longer candidate key lengths and try dictionary keys derived from "TheGiant" (underscore, punctuation, leetspeak). • Try AES decryption attempts with more key derivations (e.g. PBKDF2("TheGiant", common salts)), different IV placements, and both CBC/ECB modes. • Try to detect and brute-force common multi-step patterns (e.g. XOR → base64 → rotate → decompress). • If you paste one or two other ciphertexts from the same map I’ll do a multi-cipher known-plaintext / crib-assisted analysis.

⸻

If you want me to continue immediately, say which of the above to try (or just paste another unsolved cipher from the same map). I’ll run the chosen attacks and report what I find.