Skip to content

Changes to modules/effects don't persist across a load or revert #115

Description

@JonnyOThan

Sometimes this is nice, to revert your in-progress changes. But other times it's likely to lose work. We could keep a database of updated cfgs that persists across scenes and loads. Needs some explicit designs around workflows.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions