Jump to content
TrinityCore

Understanding the Hotfixes table


ghostdub
 Share

Recommended Posts

Hello, everyone!

I'm trying to understand how the Hotfixes database works, in particular the item_sparse_locales table. I couldn't find enough documentation to properly understand how it all works.

As far as I understand it, this table is a good way of altering a certain item's name/description without updating the db2 files in the client.

What I don't understand is some of its fields and how to fill them to get it to work:
• Locale: I know it's supposed to be filled with 4 chars but I'm not quite sure what the format should be or if it's case sensitive: enUS, enus, ENus or ENUS?
• Name2_lang, name3_lang, Name4_lang: Why are there 3 "name" fields aside from the numberless one? What's their purpose?
• VerifiedBuild: What value should I insert here? Any positive value works?

There's also the matter of the hotfix_data table (this is all the documentation I could find about it: https://trinitycore.atlassian.net/wiki/display/tc/hotfix_data ), I couldn't quite figure out how to get it to work with the item_sparse_locale table or even if it's necessary. There're some entries in the regular item_sparse table that don't seem to be reflected in the hotfix_data but they're still picked up by the client regardless.

Thanks in advance,
Dub.

EDIT: I'm also looking for the function in the Core that handles sending item names/descriptions to the client, if the previous stuff doesn't work out! I'm trying to get certain items to load their names and descriptions from a MySQL table (custom or already available).

Edited by ghostdub
Link to comment
Share on other sites

I'm guessing VerifiedBuild might either represent the expansion pack where the data was first introduced. Just an initial thought though. It could be useful for conditional statements in the core, especially if an npc should or should not behave a certain way, or it's a way of saying that the data is set in stone. I'm guessing the latter if the verifiedbuild matches any of the builds for the wow clients.

Link to comment
Share on other sites

VerifiedBuild is not used by the core, at all. Its purpose is to annotate the build where the data was introduced to our DBs (except for custom stuff, all the data in the hotfix DB is from sniffs).

I'll let someone else answer the questions regarding the hotfix DB.

Link to comment
Share on other sites

  • 1 month later...

Hard for "me" to explain. But I have a slight understanding. Just read whatever is under the hotfixes DB in the wiki and I am sure that you will get an idea of what it is for. Example: You have an item which is plate, you can set it to leather if you want and also to what slot it should be along with other stuff such as flags etc.. Correct me if I'm wrong.(Just my understanding so far, might or probably will be wrong=D). Also interested in knowing the full use of this table.

Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Frik24
      Hello TrinityCore members,

      I wanted to mess around with 6.2.4a build 21742,
      I've downloaded/compiled the trinitycore TrinityCore-6.2.4-21742 from github

      I've got connection_patcher.exe among other files in my release build

      I've got client with same patch TrinityCore-6.2.4-21742

      I patched the client(all successful) with patcher i've got from compiling source.

      When i run WoW_Patched.exe i get error message https://imgur.com/a/ZZQI3J9
       
      can anyone help me i'd appreciate it a lot!
    • By Ulduar
      Hey everyone. Sorry for questions.
      Hotfix_blob table - how does this table work?
      TableHash - not questions, understandably. Taken from db2 hash in WoW Packet Parser. RecordId - not questions, understandably. Taken id from approapriate db client files. blob - need understand, how customer keys are generated. Not just only from sniff. Thanks advance.

    • By darki73
      So i guess it is pretty obvious about what am i going to ask =)
      Problem is, previousle we could just sha1 username and password separated by colon and here is the sha_pass_hash.
      The problem i am facing right now, is that according to https://github.com/TrinityCore/TrinityCore/blob/86b98686a95e23247ecb774fb23ecd5b8d94b97b/src/server/game/Accounts/BattlenetAccountMgr.cpp#L177 Trinity now uses SHA256, so the hashes do not match anymore. The thing is, password length in database is 40 symbols (exactly as many as in sha1 hash), but sha256 hash length is 64 characters long. I am confused...
      I've tried to recreate whole "Cryptography" thing on PHP but, guess what, failed.
      Can somebody explain me how the password is generated nowadays?
      Thank you for your attention. 
    • By HolyNitzan
      Hey Guys,
      I'm  using the last build of TrinityCore for WoD, currently using latest TDB release, I noticed that there are no spawns in Draenor, I would like to konw how could I solve it? is the TDB not populated with Draenor mobs/npc spawns?
    • By Shinzon
      I have searched all over the forums and can't find anything that exactly matches this. 
      I can connect fine to the server using my windows client, but when I try to connect using my mac client it immediately bounces back stating "You have been disconnected from the server". 
      I have the correct IP address in the config.wtf (And realmlist in the DB) but still can't connect. 
      I of course can't apply the connection patcher, because the EXE isn't mac compatible. 
      Is there something else I need to do to connect with mac?
      Here is my connection.log if it helps (NOTE that the ".logon.battle.net" I can't get rid of... there is no where config.wtf that has that).
       
      3/14 13:10:21.966  Login program=WoW platform=Mc64 locale=enUS 3/14 13:10:22.097  Component WoW.Mc64.20886 3/14 13:10:22.097  Component WoW.base.20726 3/14 13:10:22.099  Battle.net is Component Bnet.Mc64.37165 3/14 13:10:22.099  LOGIN: state: LOGIN_STATE_CONNECTING result: LOGIN_OK  3/14 13:10:22.145  Failed to resolve “108.26.241.19”.logon.battle.net 3/14 13:10:22.145  LOGIN: state: LOGIN_STATE_FAILED result: DISCONNECTED  3/14 13:10:22.145  Login program=WoW platform=Mc64 locale=enUS 3/14 13:10:22.145  Component WoW.Mc64.20886 3/14 13:10:22.145  Component WoW.base.20726 3/14 13:10:22.154  Battle.net is Component Bnet.Mc64.37165 3/14 13:10:23.298  Client Disconnect due to reason:8 3/14 13:12:54.053  LOGIN: state: LOGIN_STATE_CONNECTING result: LOGIN_OK  3/14 13:12:54.073  Failed to resolve “192.168.1.130”.logon.battle.net 3/14 13:12:54.151  LOGIN: state: LOGIN_STATE_FAILED result: DISCONNECTED  3/14 13:12:54.151  Login program=WoW platform=Mc64 locale=enUS 3/14 13:12:54.173  Component WoW.Mc64.20886 3/14 13:12:54.173  Component WoW.base.20726 3/14 13:12:54.308  Battle.net is Component Bnet.Mc64.37165 3/14 13:12:54.309  Client Disconnect due to reason:8  
       
       
×
×
  • Create New...