With this PR, we should be able to use our own objects (eg: Player, Items, etc), import collisions from LDtk, and import entity fields as metadata. Also fixed a few issues I found while using this plugin.
Makes it possible to import correctly the large map sample with their correct coordinates (both for the levels and for the entities).
Fixed one error for using a null entity when it was not properly configured on LDtk.
Added the possibility to load existing resources using the path to it instead of the supported NodeTypes.
Added the option to import collisions (added to the README) by having a "Collisions" layer, and it creates a StaticBody2D with one object per tile that needs collision (whatever was added in that layer). It's way faster than adding collision on each tileset for some reason. Also it would be nice to optimize this later by simplifying the geometry (aka use less collision nodes), we can do that if we also consider the Y axis, but the logic is a bit more complicated for that.
Use the correct rendering order from LDtk.
Add entity fields to the node property (it it exists) or as metadata.
levigilbert
commented
3 years ago
With this PR, we should be able to use our own objects (eg: Player, Items, etc), import collisions from LDtk, and import entity fields as metadata. Also fixed a few issues I found while using this plugin.