DB/SoundWaterType: Difference between revisions

From wowdev
Jump to navigation Jump to search
Line 6: Line 6:
In the alpha, these groups are stored in a <code>LIQUIDINFO</code> struct. <code>HandleWaterAmbiences</code> controls what LIQUIDINFOs should be active and the LIQUIDINFOs themselves control what one of their three sounds plays.
In the alpha, these groups are stored in a <code>LIQUIDINFO</code> struct. <code>HandleWaterAmbiences</code> controls what LIQUIDINFOs should be active and the LIQUIDINFOs themselves control what one of their three sounds plays.


==0.5.3.3368, 1.12.1.5875==
==0.5.3.3368 - 3.3.5a.12340==
  struct SoundWaterTypeRec {
  struct SoundWaterTypeRec {
   uint32_t m_ID;
   uint32_t m_ID;
Line 13: Line 13:
   {{Template:Type/foreign_key|table=SoundEntries}} m_SoundID;
   {{Template:Type/foreign_key|table=SoundEntries}} m_SoundID;
  };
  };
==Structure==
==Structure==
  '''Column Field Type Notes'''  
  '''Column Field Type Notes'''  

Revision as of 23:15, 3 October 2017

PreVanilla … Wrath

The client expects this DBC to have groups of 3 records grouped by m_soundType. Each group will have one record of each of the valid m_soundSubtype values.

This section only applies to versions ≤ PreVanilla (0.5.3.3368).

In the alpha, these groups are stored in a LIQUIDINFO struct. HandleWaterAmbiences controls what LIQUIDINFOs should be active and the LIQUIDINFOs themselves control what one of their three sounds plays.

0.5.3.3368 - 3.3.5a.12340

struct SoundWaterTypeRec {
  uint32_t m_ID;
  uint32_t m_soundType;    // grouping key
  uint32_t m_soundSubtype; // valid values are 0, 4 or 8. client reads as (m_soundSubtype >> 2) & 3
  foreign_key<uint32_t, &SoundEntriesRec::m_ID> m_SoundID;
};

Structure

Column	Field 			Type 		Notes 
1 	ID 			Integer 	
2 	SoundType 		Integer 	Key for grouping records together
3 	SoundSubtype 		Integer 	Valid values are 0, 4, 8. Exactly one of each must be used in each group
4 	iRefID_SoundEntries 	Integer