[Dbc, Maps, mmaps, Vmaps problems]

On ‎4‎/‎7‎/‎2016‎ ‎9‎:‎07‎:‎06‎, JChryst said:

I am having issues with mapextractor on GNU/Linux (Ubuntu 14.04.1 LTS; Kernel 4.2.0-35-generic; x86_64).  When I run mapextreactor in my WoW client directory I get the following output:

Map & DBC Extractor
===================

No locales detected

I believe that I am on the 3.3.5 branch.  Server and tools appear to have been built successfully.  I have tried various client installs from Mac to Windows to WINE; all with the same results.  I have tried various locations using the -i switch, symlinks to executable, etc.  Source code was pulled a week ago and compiled.  I am just a lowly network engineer trying to get a server running for a friend.

I have searched this forum as well as the Internets.  Most answers apply to Windows and I have tried all that I could.  I have inspected the Config.wtf file and I see locales are set to "enUS".  Unfortunately I have not had a chance to inspect the source code.  Thoughts?

Thanks in advance,
Joe

I am having the same issue now.

Compiled 3.3.5 this morning with tools

. 

I have tried 3.3.5 and  3.3.5-Graphana - Not sure of the difference here

Include Tools for the mapextractor.exe (no version in windows >properties>details, but it is 205kb)

Build Result:

========== Build: 22 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========

Start up wow client. 6.2.4.21463

Get all the way logged in to set enUS.

Exit.

run mapextractor.exe from root:

G:\Games\World of Warcraft>mapextractor.exe
Map & DBC Extractor
===================

 

No locales detected

Added Set Locale "enUS" to Config.wtf

 

No difference.

Not sure what I am doing wrong or if these tools do not work anymore on 3.3.5.

I guess I am going to try the 6x next.  Any pointers would be greatly appreciated.  Scanned through the forms for some time now and see some hits on this but no workarounds did the trick.

 

 

 

 

[Fatal error while logging in | result=( | code= (225)]

Here is what I am seeing:

My Patched 64 - 21463 should be currently supported.

My Trinity Core

TC>TrinityCore rev. d82a2cf47118 2016-04-16 19:05:32 +0100 (master branch) (Win6
4, Release) (worldserver-daemon) ready...

My bnetserver.conf

LoginREST.Port = 8081
LoginREST.ExternalAddress=10.1.1.8
LoginREST.LocalAddress=10.1.1.8

 

Any Ideas or Thoughts?

[Fatal error while logging in | result=( | code= (225)]

I read all the faq's and unable to figure this out.

I have pulled down the latest off of git | Compiled and have a working Bnet and worldserver |I have patched the client on the machine.  |created accounts via TC shell prompt| changed the config.wtf for my local lan ip (all config and setup use local lan IP not 127...  but I have tried both)

I get this in the client BattleNnet.log (windows 10)

4/16 21:00:13.262  [IBN_Login] OnRealmJoin | code= (225)
4/16 21:00:13.262  [GlueLogin] Fatal error while logging in | result=( | code= (225) | localizedMessage= | debugMessage=Error joining realm)
4/16 21:00:13.262  [IBN_Login] Front disconnecting | connectionId=1

Can anyone point me in the right direction?