[fixed/closed]Godsend equipped deals damage through block

[Nexhro]

Describe the Bug:
When a creature equipped with Godsend is blocked by one creature and the latter is exiled by Godsend 's triggered ability, the first creature deals combat damage to the attacked player, even if it doesn't have trample.

Which card did behave improperly ?
Godsend

Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
JOU v1, duel

What exactly should be the correct behavior/interaction ?

510.1c A blocked creature assigns its combat damage to the creatures blocking it. If no creatures are currently blocking it (if, for example, they were destroyed or removed from combat), it assigns no combat damage. If exactly one creature is blocking it, it assigns all its combat damage to that creature. If two or more creatures are blocking it, it assigns its combat damage to those creatures according to the damage assignment order announced for it. This may allow the blocked creature to divide its combat damage. However, it can't assign combat damage to a creature that's blocking it unless, when combat damage assignments are complete, each creature that precedes that blocking creature in its order is assigned lethal damage. When checking for assigned lethal damage, take into account damage already marked on the creature and damage from other creatures that's being assigned during the same combat damage step, but not any abilities or effects that might change the amount of damage that's actually dealt. An amount of damage that's greater than a creature's lethal damage may be assigned to it.

Are any other cards possibly affected by this bug ?
-

[Korath]

The becomes-blocked event in Manalink gets sent before cards are flagged as having been blocked, so it's a bit surprising this hasn't shown up earlier. "When [this creature] becomes blocked, destroy the other creature" (such as Wooden Stake, though that apparently got broken at some point), "...this creature deals X damage to target creature" (such as Laccolith Grunt, aimed at the blocker), and "...the other creature ends up with -X toughness" (such as Saprazzan Heir against a Nyxathid) all manage not to trigger this bug through different methods, mostly by accident. Exiling and sacrificing "properly" get rid of the blocker immediately, though. Worked around in 4a38041.