Skip to content

Rethink the way to manage sound design configs #687

@AerunDev

Description

@AerunDev

As a Developer
I would like to rethink the way sound design config is managed
So that I can simplify the code both Studio & PSDK sides

Context

During the implementation of the PSDK binding of Sound Design config, we had some ideas about how to simplify and improve the way to manage each sound effect.
For now, sounds are stored this way:

{
  "backgroundSound": {
    "cancel": {
      "name": "path/to/file",
      "volume": 40,
      "pitch": 100
    },
    ...
  }
}

It could be cool to improve the structure to get this one:

{
  "sounds": [
    {
      "dbSymbol": "cancel",
      "path": "path/to/file",
      "type": "bgs",
      "volume": 40,
      "pitch": 100
    }
  ]
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    Technical storyIssues related to technical work

    Type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions