rednode API - v0.50.0
    Preparing search index...

    Interface TraceBatch

    What audio.trace hands over each time.

    interface TraceBatch {
        dropped: number;
        loads: { found: boolean; ms: number; sound: number }[];
        posts: {
            event: number;
            ms: number;
            name?: string;
            object: string;
            playing: number;
            recordings?: number;
        }[];
    }
    Index
    dropped: number

    Records lost since the last batch because too many came at once.

    loads: { found: boolean; ms: number; sound: number }[]

    Sounds the game loaded: ms, the sound id, and whether the index had it.

    posts: {
        event: number;
        ms: number;
        name?: string;
        object: string;
        playing: number;
        recordings?: number;
    }[]

    Events the game posted to Wwise: ms since the trace started, the event's Wwise id (FNV-1 of its lower-case name), its name when REDnode knows it, the Wwise game object it was posted on (a 64-bit number, as a string), and the playing id Wwise gave it (0: the post failed).

    Names come from REDbridge's list of events (WolvenKit's, from game 1.6), which the host loads when a trace starts; your package needs no permission for them. Events newer than the list, or traced before the list has loaded, have no name. A Wwise game object is not an entity id (Sound Tools SP1).

    recordings counts the event's recordings in the game's sound index, which audio.playGame plays with { event }: 0 for a stop event, or one whose sound lives in a Wwise bank.