@Rhuan I've been testing that code. It sort of functions. See attached image.

This is perplexing me. The map slide functions once in any given direction. I've been at this for over an hour. I just don't understand why it responds differently on a second processing of the code.

Edit: replaced example with more detailed example.

Put the map sliding function into inEdit.js for later recoding. Been getting the levels arranged in their proper locations on the Overworld map. Refined Setzer's level... *Note: Secret passageways not included on map.

Out of boredom I made a fanart mockup esque type dealy of the ship casino room in a more Zelda 1 form. I like spriting so it's fun to do once in a while.

This is perplexing me. The map slide functions once in any given direction. I've been at this for over an hour. I just don't understand why it responds differently on a second processing of the code.

Edit: replaced example with more detailed example.

Without seeing the code you've actually used I can't tell you what the issue is but at a quick guess it looks like the relevant x/y variables are being set incorrectly when the function is first called.

Out of boredom I made a fanart mockup esque type dealy of the ship casino room in a more Zelda 1 form. I like spriting so it's fun to do once in a while.

Not too bad. However, I am using the actual "Blackjack" as depicted below.

Not too bad. However, I am using the actual "Blackjack" as depicted below.

I did it simply to ease my brain. Seeing NES Link in FF6 graphics did the brain a hurt.

This is perplexing me. The map slide functions once in any given direction. I've been at this for over an hour. I just don't understand why it responds differently on a second processing of the code.

Edit: replaced example with more detailed example.

Without seeing the code you've actually used I can't tell you what the issue is but at a quick guess it looks like the relevant x/y variables are being set incorrectly when the function is first called.

Even your initial code responded that way. Would function once then not process the same way again.
All I did was copy the sliding map function into my inEdit.js, corrected a typo, and added the SetRenderScript to the end of one of my map exit functions. Perhaps, something with the map exit is causing the sliding map to respond that way but I don't think it should be affecting it. I'll post a code snippet shortly for you to look at.

My initial one was a use once example - the x and y values need to be set differently depending which way you're sliding and the termination check needs to be different to.

Not too bad. However, I am using the actual "Blackjack" as depicted below.

I did it simply to ease my brain. Seeing NES Link in FF6 graphics did the brain a hurt.

What about seeing Setzer's Airship flying over hyrule? 

In part of the story Link finds a journal in an outpost depicting Setzer's arrival in Hyrule which I have been developing a "cutscene" for. Basically, Link finds the journal, screen fades to black, re-enters on the southern portion of Hyrule where the airship come in from off the screen. Flies over the outpost and heads west, while flying over the desert region a Gleeok (2 headed version) launches multiple fireballs at the airship where it is hit and crash lands in the desert.

My initial one was a use once example - the x and y values need to be set differently depending which way you're sliding and the termination check needs to be different to.

I did do some variations to it before saying "arrrrrrgh, I'll try coding this again later." Such as adding in a switch (dir) & then coding the cases accordingly. In every attempt (minimum 2 hours before coding something else) it went wonky. The video showed the results of my attempts. I got frustrated after a few hours. It's on my task list of things to do.

What about seeing Setzer's Airship flying over hyrule? 

In part of the story Link finds a journal in an outpost depicting Setzer's arrival in Hyrule which I have been developing a "cutscene" for. Basically, Link finds the journal, screen fades to black, re-enters on the southern portion of Hyrule where the airship come in from off the screen. Flies over the outpost and heads west, while flying over the desert region a Gleeok (2 headed version) launches multiple fireballs at the airship where it is hit and crash lands in the desert.

Actually I never found that one to be bothersome. It's a simple enough image that I never thought twice. Though I did react to the Enterprise better simply because of a less complicated colour scheme haha. I'm not judging, I like the story behind all this. I was just bored, on my lunch break, and wanted to see what I could come up to see if I could appease my pixel-ego.

My initial one was a use once example - the x and y values need to be set differently depending which way you're sliding and the termination check needs to be different to.

I did do some variations to it before saying "arrrrrrgh, I'll try coding this again later." Such as adding in a switch (dir) & then coding the cases accordingly. In every attempt (minimum 2 hours before coding something else) it went wonky. The video showed the results of my attempts. I got frustrated after a few hours. It's on my task list of things to do.

To do it right you'd need a switch, probably 2 in fact.

Come to think of it Radnen's sliding map transition got bugged in some recent miniSphere version and I haven't looked into what caused that regression yet...

@Rhuan Keep in mind that this is from like 2+ hours of going blind staring at the screen..