Azure Dreams Fusion Sprite Overwrite Glitch

Описание: I've discovered another glitch in Azure Dreams. This one "overwrites" the appearance of a familiar with that of another one, leading to some very crazy results. It appears to be mostly cosmetic at the moment and doesn't seem to have any beneficial uses so far beyond being fun to play around with. This video starts with some quick examples of what can be done by using this glitch and then jumps in to showing you how to do it, which I will explain below:

You will need to enter the tower with 3 Familiars and 2 Tumna Fruits.

Take out 2 Familiars. Feed a Tumna Fruit to each of them. Now fuse them together. The Familiar that gets absorbed is the one who will overwrite the sprite/appearance of the remaining third monster in your inventory.

Attempt to take out the third Familiar while the fused frog is still out. The game will not let you. Koh will open the bag and close it but the monster will not come out. (This step appears to be vital to getting the glitch to work and this is when the sprite gets overwritten we think).

Bag the fused frog and now take out your new creation.

As shown in the examples that follow, by changing the order of which Familiar gets absorbed and which one remains in your inventory you can create different combinations.

There are some rules that aren't understood yet regarding this glitch. For some reason it doesn't seem to work sometimes, and we're not sure why this happens or if it's only certain combinations of familiars that it works with it or what. The new appearance persists while you are in the tower, even when moving up floors, but upon returning home it resets to what it should normally be. Some animations crash or softlock the game so you will need to play around with this and see what does and doesn't work.

I want to give a special thanks and shout out to SandKnight of the Azure Dreams Speedrun community on Discord. I figured out how to do this late last night and he jumped right in to help me to test a lot of different things and was invaluable in figuring out how and why this glitch worked. We collaborated for a few hours in trying different things and without his help I'd still be trying to work out all the details of this trick.