Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(2 edits) (+2)

I've always enjoyed using LDTK. I even used it in my last game Katkoot and I'm using it for my current project. It perfectly filled the gap of not having a level editor while working with LÖVE with ease, unlike Tiled which was not so user-friendly.

However, I feel like it misses some tiny features that would make my workflow (and so many others) much easier. Here is a list of the little improvement I would love to see in future versions:

1) Being able to set Coords manually was a big improvement in my opinion, but I think you can push even further by making it that we can move the entities by pixels using arrow keys on keyboard. That would make it much faster to adjust and tweak the position without the need to click on anything. It would be even nicer if you allow us to change the values by simply scrolling with the mouse wheel inside input boxes that can one hold numbers. 

2) Instead of representing entities using a rectangle or an icon set, I would love to be able to select an individual image file from my project that isn't a part of any tileset. So, I will be able to create an entity, then select an image from my computer that isn't necessarily used in LDtk or in any of my defined tileset, and use that to represent my entity in the editor.

3)  I like the idea of custom commands. However, you can't do much with it in its current state. I would love to be able to insert some values to use as arguments in the defined function. I'm talking about something like how you set the "Default level identifiers". So, I should be able to call commands like "run game --ldtk [LEVEL_INDEX]". Also being able to have multiple custom defined shortcuts for multiple commands would be a nice addition, though not necessarily that useful.

4) Move editor/project settings outside the .ldtk or .json to make it shorter. You can have an additional file for those. You can make it optional to keep it or not in the main file.

(+2)

Thanks for the feedback! The best way to submit suggestions is using GitHub issues here: https://github.com/deepnight/ldtk/issues

About these points:

  1. this should be fixed at one point, when I’ll complete this issue (because it’s somehow related internally): https://github.com/deepnight/ldtk/issues/768

  2. this could totally be done, feel free to submit an issue about this one :)

  3. current custom commands were quickly (and poorly) implemented: it should be reworked for next update, including adding variable arguments.

  4. For now, there’s no plan about moving these settings to another file, as this could break all existing importers easily. Unless the change is really needed, I tend to be very careful about implemented JSON parsing breakers. In this case, I don’t think the benefit would be relevant (we’re talking about removing a few kilobytes at most)

(+1)

Thanks for the reply! I'm glad to hear that you are already working on those features already.
As for point 2, I've submitted an issue here https://github.com/deepnight/ldtk/issues/842 .

I'm looking forward for an update when ready <3