Skip to content

describe data design #1

Description

@meshula
  • what does a game look like?
  • what does a level look like?
  • how are assets referenced?
  • what is the role of payloads?
  • what is the role of variant sets?
  • how are LODs represented?
  • how is physics described?
  • how are triggers described?
  • etc.

Individual issues should be created for each and referenced here as the organizing topic.

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