Posted by: typhoonandrew | 5 December, 2008

WoW Code – show and share your passion

In an attempt to understand where players are coming from, here is a code for World of Warcraft which lets you tell folks about your passion. Who are you, your attitude, how often do you play, what classes, what levels, what style, etc.

Initially I was thinking of a Myers Brigs personality test to tell people how I’d rate them as players, but that is just making subjective judgments about players. Never good. So instead using this you can classify yourself, and tell others what you think you are.

Up front disclosure: this is darn geeky. Its akin to having an IBM monogrammed pocket protector in 1985, so if you’re one of those “chic” wow players I apologise – you may not get it.

TyphoonAndrew is

N: Mortgen, M:DK75, Mb: 8/0/57, Mr: Dr,  S: Nagrand-Oceanic-Pve, G: Epilogue, Pvp–, Pve+, Y2005.6, D+C, Ori-ZG, TBC-Gru/TK, L+, RP+. :| ,  V0.2

A few conventions used here are:

  • {term}! = not interested, never will do or participate. eg. Pve!
  • {term}++, +, present, -, — = basically gives a 5 point scale for how you view/like something.
  • {term}? = if you consider the activity silly. eg. RP?
  • Subterms are added after the main modifier. eg. D++H
  • Sub values or multiple values are separated by a “/”. eg. R: Hu+/Gn-/Dw+
  • Commas are the Term separator, which is a switch from v0.1.

