Plus Emu 2.1 [CamWij's | Wesley's edit] | Client stuck @ 87%

Hey guys, I am using Wesley's Plus Emu edit, I've tried 2 different databases, and to no avail. I've tried 2 different clients, one static and one linked with the CMS, I've tried forcing the SSO, etc..

The client seems to get stuck at 87%, then sits there for a bit, and then redirects me to http://localhost/game/

The emulator seems to be receiving a connection, but a unhandled header, here's a print screen:
http://prntscr.com/4hvz8y

Here's a print screen of my client2.php file:
http://prntscr.com/4hvze3

The SSO ticket is linked with an account on the database.

There are NO javascript errors in Google Chrome.

I am using the SWF build: RELEASE63-201405071257-197450526 (is that the correct one?)

I've checked the ports, they're correct (30000)

I've checked all the links, so I don't know where the problem resides..

My external_variables: http://pastebin.com/tRDKgXek


All help is highly appreciated! :blush:

Like I said in the other thread, you're using the wrong Habbo.swf. The Habbo.swf that should be used is for the original Plus emulator released back in march / april.

Update the headers or find the correct Habbo.swf. I don't know what release should be used with it so can't help you with that.

I managed to somewhat get it working, it loads the client, and welcome message, although it disconnects me right away, I changed the Habbo SWF to "RELEASE63-201401301855-255051757" which somewhat seems to work.. Console print screen: http://prntscr.com/4hwr19 - I will be working backend to see if I can fix the error myself, but if anyone has any information that can help me fix it, let me know. @The General

- - - Updated - - -

Managed to get the client to load. Will post any error updates.

I don't know the issue. It is probably your configuration as everything used to work fine back when we used it.

Quote:

---

Originally Posted by The General

I don't know the issue. It is probably your configuration as everything used to work fine back when we used it.

---

Yeah it was exactly the SWF version :) For anyone who comes accross the same problem as me, the SWF version that works (for me at least) is: RELEASE63-201401301855-255051757