Kudos for relative file references!


Maybe this was an obvious choice, but a BIG KUDO for electing to make all of the Tileset file references in the .tmx files as RELATIVE refs! It might have been easy/tempting to make them absolute refs, which would lock them to the individual’s PC file structure. Instead, once the Tiled .tmx is loaded, the relative refs can go find the Tileset (and other) graphic files with ease (assuming of course they are in their relative place).

Why is this a big deal for me? I am working with a team on a WWII game, and we are using Tiled to produce maps. We elected to put the Tiled files all out on a shared GoogleDrive to facilitate teamwork. And because the internal refs are all relative to the main .tmx… once ANY of us navigates to and loads that .tmx, all of the rest of the support files (graphics, etc.) get picked up automatically via those relative refs on GDrive. Ergo: Very easy to work as a team!

So, a kudo for that choice! :slight_smile:

(Thorbjørn Lindeijer) #2

I’m glad to hear working with a team with Tiled is working out well for you! It was indeed an obvious choice, since using absolute paths would have caused so much trouble. :slight_smile:

Of course, even relative paths can end up pointing to the wrong location. In Tiled 0.15, one of the most important improvements I made was that any file reference can be fixed up when opening the map. Before that version, the map would fail to open and the only way to fix it was to open the map file in a text editor in order to correct the paths.

Btw, are the files also kept in a version control? I think Google Drive is a great tool for collaboration, but it’s probably not a good way to keep track of changes and backing up old states.