Skip to content

Organisation #1

Description

@IntelOrca

They way we are planning on doing content for OpenRCT2 is to store music in the same way as rides and scenery. So each music track will be a custom object that is referenced by a park. This means that any custom music created (different songs from the original game) will be like custom rides and just hosted as independent entries on the online content database.

Therefore I think that it should be organised as follows:

  • OpenMusic - this repository - contains only the original game music remastered.
  • CustomMusic (any name you like, different repository) - your new music

You can then have a CI to render the music tracks and bundle them into our object format (yet to be designed) and uploaded to the content server (yet to exist).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions