[Other Question] How to release a map-only updated patch?

[warsawgecko]

I couldn't find if this was asked before, forgive me.

But I'm curious which files are related to the maps so that I could compress only those files, allowing downloaders to basically drag and drop without having to re-download a 300MB file?

I had copied a map to make its Dive version but there are some transparent tiles that I didn't see, which are preventing movement. So I'd like to release just the map update if possible?

 

[Vendily]

Well, all you need to do is zip up the MapXXX.rxdatas related to the maps that changed.
XXX being the map ids of the changed maps.
(I usually zip up the whole data folder though)

 

[warsawgecko]

Well, all you need to do is zip up the MapXXX.rxdatas related to the maps that changed.
XXX being the map ids of the changed maps.
(I usually zip up the whole data folder though)

Thank you very much, and for the guide to common errors! That will help me greatly in the future.

Additionally, with moving these files will it also include the events on them? Specifically, warp events.

 

[Vendily]

Thank you very much, and for the guide to common errors! That will help me greatly in the future.

Additionally, with moving these files will it also include the events on them? Specifically, warp events.

Yep! All these MapXXX files are self contained with all the data involving them within!
You may have seen scripts distributing map files before, mostly so you can see the events within.
It's very convenient for really complicated stuff.

You may need to repoint map warps if the map ids they used to point to changed, but in this case, you should be fine, since you are taking it out of your project to put it in the same project.

As for the common errors guide, it was made for v17.2, so its probable that the exact error messages and line numbers have changed at this point.

 

[warsawgecko]

Yep! All these MapXXX files are self contained with all the data involving them within!
You may have seen scripts distributing map files before, mostly so you can see the events within.
It's very convenient for really complicated stuff.

You may need to repoint map warps if the map ids they used to point to changed, but in this case, you should be fine, since you are taking it out of your project to put it in the same project.

As for the common errors guide, it was made for v17.2, so its probable that the exact error messages and line numbers have changed at this point.

So I edited the map and fixed the error and released it as a small patch but the person experiencing the issue still can't exit the house.

I double-checked and it is a touch-based event that is connecting to the intended destination.