I'm getting a response of 0x0C ("Realm server did not detect a Battle.net connection") to MCP_STARTUP, but if I go on to send MCP_CHARLIST2 anyways, the MCP server lets me log in. Any ideas about what could be going on?
Does the official client have the same behavior?
I seem to recall that there was, once upon a long time ago, a bug where you could continue to talk to the MCP even after the MCP login request failed. I'd be surprised if that bug managed to resurface once again.
Would Warden have any possible influence on that?
Quote from: Skywing on November 25, 2008, 09:52:24 PM
Does the official client have the same behavior?
I seem to recall that there was, once upon a long time ago, a bug where you could continue to talk to the MCP even after the MCP login request failed. I'd be surprised if that bug managed to resurface once again.
I don't have an official client to test against, unfortunately. I just went on my bot today to refresh my realm chars, and noticed that it didn't work.
I'm confused though - if the realm server is rejecting the login because it could not find an associated BNCS connection, then how could such a bug explain that the character login succeeded?
Quote from: rabbit on November 25, 2008, 10:04:43 PM
Would Warden have any possible influence on that?
Nope, this is MCP, not D2GS.
Quote from: Camel on November 26, 2008, 01:44:25 AM
I'm confused though - if the realm server is rejecting the login because it could not find an associated BNCS connection, then how could such a bug explain that the character login succeeded?
It was more a suggestion on things to poke around with than an explanation.