There’s a few different things being discussed in this thread, so to add some clarity here:
- Tilemap Support: There is an effort to add this to GD5 undergoing right now. It is currently being worked on by Blurymind. You can follow along here: Support for Tilemaps objects (tilesets and Tiled files) · Issue #503 · 4ian/GDevelop · GitHub
- Tilemap Editor: As of right now, there is an eventual goal to be able to edit tilemaps within GDevelop. This is not planned to even be looked at until base support is implemented.
- Tiled Map Editor: This is an external tool that can be used to build Tilemaps and Tilesets (TMX and TSX files). These file formats will be used for the above mentioned Tilemap support. You can also use Tiled to make a map and then export it as an image to be imported into GDevelop.
- Tiled Sprite Objects: This exists in the engine right now, but is meant to be a single tile that repeats as you resize it, rather than stretching like normal Sprites do. It is not intended to replace a Tilemap.
For right now, knowing that TMX/TSX files will be supported in the future, I recommend using Tiled Map Editor to make your maps, export the maps as images, but save the originals. When you import the images into GDevelop (as Sprites), you can then make a simple red/blue/etc block object with the “platform” behavior and place it around your map to allow for collisions. Then at the start of your scene, hide the collision objects.
Make sure you keep your TSX/TMX files once Tilemap support is implemented, too.
Hope the above helps.