DB/SoundWaterType: Difference between revisions
Jump to navigation
Jump to search
Barncastle (talk | contribs) |
Barncastle (talk | contribs) mNo edit summary |
||
Line 1: | Line 1: | ||
{{Template:Sandbox/VersionRange|min_expansionlevel=0|max_expansionlevel=3}} | {{Template:Sandbox/VersionRange|min_expansionlevel=0|max_expansionlevel=3}} | ||
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. | The client expects this DBC to have groups of 3 records grouped by m_soundType. Each group will have exactly one record of each of the valid m_soundSubtype values. | ||
{{Template:SectionBox/VersionRange|max_expansionlevel=0|max_build=0.5.3.3368}} | {{Template:SectionBox/VersionRange|max_expansionlevel=0|max_build=0.5.3.3368}} |
Latest revision as of 23:15, 3 October 2017
The client expects this DBC to have groups of 3 records grouped by m_soundType. Each group will have exactly one record of each of the valid m_soundSubtype values.
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