And the terms are:

  • N = Name. eg N: Mortigen
  • Mc = main class. eg. Wa, Ro, DK, Wl, Pr, Ma, Dr, Hu, Pa, Sh
  • Ms = main spec. eg. Resto, Unholy, Prot, Shad; or P, S, A added to the class descriptor.
  • Mb = main build. 7/0/59
  • Mr = Main race. Hu, Gn, Sw, Ne, Dr, Be, Tr, Or, Tu, Un.
  • All combined the M statement might be: M: DK74, or M:DK-U-74, UDK74-Un, or M:DK74-7/0/57. All which mean an Unholy Undead Death Knight at level 74. Or could be broken into the separate items, if you prefer. Given how important our mians are, it was better to give a few options.
  • Alt = listing any major alts: Ro70, Pr72. Can also have spec: SPr72 (72 Shadow Priest), RPa 55 (55 Ret Pally)
  • S = Server name, location, and mode of your main server. Eonar-US-Pve.
  • G = Guild name and ranks like M = master, O = officer, R = raider, G by itself means guilded, G! not interested in joining a guild. Class and role specific officers should add: +L = loot, +class. eg. GMO+Pa is the Guildmaster and Paladin class leader.
  • Pvp = You’re a gun pvp’er Pvp++, or hate it Pvp!
  • Pr: Pvp ranking. Bracket / Season / Top rank
  • Pw: Pvp win/loss ratio. eg. Pw: 222/47
  • Pk: Pvp kills. eg. Pk: 1024
  • Pt: Old pvp title in pvp eg. Pt: Seagent
  • 2v2 = rank and record
  • 3v3 = rank and record
  • 5v5 = rank and record
  • Pve = You do a little raiding
  • Sk: Skill abbreviation, and score. EN, BS, LW, SK, HE, AL, JC, TA, MI, with the score. Also may add the specalisation if present. eg. TA375-Sh for a Shadow Tailor. eg SK:BS200/MI225/FA375/FI90/Co15
  • Y = Year.month you started playingplaying, such as Y2006.5 means May 2006.
  • D = dedication, such as ++ all the time every night, — very rarely play, H consider yourself hardcore, C consider yourself casual. A D with no adjustments means you try to play a few times a week, for at least 3 or so hours each session; but work and life can and will get in the way.
  • Ori = List most difficult instance fully cleared, then the instance you were working on before moving to the next expansion. eg. Naxx, BWL, MC, etc. Add a B if you were in the Beta. eg. Ori:B-ZG/BWL
  • TBC = List highest/most difficult instance fully cleared. eg. Kara, Mags, Sunwell, etc
  • WLK = List highest/most difficult instance fully cleared, with a number for size (10/25), and H for heroic mode. eg. Naxx10, or HNaxx25.
  • L = ++ to — for how passionate about the game lore you are. L+.
  • C = class of love or hate. Pick a class abbreviation above, and add the typical notes. eg. C:DK++/!Hu
  • R = race of love or hate. Pick Hu, Gn, Sw, Ne, Dr, Be, Tr, Or, Tu, Un and add grades. eg. R:Dr+/Gn?
  • RP = ++ to — as normal. Then add H if you’re always in character.
  • ) = Sensitiviy, D almost never offended, ) not easily offended, | good natured, ( I’m sensitive, :X no sense of humour.
  • V = version of this code. This is 0.3.

Additions and suggestions welcome. I don’t do pvp so I’m unsure of how best to classify the ranks and achivements of pvp players, especially the old rankings.

I first saw this concept in an Ars Magica roleplaying forum many years ago; thanks to the ArM Code for the basic idea.

Edit: will be updated soon, so throw in you suggestions for PVP classification. Also I’m thinking that an XML version that is parsed by a web script might be a great way to kill my time offline over Christmas.

And thanks to Massively for the 1000 hits in a day on the 23rd, nice to see a traffic spike.


Responses

  1. Outstanding. Thank you so much.

  2. Also, wasn’t the geekcode the canonical one? Probably worth a mention. At any rate, I’m bubbling with anticipation.

  3. That was my first reaction – it’s the geek code Warcraftified! Nice one! I will have to spend some time putting mine together.. right now I’m too sick :(

    Oh – you need to write a parser that will translate the code for you heh. I remember that the geek code had one. Of course having to use a translator isn’t very geeky but oh well.

  4. This is great, although I don’t think my brain can handle writing mine out after the heroic grind I’ve had today. As said by Jezrael… we need us a translator. =)

  5. [...] Mr: Be; S: Lightbringer-EU-PVE; G: Prophecy; PVP-; PVE+; Y: 2005.5; D:++C; Ori: ZA; L++; ; V0.1 WoW Code – show and share your passion TyphoonAndrew’s – Eye of the Storm __________________ It is time now, my friends, to take a stand, to proudly proclaim what it is [...]

  6. [...] out the WoW Code from Typhoon Andrew – a quick glance at who we are, and what we enjoy in the big wide world of [...]

  7. [...] – and I’m only surprised this hadn’t happened sooner – Typhoon Andrew has come up with a WoW version, a quick and easy way of summing up your WoW focus and [...]

  8. Coding an web form is about as far as I could go, and even then it would be messy as hell.

    I’ll have to get one of the Devs at work on to it (wishful thinking). :)

  9. This is funny. I remember using the Geek Code back before the web. (Yes, I was there before everything was about www AND I play WoW.) :P

    Great memories and great job!

  10. I love this!

    M:Pa80, Ms:H, Mb:51/5/15, Mr:Be, S:Hyjal-US-Pve, G:Schadenfreudian Slips, Pvp, Pve++, Y2005.2, D+C, TBC-Kara, L, C:Pa++,Hu-;R:Un,Be;RP,:|,v0.1

  11. [...] all that mean? First check out Typhoon Andrew’s post on WoW Code, then check out a few others, such as Isisxotic’s, Siha’s, Andrea’s, and [...]

  12. Hmm, very cool! Could do with a faction of choice option too :D

  13. Geez. Geek.

    *puts his wow code on his blog’s sidebar*

  14. [...] and lastly one over at The Pink Pigtail Inn. All were found to be using a code first referenced by Typhoon Andrew. It seems to be a way to sum up your entire Wow career in a single line of coded text. I decided to [...]

  15. [...] would appear that Geekcode has been given the WoW treatment by TyphoonAndrew in the form of WoW Code… Awesome I say! I was always a fan of Geekcode (GS d@>- s>+:(+) a– C$@>++++ [...]

  16. Ok, this code doesn’t go as far as the real geek code in terms of non-geek readability, but who cares. I really like it. But maybe a consistent way of determining code identifier and value would be nice.

    Like in most of them it is identifier:value(s) whereas sometimes it is identifier-value(s), another time (Dedication) it is a simple identifier values. And, for Loved Race and Class the values are comma seperated as well as the whole code is comma seperated. there is of course a missing break! ;)

    just my 2 cents for improvement?

  17. btw: forgot mine:

    M: Pr76-5/0/61-Be, S:Aegwynn-EU-PvP, G: Söldner des Schattens, PvP–, PvE+,Y2005.10, D+C, Ori-BWL, TBC-BT, L+, C: Dr++, Pr++, Wl+, Dk+,Ma+, Ro-, R: Or++, Tr++, Ud++, Be+, Ne+, Gn?, Hu–, RP-, :| , V0.1

  18. @heppa – you’re right. My geek cred and code skills have degraded in the years since I’ve stopped being a sysadmin. Now I get the techs and devs to formulate the solution based on my sketchy whiteboard diagrams. I know they just love them.

    I’ll do a v0.2 soon, as soon as I figure out or somebody tells me what in hell to list in pvp; and then I can roll up all the improvements mentioned here too.

    Doing updates for documentation is too close to work for me to enjoy on a weeknight.

  19. what in hell to list in pvp
    - Bracket / Season / Top rank
    - Pre 1.12 title if you have one
    - HKs
    - BG win / loss ratio

    That probably covers most of it

  20. Maybe a modifier to the raiding that would show the highest instance you raided in, even if you didn’t fully clear it? Like TBC-Gruul/BT meaning you cleared Gruul’s, but raided into BT before Wrath came out.

  21. Delightful. Yet another reason to waste time at work.

    Cheers.

  22. [...] 2008 at 10:57 am (Random Stuff) Aparently we all remember Geek Code because there’s now a WoW version.  Simply because it amuses [...]

  23. Hmm… what about N:[name] at the beginning? :)

  24. [...] I’m not old enough to remember the IBM code, but TyphoonAndrew has come up with a WoW version. [...]

  25. [...] No idea what i’m talking about?  Check out Typhoon Andrew’s post. [...]

  26. Ha! I like the idea…when I have time I’ll jot my code down.

  27. [...] – to end this on a silly/fun note – Typhoon Andrew, over at Eye of the Storm, has developed a WoW Code – here’s mine: N:Anna, M: Pa80-Hu-Holy/Sh75-Dr-Resto, Alt: [...]

  28. N: Skarlarth, M: Dw-Hu-77-MM-04/53/11, Alt: Hu-Pa-71-Prot / Dw-Pr-71-Hly-Dsc / Ne-Dr-70-Bal / Ne-Hu-70-BM / Hu-Ro-70-Com / Dr-Sh-70-Ele, S: Medivh-USE-PVE, G: The Kaldorei / GM, PvP: Present, PvE: ++, Y: 2004.12, D: +C, Ori: Ony, TBC: Mags, WLK: DK, L: +, RP: Present, :) , V0.2

    Being an alt geek and a beliver in being “an economy unto myself” what about adding Crafting tags?

    Awesome, btw; I have my new Sig file.

  29. I hope to see trade skills in a future version!

  30. Updated with SK to indicate skills, holds skill abbreviation, level, specialisation for trade and secondary skills.

    Nice suggestion!

  31. [...] on the Eye of the Storm blog, Typhoon Andrew has created a new internet self-classification code to reflect those with a passion [...]

  32. I’d love a way to indicate Hunter Pet type and Warlock Minions.

    Maybe the number of vanity pets and mounts too, for the obsessed collectors.

    Also, number of achievements completed, or achievement points could be good.

  33. [...] time to break it down, but TyphoonAndrew at The Eye of the Storm blog has already done that in an easy to read format. Now if you could excuse us, we’re going to go break out our Tandys and play some extreme [...]

  34. [...] here is an interesting one… WoW Code from TyphoonAndrew’s blog. The basic concept is, you replace terms with your information. But the conventions are zooming [...]

  35. [...] time to break it down, but TyphoonAndrew at The Eye of the Storm blog has already done that in an easy to read format. Now if you could excuse us, we’re going to go break out our Tandys and play some extreme [...]

  36. En-Gob for goblin engineer, and En-Gno for Gnomish engineer in the skill section

    N:Lîlîth,Mc:Pa80,Mb:56/0/15,Mr:Be,S:Crushridge-US-PvP,GO:Premature Consecration,Pvp-,Pve+,Sk:MI450/En-Gob435,Y2007.5,D+C,Ori:AQ40,TBC:Mags,WLK:AN,L++,RP-,:),V0.3

  37. [...] Chi gira su internet da almeno un decennio sicuramente si ricorderà del geek code, utilizzato in firme di forum, finger, profili di community, eccetera eccetera. Analogamente a quel codice che per anni è rimasto di nicchia, si sta diffondendo ultimamente tra i giocatori di World of Warcraft il WoW Code: se vi state chiedendo cosa sono quella sfilza di codici, -, +, eccetera nelle firme di alcuni giocatori sui vari forum, trovate la risposta a questo indirizzo! [...]

  38. [...] time to break it down, but TyphoonAndrew at The Eye of the Storm blog has already done that in an easy to read format. Now if you could excuse us, we’re going to go break out our Tandys and play some extreme [...]

  39. [...] Typhoon Andrew for reviving the geek code [...]

  40. [...] Typhoon Andrew for reviving the geek code [...]

  41. [...] time to break it down, but TyphoonAndrew at The Eye of the Storm blog has already done that in an easy to read format. Now if you could excuse us, we’re going to go break out our Tandys and play some extreme [...]


Leave a response

Your response:

Categories