Currently, we use devices such as file input to introduce external files, which work by setting file path. When users are only working locally, there is no problem with this. But when we expect to share .tmd, we have to package and publish external files together, and this sometimes brings path redirection issues.
Especially when we attempt to share a macro (or a locked one) that references an external file, as publisher, I have to share multiple files simultaneously; as user, I am unable to know/configure the file address inside the macro to point to the correct location.
Therefore, I request a feature that allows external files to be packaged into tmd/dev as part of the project. A common/possible implementation is to add a checkbox for the file input device, where when checked, external files will be packaged as part of the project file when saved.
4 Likes
This is definitely something I’d like to add.
In general, I think it would be really useful to have an companion data file that can contain various useful things, from external assets, cache files for things like the Tiled File Input device, saved build results, and so on. During editing, that data needs to be stored in a companion file instead of the TMD, but you could then “Package” a world so that all of its various external inputs are included.
I had not thought of including a “packaging mode” for Macros, but you’re right - that would be quite useful.
2 Likes