i ve had mix results with components files / sometimes it does the "cannot save" bug (or maybe i'm the bug :D causing impossibility to save into components or back into map format)
the function is a "save as" function (file/save file save as .. there it allows you to choose / choose save as components)
the idea is straightforward, maps are a file or a folder, this function allows you to view the map as a sum of all its parts (your imported assets notably) a folder with all the files that makes it (game data / trigger data / etc / all of it)
This folder in which you can then "manually" add stuff or change it (like importing data (copy pasting it) or adding files etc)
.. in this form, your map can be opened but not published (didn't try recently but i doubt that has changed)
once you have done what u need, you re save as
instead of as components / save as map
and if it works .. bob's your uncle (done all good)
...
So for merging files you would/could make your two maps as components and mess with whatever you want to mess with (taking trigger data from one trigger file unto the other for instance) IN the folders/opening those files (again as raw "code" files) or "simply" exchanging one game data file for another (that s prone to bugs of course)
Then you would re save as a map and the change will work or not (sorry to add that this method is kind of risky, do make backups etc (just in case) .. since you could be stating contradictory code with this method (through not knowing all the "linked" stuff you are "messing with".. the probability of error is quite potent)
...
i've never really successfully used the "merge" function, but again! just make back ups and try it
the function seems "clear enough" .. again i tried and never got it to work (but that was several years ago)
To be clear, the "component's method is standard .. why everyone is advising you to try/do it
tldr
i ve had mix results with components files / sometimes it does the "cannot save" bug (or maybe i'm the bug :D causing impossibility to save into components or back into map format)
the function is a "save as" function (file/save file save as .. there it allows you to choose / choose save as components)
the idea is straightforward, maps are a file or a folder, this function allows you to view the map as a sum of all its parts (your imported assets notably) a folder with all the files that makes it (game data / trigger data / etc / all of it)
This folder in which you can then "manually" add stuff or change it (like importing data (copy pasting it) or adding files etc)
.. in this form, your map can be opened but not published (didn't try recently but i doubt that has changed)
once you have done what u need, you re save as
instead of as components / save as map
and if it works .. bob's your uncle (done all good)
...
So for merging files you would/could make your two maps as components and mess with whatever you want to mess with (taking trigger data from one trigger file unto the other for instance) IN the folders/opening those files (again as raw "code" files) or "simply" exchanging one game data file for another (that s prone to bugs of course)
Then you would re save as a map and the change will work or not (sorry to add that this method is kind of risky, do make backups etc (just in case) .. since you could be stating contradictory code with this method (through not knowing all the "linked" stuff you are "messing with".. the probability of error is quite potent)
...
i've never really successfully used the "merge" function, but again! just make back ups and try it
the function seems "clear enough" .. again i tried and never got it to work (but that was several years ago)
To be clear, the "component's method is standard .. why everyone is advising you to try/do it
gl
hf
tldr