Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LDtk 1.0 checklist #68

Closed
7 of 12 tasks
Trouv opened this issue Apr 2, 2022 · 2 comments · Fixed by #75
Closed
7 of 12 tasks

LDtk 1.0 checklist #68

Trouv opened this issue Apr 2, 2022 · 2 comments · Fixed by #75
Labels
enhancement New feature or request

Comments

@Trouv
Copy link
Owner

Trouv commented Apr 2, 2022

The ldtk-1.0 branch is being developed to support the first major release of LDtk. This issue is intended to track new features that may need support, bugs that need fixing, design considerations, etc:

Required:

  • LDtk 1.0 files load
  • ldtk types updated
  • new field instances (entity refs, tiles) supported
  • decent solution for using entity refs to create relational components spun off into its own issue "relations" feature #70
  • examples/sample files updated
  • Use iids instead of uids wherever applicable
  • multi-worlds doesn't break plugin

Bonus points:

  • Support for entity instances using field instance tiles for display
  • more comprehensive multi-worlds support
  • parallax layers support (not sure how this would even factor into the api, so maybe best to leave to the user)
  • nine-slice entity display
  • hot reloading for external levels (seems like it'll work now) Hot reloading for external levels #1 It won't really work after all, though you can save twice as a workaround
@Trouv Trouv added this to the bevy_ecs_ldtk 0.3.0 milestone Apr 2, 2022
@Trouv Trouv added the enhancement New feature or request label Apr 2, 2022
@droog126
Copy link

droog126 commented Apr 4, 2022

wait for you

@Trouv
Copy link
Owner Author

Trouv commented Apr 7, 2022

It's not all done yet but it's basically working on the ldtk-1.0 branch now if you want to change your Cargo.toml to use it. I'm not gonna cut a new release with 1.0 support until bevy 0.7 and bevy_ecs_tilemap 0.6 come out since that's right around the corner, theoretically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants