MCP Question

[BaDDBLooD]

Did blizzard implement any protection against this?

Logging on a D2XP Character using D2DV

i seem to get ipbanned HORRIBLY when i accidently do this.

[OnlyMeat]

Actually i found something strange a while back, if you create a character say a sorc for example (normal d2 client) then try and create a game with it specifiying a different character type in the create game packet (custom client), when you try and log back on as that character the class has changed to the one you specified in the custom client, interesting bug 

[Blaze]

So you can change a barb into a necro?

[MyndFyre]

Did blizzard implement any protection against this?

Logging on a D2XP Character using D2DV

i seem to get ipbanned HORRIBLY when i accidently do this.

Well then, logic would indicate that it's probably protected. 

[OnlyMeat]

So you can change a barb into a necro?

It was caused by a bug in my code where it was'nt using the correct char class id in the create game packet, i created a sorc then sent 0x00 in the game packet where it should have been 0x01 which turned her into a zon in the game, then i logged bot out and logged on with real client and char was now a zon .

Of course i did'nt do any extensive testing with this because it was simply a bug in my code which i fixed.

So it may not work with characters above lvl 1 or other conditions, but feel free to try it although it might have been patched by now.

[UserLoser.]

Actually i found something strange a while back, if you create a character say a sorc for example (normal d2 client) then try and create a game with it specifiying a different character type in the create game packet (custom client), when you try and log back on as that character the class has changed to the one you specified in the custom client, interesting bug 

What byte would declare the character class in D2MCP packet 0x03?  I don't recall any byte/word/dword/ect, defining the character's class

[OnlyMeat]

Actually i found something strange a while back, if you create a character say a sorc for example (normal d2 client) then try and create a game with it specifiying a different character type in the create game packet (custom client), when you try and log back on as that character the class has changed to the one you specified in the custom client, interesting bug 

What byte would declare the character class in D2MCP packet 0x03?  I don't recall any byte/word/dword/ect, defining the character's class

I did'nt specifically mean 0x03 (Realm) but the joining game process really, it's actually the 0x67 D2GS packet i was talking about which is involved in the create//join game process, if i remember correctly the char class is at offset 0x06 within the data section portion of the out going packet.

Hope that clarifies it.