TehGuy

Aye, the server isn't the one having issues, I don't think, but the client executables (both 32- and 64-bit) after applying the connection patcher on them so that's why I feel it has something to do with that (normal Blizz client works just fine). I've been pulling builds as they get released and rebuilding in hopes it stops, but it's a persistent issue :/

Whatever it was, it seems to have been fixed in a recent commit as I've just pulled the 3.3.5 branch a couple of minutes ago and got a successful x64 build Compiled using Visual Studio 2015 on Windows 10 Pro x64

Right, messing about with the 6.x branch, I can get in and do stuff just fine; however, within 5 minutes the entire client will seize up and then crash. Wondering what was up, I opened task manager and launched WoW again. At the point the freeze happens, the executable just begins to consume ram (the non-64 bit exe will crash before hitting 4 GB, I did not dare wait to see how far the other would go) until it hard crashes. After messing around on the live retail client, this doesn't occur at all. I'd just like to know if this is some mess-up on my end that I can fix or there's actually a problem somewhere addendum: the log always ends with something like this, if it helps No defined handler for opcode [UNKNOWN OPCODE 0x158E (5518)] sent by [Player: Danath GUID Full: 0x08000400000000000000000000000001 Type: Player Entry: 0 Low: 1, Account: 3] Received not handled opcode [CMSG_CLOSE_INTERACTION 0x001D (29)] from [Player: Danath GUID Full: 0x08000400000000000000000000000001 Type: Player Entry: 0 Low: 1, Account: 3] Prevented sending of [SMSG_LOOT_RELEASE 0x12E7 (4839)] to non existent socket 0 to [Player: Danath GUID Full: 0x08000400000000000000000000000001 Type: Player Entry: 0 Low: 1, Account: 3] Prevented sending of [SMSG_AURA_UPDATE 0x10AF (4271)] to non existent socket 1 to [Player: Danath GUID Full: 0x08000400000000000000000000000001 Type: Player Entry: 0 Low: 1, Account: 3] Prevented sending of [SMSG_CANCEL_COMBAT 0x02DB (731)] to non existent socket 0 to [Player: Danath GUID Full: 0x08000400000000000000000000000001 Type: Player Entry: 0 Low: 1, Account: 3] Prevented sending of [SMSG_UPDATE_OBJECT 0x026B (619)] to non existent socket 1 to [Player: Danath GUID Full: 0x08000400000000000000000000000001 Type: Player Entry: 0 Low: 1, Account: 3] Prevented sending of [SMSG_LOGOUT_COMPLETE 0x16EF (5871)] to non existent socket 0 to [Player: Account: 3]

So after finally managing to follow through the tutorial without issue (tried a long time ago, but I guess I just didn't know what I was doing), I'm now running into this Realm Loop problem.. It takes the 'test' 'test' credentials just fine and I can select the Trinity realm but then it just boots me right back to the realm selection after some 2-3 seconds of trying, no errors are spat back at me and nothing new pops up on either worldserver or authserver terminals. I've got the worldserver and authserver set up in an Ubuntu 15.10 x64 VM, if it matters, and the IPs in the conf files have been changed to reflect the fact that WoW and the TC server are not running on the same machine/IP. All relevant ports have been forwarded as well This is for WoW 3.3.5a, by the way ALSO, the authserver seems to want to ignore whatever name I put in the MySQL database under that 'realmlist' table; it just keeps saying 'Added realm "Trinity" at 127.0.0.1:8085' EDIT: OK, so the MySQL Workbench client I was running on the Windows side wasn't making the changes I thought it was making (basically none at all). I managed to solve my issue using this guide (http://www.reaper-x.com/2007/07/03/creating-public-server-for-lan-party-setting-up-private-wow-server/) which helped me make the needed changes on the Ubuntu side =3=