You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scenario:
I have made 4 ldtk projects, they corresponding to 4 world/land/level in my game.
I made one of them first, and difined lots of entities.
Then I copy it to 4, and change what I need.
with project growing,
I need add more entity types now,
and I may add more worlds/land/level in my game,
I have to add new entities to each project manually and keep them sync with each other.
Proposal:
External Enum is easy to define with a text, so it's feasible to implement an "External Enums" feature.
But how about an "External Entities" feature?
What I could think is to allow a project indicate another project as "entity template reference". it will forbid current project create any entity definition, and use/update those from "entity template reference" directly.
I'm not sure about the implementation details, any more feasible idea to reuse entities between projects?
The text was updated successfully, but these errors were encountered:
It seems more related to the upcoming multi-worlds update (see #231).
The idea, in short, is to allow having multiple worlds in a single LDtk, each one having its own levels and layout.
Scenario:
I have made 4 ldtk projects, they corresponding to 4 world/land/level in my game.
I made one of them first, and difined lots of entities.
Then I copy it to 4, and change what I need.
with project growing,
I need add more entity types now,
and I may add more worlds/land/level in my game,
I have to add new entities to each project manually and keep them sync with each other.
Proposal:
External Enum is easy to define with a text, so it's feasible to implement an "External Enums" feature.
But how about an "External Entities" feature?
What I could think is to allow a project indicate another project as "entity template reference". it will forbid current project create any entity definition, and use/update those from "entity template reference" directly.
I'm not sure about the implementation details, any more feasible idea to reuse entities between projects?
The text was updated successfully, but these errors were encountered: