Shauren

Commands are logged only for accounts with level greater than 0 - https://github.com/TrinityCore/TrinityCore/blob/6.x/src/server/game/Chat/Chat.cpp#L300

localSubnetMask controls the choice of address vs localAddress to send to connecting clients bnetserver applies that value to connecting client address (make sure to NOT connect with portal=127.0.0.1) and to localAddress, if the network matches then localAddress is sent, otherwise address In your case where you don't want to expose anything to the internet I would just set both addresses to 172.17.17.23 (then netmask doesnt even matter) You can find the complete logic here https://github.com/TrinityCore/TrinityCore/blob/6.x/src/server/shared/Realm/Realm.cpp#L21 ps. The fact that you could even see the realm list in client means LoginREST.* configs passed successfully.

works for me.

Do not use "localhost" in portal - type in the ip address directly "127.0.0.1". Since the new patch client can translate "localhost" to IPv6 representation instead, "::1" which will not work.

ERROR_HTTP_COULDNT_CONNECT indicates improper bnetserver configuration You need to configure these as well https://github.com/TrinityCore/TrinityCore/blob/6.x/src/server/bnetserver/bnetserver.conf.dist#L57 (if you PC has no local network, no router at home for example, you leave LocalAddress as it is) And yes, this is an additional port that you need to keep open, no way around that

You did not copy the required file from build dir.

An issue with connection patcher on mac is very much possible, I do not have a mac to test so all changes I do are "I hope it works"

--- Canned message start --- It appears the issue in the original post was solved, so this thread shall be closed. Should you encounter any other difficulties, please open a new thread. --- Canned message end ---

No no no no and no. The problem here is that this guy is missing a field in his account table https://github.com/TrinityCore/TrinityCore/blob/3.3.5/sql/base/auth_database.sql#L48

Incompatible? realmlist.gamebuild controls that.

FFS when will you people learn that copying the patched exe from another machine alone IS NOT ENOUGH? You need another file in wow installation folder - tc_bundle.txt

Indeed you are missing something bnetserver gained these new config settings LoginREST.Port LoginREST.ExternalAddress LoginREST.LocalAddress Needless to say, you need to configure and open this port. Fill ExternalAddress with your external IP and LocalAddress with your LAN IP

https://github.com/TrinityCore/TrinityCore/blob/3.3.5/src/server/worldserver/worldserver.conf.dist#L558 controls allowed character sets in names, check that

--- Canned message start --- It appears the issue in the original post was solved, so this thread shall be closed. Should you encounter any other difficulties, please open a new thread. --- Canned message end ---

This is the last commit working with 6.2.3.20886 https://github.com/TrinityCore/TrinityCore/commit/363731aac827f3eab051064ba466cef49f6cc111 Anything beyond that is a working-in-progress on 6.2.4 and is not usable

FYI the client does not have a command line param called "noautoupdate", you putting it there does nothing

Run the exe with the following parameters Wow_Patched.exe -uid plsnopatch -noautolaunch64bit The -uid followed by a random string is the key

My point was to simply look at what our code does instead of just taking it (in case you use a different language) - the 5 lines i linked were that "magic" block that you needed its size to get to data part

Why didn't you just do it the way TC does? https://github.com/TrinityCore/TrinityCore/blob/6.x/src/server/shared/DataStores/DB2StorageLoader.cpp#L161

There is no such thing as localization data inside db2 files - they only have strings in one locale (multilocale installations simply have multiple files) The same applies to 6.x dbc files Legacy 3.3.5 handled it differently - each string field was actually an array of 16 strings with space for locale

This sniffer is closed source, don't ask for new sniffer versions making new threads or on irc, new versions will be released when I have time. The sniffs are only available for TC developers and official contributors because they contain private data. Sniffer only works with LIVE realms and the build number stated on title/key file. How to use it: Put it on your wow directory. Start wow.exe. Start attach_sniffer. login. OR Start Wow-64.exe Use attach_sniffer_64 login. If you want to force WoW to start in 32-bit only mode use Wow.exe -noautolaunch64bit Upload your sniff compresed with zip, rar, 7z or some linux format to some non-anoying file hosting (for example zippyshare, mega, anything without captchas or wait times). Post your sniff at http://www.trinitycore.org/f/forum/13-wdbadbsniffs/ only devs will see your sniff there. Note: When updating sniffer you need to overwrite all old files. Edit by ShinDarth: In order to run the sniffer under GNU/Linux or Mac OS X you have to use the Windows client (Wow.exe) and open it using wine (get the latest version). Note: if you have the Mac OS X client already, you can just download the *.exe and *.dll files of the Windows client and add them to your Mac client folder. Instructions: - open a terminal window and run: wine Wow.exe -noautolaunch64bit Script for wine (save in the same directory as wstc) #!/bin/bash WSTC_COMMAND=$(grep -E -o 'WSTC.exe .*\.wstc' ./attach_sniffer.cmd) set -x wine $WSTC_COMMAND WSTC_7.2.5.24742_Release.zip WSTC-64_7.2.5.24742_Release.zip

--- Canned message start --- It appears the issue in the original post was solved, so this thread shall be closed. Should you encounter any other difficulties, please open a new thread. --- Canned message end ---

First. your structure of CriteriaTree has fields in wrong order - m_ID, m_criteriaID, m_amount, m_operator, m_parent, m_flags, m_description_lang, m_orderIndex This is how you get to Criteria.db2 id Take the id of CriteriaTree (16658) and find all CriteriaTree where m_parent = 16658, this gets us CriteriaTree 16659 with m_criteriaID = 12909 (repeat this until you run out of criteria trees) 12909 is your id.

The data that was before in Achievement_Criteria.dbc was moved to Criteria.db2 (and similar criterias were merged), CriteriaTree.db2 now has the data that was different for each criteria The id for achievement_criteria_data is now taken from Criteria.db2

@MHard we do not support using the connector library, only the lib shipped with MySQL server installation. Additionally LIBMYSQL_VERSION_ID define is not present in older versions of MySQL (5.5) so it cannot be used.