Event Moving Error

I have been using a pair of scripts (found here) which allow me to connect two maps together. Unfortunately, I have encountered an error caused by the script that I can't figure a way around. When I call "Transfer Player" and "Set Event Location" on one of the connected maps, I need to set the coordinates as if the two maps are one huge entity instead of separate. This doesn't seem to be affecting anything else, as doors and other events on both maps still function properly. (it becomes [26,55] instead of [26,15] in one instance) It was relatively simple to make the map larger and allow for altered coordinates, but I would still like to figure a way to fix the problem so I can avoid this in the future.

In a more complicated issue, events moved by "Set Event Location" are now being replaced by other events (from the same map) for no discernible reason. I attempt to move events 21-24, but get events 22-25 moved to those locations instead. I would like to check the script to figure this out, but I really don't know enough about Ruby to understand it. When I temporarily removed the script, all events moved properly again. I do not want to have to lose the script, and I was wondering if anyone had any clue how to fix this problem.

I attached the portion of the event code where the events are moved, in case that might be relevant.

1) Tsukihime stated the limitations of using the Connected Maps script. It may not be obvious but number 6 implies the existence of the problem you are having.

"6. Any other property that relies on separate instances of the map are also gone (parallax maps, for example)"

You already have a workaround method (ie : manually calculating the desired coordinates).

2) As for 'replace by other events' issue, I cannot seem to replicate your problem. Either :

- Try to remove other scripts except the Connected Maps & Area Maps scripts, and check if your problem is resolved (may be a script incompatibility); or

- Whip up & upload a sample of your project so that we can have a look at it.

For the first problem, I didn't consider this case, but I can offset them relative to the connected map's origin. I would also need to change the map ID if the target was on the same map.


I've updated the script to address the first problem.


The second problem I may have messed up on ID re-assignment and 21 got assigned 22, but when I tested it with two maps with one event each, they were moving the correct events around, so you'll have to reproduce it in a new project and then upload it if it still occurs.