Anonymous ID: ce2200 March 14, 2026, 8:41 a.m. No.24380198   🗄️.is 🔗kun   >>0221 >>0228

>>24380159

battle.net account 2010

Likely already had an account and it was then converted to the new real ID system

99.999% sure they were using in game system for comms prior

Ex: lol=kek

 

Blizzard Real ID was first introduced in World of Warcraft with Patch 3.3.5, released in 2010, as an optional in-game feature to help players connect with real-life friends across Blizzard games. It allowed users to link their real names to their Battle.net accounts

Anonymous ID: ce2200 March 14, 2026, 8:59 a.m. No.24380244   🗄️.is 🔗kun   >>0245 >>0252 >>0253

>>24380228

Wow specifically had built in code due to cross faction chat

 

4 races of the horde can type and understand each other

4 races of alliance can type and understand each other

Horde typing near alliance scrambled the text to unintelligible garbled nonsense, but it was consistent

 

Horde player types "lol" and alliance player sees "kek"

Alliance player types "lol" and horde player sees "bur"

 

Cross faction communication was always a BIG NO so blizzard made the translations difficult to figure out, even today, 20 years later, there is no definitive way to decode it

 

People have figured out ways to say certain phrases through denial and error though

 

11 dd c = ha ll o

a way to say hello to the opposing faction if you happen upon them out in the wild

j c 108 d = n o kil l

17 13 34 3 1 p = me lo be y o u

 

spacing is required

Anonymous ID: ce2200 March 14, 2026, 9:04 a.m. No.24380253   🗄️.is 🔗kun

>>24380244

Imagine getting an email that says

11 dd c 17 13 34 3 1 p

(ha ll o me lo ve y o u)

if you knew to input that into wow chat you would have the decode

if you're an investigator you have 0 chance of decoding that

imagine the shit they could've said