Nice to see the GUID documentation expanded. Clearly a API that's very interesting to read about. :)
Hi, i think some information on the unitGUID is incorrect, Relating to the 0xXXX part of the ID String, i'm not sure what is what (i'm still trying to work it out), but here are some examples i have gotten so far:-
- 0xF1300040884A1D5E - Vale Moth
- 0xF430004088528CCF - Vale Moth
- 0xF7300040881EB93A - Vale Moth
The parts of the string are correctly identified (ie unit type, 000's, mob id, and spawn number) it's just the unit type that seems to have different values as indicated in the wiki page.
- I have to say I don't really see what the problem is. To me they all look like proper guids for a Vale Moth.
0xF13 & 0x00F == 0x003 0xF43 & 0x00F == 0x003 0xF73 & 0x00F == 0x003
- They all have 4088 as NPC ID which converted to decimal is 16520 - . Te spawn counter is hard to comment on.
- Tanoh (talk) 09:24, 23 December 2008 (UTC)
I added information for the pet GUID based on my testing with a bunch of gnome warlocks. I created four of them. Then I leveled them until I got the quest that gives you the imp. Then I turned it in with each of them and checked the GUID. I have checked the GUID after restarts for a couple months and the pet id part has stayed the same. I believe I summoned the imps for the first time in a different order as well, but I did not save that data.
Based on the data I believe the middle of the pet GUID is a simple counter for all pets. I'll be doing another test to check this using both hunters and warlocks in case the pet type makes a difference.
|Character||Order Receiving Quest||Order of Quest Turn ins||GUID|
Unit type mask change Edit
I've changed the text that suggested that masking the top of the GUID with 0x00f will yield 0x000 for players: several European realms in various languages now appear to hand out player GUIDs that begin with something like 0x058: the key point is that one of bits previously assumed to be used for type is now apparently set for players, indicating a different purpose. Masking the top of the guid with 0x007 instead of 0x00f would solve the issue. -- foxlit (talk) 15:47, 6 June 2009 (UTC)