Fate Egg Bugs in PvP

[YawnChainHow]

First noticed during a mirror duel vs ddevans96, this bug was confirmed during a second duel.



What appears to happen is that hatching an Egg produced by a MitoSoR'd Egg would produce a random creature (usual behavior) plus a copy of that creature (which looked as if Parallel Universe was casted on it.

This copy ("ghost") would vanish at the end of the turn, deal no damage, fail to mimic actions of the original creature, and generally leave no trace of its existence. This makes me believe that it is merely a graphical error, but I have not tested it extensively.

We confirmed through the ingame chat, and afterwards, that we were indeed playing each other (as opposed to an AI) during the match.

Things I have not tested: Hatching Eggs that did not originate from Mitosis after the combo is played; behavior with a full field (therefore no place for the copy to appear)

We also desynced during the second match (though not the first) and this behavior was consistent throughout, which is to say that it was not caused by desync.

[ddevans96]

What Yawn said. He pretty much summed everything up.

[furballdn]

I remember seeing a glitch like this happen in pvp before, asking about it on forums, and I heard that it was a confirmed bug.

[bogtro]

Fate Eggs have always caused a desync with me, spawning two creatures with the other disappearing later on. This occurred even without the MitoSoR interaction.

[Wizy]

This happens since the change to SoR, when an egg hatches, it makes a clone and then if a SoR was not used on the egg the clone dies.
But it is not only graphical. When the clone dies, it generates a dead effect. If bone wall/boneyard/scavenger is in play, it is pretty much guaranteed to cause desynch.

[TheonlyrealBeef]

As long as SoR is used on the Eggs or no creatures fill the board after an Egg hatches without SoR and there is nothing that benefits from death effects no desynch will occur.

Spoiler for pictures:

Charger was with SoR, Photon without, neither caused a desynch since the Charger spawned perfectly and the incorrectly showing up extra Photon appeared and disappeared without causing inconsistencies.

However, a Fate Egg was played after hatching the Octopus but before ending the turn so a desynch occurs, because two creatures can't occupy the same place (the Fate Egg and the illegal copy).

Graphical error of two spawning will always occur and the illegal duplicate will die without attacking, death effects will take effect on one side and the desynch may be "corrected" by also applying it to the other side (a death effect that should never have occurred).

Spoiler for screenshot:

Hatched two Fate Eggs and then played a third vs a 7 counter Bone Wall. Initially shows 7 counters.

Illegal copies spawn, their places illegal, causing desynch and their removal death effects. See how left currently shows 5 BW counters whilst right shows 9.

After passing another turn from the left side the BW counter is back at 7 to "fix" for the desynch...

Moving to confirmed and changing title to describe the general case: Mitosis is not a factor and it's more than just graphical (death effects).

[Bloom]

Hey guys I'm currently in a game where SoR was used on a Fate Egg which proceeded to "hatch" 2 Arctic Dragons. Neither of them died and they both behaved like normal creatures.

[bogtro]

This is intended behavior - SoR causes 2 copies of the same creature from one fate egg. The graphical error of 2 spawning without an SoR is a bug however.

[RootRanger]

Ah, this reminds me of the fate egg tournament. There were so many desyncs that it went on for six hours. Good times, good times.

[Bloom]

This is intended behavior - SoR causes 2 copies of the same creature from one fate egg. The graphical error of 2 spawning without an SoR is a bug however.

Prior to the dragons appearring, he also SoR'd another Fate Egg and it only produced one Elite Wyrm. That's what really confuzzled me.