Jump to content
TrinityCore
Ulduar

Hotfix_blob table

Recommended Posts

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.

image.png

Share this post


Link to post
Share on other sites

This table exists only to send sniffed hotfixes for db2 files that are not loaded by TC. You should never try to manually insert data into it.

If you really must know - blob is simply the entire db2 row written as binary

  • Thanks 2

Share this post


Link to post
Share on other sites
5 hours ago, Shauren said:

This table exists only to send sniffed hotfixes for db2 files that are not loaded by TC. You should never try to manually insert data into it.

 

Thanks, Shauren. i know that.

 

5 hours ago, Shauren said:

If you really must know - blob is simply the entire db2 row written as binary

Maybe Casc can show binary values. I already understood, that can fix only existing data.
I was not going to insert custom data.

 
 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By ghostdub
      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).
×
×
  • Create New...