gameboy9 / DW4RandoHacker

Dragon Warrior 4 RandoHacker
GNU General Public License v3.0
18 stars 5 forks source link

Chapter 4 teleport bug #70

Closed Tundra83 closed 5 years ago

Tundra83 commented 5 years ago

Made a youtube video showing what it is doing instead of trying to explain it. https://www.youtube.com/watch?v=KdJHdfJkTEk&feature=youtu.be

Tundra83 commented 5 years ago

I was using no codes or anything. Just the randomly generated game file.

Sent from my Samsung Galaxy smartphone.

-------- Original message -------- From: Dan Weiss notifications@github.com Date: 2019-05-29 8:55 p.m. (GMT-07:00) To: gameboy9/DW4RandoHacker DW4RandoHacker@noreply.github.com Cc: Tundra83 josepharussell@hotmail.com, Author author@noreply.github.com Subject: Re: [gameboy9/DW4RandoHacker] Chapter 4 teleport bug (#70)

Just to be sure, you aren't using the debug mode game genie code? It changes the first return destination to Keeleon.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/gameboy9/DW4RandoHacker/issues/70?email_source=notifications&email_token=AMGHRHUYXR72LONEGZLK2ADPX463JA5CNFSM4HQJGLXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWRGRJA#issuecomment-497182884, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMGHRHROJZONOQXWAF2ZK33PX463JANCNFSM4HQJGLXA.

Dwedit commented 5 years ago

Just saw it happen here:

https://clips.twitch.tv/SquareFineGaurKlappa

This was in chapter 5, not 4.

Polantaris commented 5 years ago

I think this is related to what I mention in this post here:

https://github.com/gameboy9/DW4RandoHacker/issues/69#issuecomment-498049326

If that's the spot where the Treasure Map is marked it seems to warp you to Keeleon after a large delay (potentially as a fallback result).

Honestly I don't even remember what's supposed to be there in the main game.

xJackieBx commented 5 years ago

the mark on the map is where the world tree (zenithian sword) is located in vanilla

gameboy9 commented 5 years ago

Should be resolved in the next release!