diff options
| -rw-r--r-- | Add-a-new-map-and-landmark.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Add-a-new-map-and-landmark.md b/Add-a-new-map-and-landmark.md index b2b8a95..966da9f 100644 --- a/Add-a-new-map-and-landmark.md +++ b/Add-a-new-map-and-landmark.md @@ -314,8 +314,8 @@ The **connections** value is a combination of `NORTH`, `SOUTH`, `WEST`, or `EAST The `connection` macro takes six arguments: the direction, map name, map ID, X/Y offset, distance offset, and strip length. Again, the direction, map name, and map ID are just for identification, but the other three values are more complicated. -- **X/Y offset:** How many blocks to shift a connection perpendicular to its direction. A north or south connection gets shifted right/east, a west or east connection gets shifted down/south. -- **X/Y offset of block data to load:** The block data from this offset in the target map is loaded to the X/Y offset of the source map. Same rules as the previous argument apply. +- **X/Y target offset:** How many blocks to shift a connection perpendicular to its direction. A north or south connection gets shifted right/east, a west or east connection gets shifted down/south. +- **X/Y source offset:** The block data from this offset in the target map is loaded to the X/Y offset of the source map. Same rules as the previous argument apply. - **strip length:** How many blocks wide the connection is. Anyway, I can't fully explain how to determine the right values here; try looking at how other maps connect and base your own connections on them. In this case, we made `GLOBAL_TERMINAL_OUTSIDE` the same height as `GOLDENROD_CITY`, 18 blocks, and they'll line up perfectly side by side without any Y offset, so the connection values are easy to set. |