[Help] Updating to new UI [Help]

[Chrobens]

So I am attempting to update Mango Emulator to PRODUCTION-201511261225-165895972...
And here I am so far...

No Events proceed after this execution, I need help understanding what I must do, as I am new to this :]

 

[Yadz]

Mango Emulator does not work with that build, unless you've fixed it yourself.

 

[Chrobens]

Mango Emulator does not work with that build, unless you've fixed it yourself.

It Certainly does as I've had an older PRODUCTION revision used with it

 

[Jaden]

It Certainly does as I've had an older PRODUCTION revision used with it

Tempted to help you, although you did try to have a go at me if I remember correctly...

 

[Chrobens]

Tempted to help you, although you did try to have a go at me if I remember correctly...

I indeed attempted to criticize you
But help threads are help threads

 

[Jaden]

I indeed attempted to criticize you
But help threads are help threads

What does your client-side console log say?

 

[Chrobens]

What does your client-side console log say?

Actually I reversed all my implements and am now back at square one mango
 

Actually I reversed all my implements and am now back at square one mango

However I still have the .swf and all the tools necessary

 

[Jaden]

Actually I reversed all my implements and am now back at square one mango

Well first, Mango doesn't have any encryption, so if you don't have RC4 patched you're going to need this...

Latest Encryption:

You must be registered for see links

and PRODUCTION added something to their encryption if I'm correct, that's why I recommend using this.

Also, make sure all your headers are correct, I'd start out with the handshake packets to make sure I have the correct headers.
There will be a few outgoing packets you'll have to adjust so the client sends back the proper structure since you're going directly from 2012 to 2014.
That's it?

 

[Chrobens]

Well first, Mango doesn't have any encryption, so if you don't have RC4 patched you're going to need this...

Latest Encryption:

You must be registered for see links

and PRODUCTION added something to their encryption if I'm correct, that's why I recommend using this.

Also, make sure all your headers are correct, I'd start out with the handshake packets to make sure I have the correct headers.
There will be a few outgoing packets you'll have to adjust so the client sends back the proper structure since you're going directly from 2012 to 2014.
That's it?

I'm using Joopie's HabboEncryption V2 :] and I disabled the RC4 on the PRODUCTION SWF anyway, cracked it
It just doesn't send back anything after the CryptoComposer, I've looked in the habbo scripts and compared current to new and got the corresponding id for the composer but seems to just be wrong

 

[Jaden]

I'm using Joopie's HabboEncryption V2 :] and I disabled the RC4 on the PRODUCTION SWF anyway, cracked it
It just doesn't send back anything after the CryptoComposer, I've looked in the habbo scripts and compared current to new and got the corresponding id for the composer but seems to just be wrong

If you patched RC4... why are you using any encryption? You'll end up getting the wrong packet id's.
Also, you need to take a look at the InitCryptoMessageEvent class and make sure it's not sending any valid DH keys.

 

[Chrobens]

If you patched RC4... why are you using any encryption? You'll end up getting the wrong packet id's.
Also, you need to take a look at the InitCryptoMessageEvent class and make sure it's not sending any valid DH keys.

Oh no I'm not using Encryption, I just have it implemented
And the init crypto just sends "Mango Emulator"
"Disabled Crypto" :]
 

Oh no I'm not using Encryption, I just have it implemented
And the init crypto just sends "Mango Emulator"
"Disabled Crypto" :]

Opposed to it sending a new BigIntDH Key