Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit)

The end of dungeon bug happened to me twice. First at the end of the 2nd dungeon, Bottle Grotto, and then again at the end of the 5th dungeon, Catfish's Maw. Both times, closing and relaunching the game allowed me to progress.

Other bugs I've found:

-Interacting with the Face Shrine keyhole opened the door even though I didn't have the Face Key yet. I only have one save file, so I haven't been able to test if this will happen in every playthrough, but I had just been told by the owl that there were two shrines I should check out, one to the south and one to the north. The one to the south is where you get the Face Key, but I went to the north first instead, and was able to open the Face Shrine and enter without first getting the key.

-The Armos Knight in the ancient ruins south of the Face Shrine (where you get the Face Key) can only be damaged by charging into him with the Pegasus Boots. In the original game, he could be damaged with the bow, or with a charged spin attack.

-I found myself unable to leave a cave once (Link was just pushing against the opening as if it was a wall). This was in the cave at C-2 (the right entrance) after I'd jumped off of the ledge inside (the one with the green skull). After a few moments, Link disappeared and reappeared on the ledge, and I walked down the stairs and was able to leave the cave. I haven't been able to reproduce this.

-My game crashed once while leaving the cave at L-9 (I think? I'm not 100% sure which cave it was, but it might also have been the fairy fountain at I-8... I wish I'd written it down as soon as it happened). When the crash happened, it displayed this message:

Index was outside the bounds of the array. at System.Collections.Generic.Dictionary'2.TryInsert(TKEY key, TValue value, InsertionBehavior behavior) at ProjectZ.InGame.SaveLoad,SaveManager.SetString(String key, String value) at ProjectZ.InGame.GameObjects.NPCs.ObjMarin.StartSinging() at ProjectZ.InGame.GameObjects.NPCs.ObjMarin.Activate() at ProjectZ.InGame.GameObjects.NPCs.ObjMarin.Init() at ProjectZ.InGame.GameObjects.NPCs.ObjMarin.Init() at ProjectZ.InGame.Map.ObjectManager.LoadObjects() at ProjectZ.InGame.GameSystems.MapTransitionSystem.ThreadLoading(String mapFileName)

EDIT: I've reached Eagle Tower, and I have a few more bugs to report.

-I was able to lift up the skeletal remains of the flying rooster in the cave below the rooster statue without playing the song to revive him. I found myself holding the flying rooster, like normal. But he wouldn't follow me out of the cave until I played the frog's song.

-Sometimes, you can't pick up the flying rooster from certain angles. This has led to me getting softlocked at the end of narrow corridors, unable to lift the bird, but unable to walk past it either. Exiting to the title screen and reloading the game resolves this.

the keyhole of the face Shrine have the wrong key , in the code is use the fishkey to chek the lock.

Speaking of Rooster bugs, the Rooster sometimes has a physical collision like a wall or stone or bones, which could be related to the bones issue.  Mostly I see this when transitioning between squares on the map or transitioning squares in the caves, but sometimes just entering a cave does it.  Additionally after obtaining the Rooster, (but before completing dungeon 7), the rooster is actually there with you inside dungeons as well, just invisible with a pickup ability turned off.  The rooster has collision like a rock or bones during the entire time you are in the dungeon which has resulted in a soft lock in Turtle Rock by the lowest rightmost chets below the Rover's room.

Finally, the Rooster will also let you bypass needing to get the mirror shield as it flies over the flame thrower.   Or the game is just giving you invincibility when riding the rooster. 
The flame thrower should be the only thing that hurts you when riding if comparing the original.

You're bug report saved my game man!!!!! I thought armos was broken, thought I was going to have to abandon my game, thought he was unhittable UNTIL I read your bug report. 2 hits, killed him in 2 hits. I wonder why of all things he would change that