When a creature is declared as a blocker, it becomes a 'blocking creature' and the blocked creature becomes 'blocked.' However, these combat statuses can be disrupted if a creature leaves the battlefield before the Damage step.
According to CR 509.2, a creature remains the blocking creature until it leaves the battlefield or the combat phase ends. If the blocker is 'bounced' (returned to its owner's hand) in response to blockers being declared — during the declare blockers step or before combat damage is dealt — it leaves the battlefield and is removed from combat entirely (CR 506.4).
Crucially, the blocked creature remains blocked even after the blocker leaves (CR 509.1h). Unless the attacker has trample, it will deal no combat damage to the defending player. The bounced creature, now safely in hand, neither deals nor receives any combat damage.
Example: You attack with a 3/3. Your opponent blocks with their 2/2. Before the Combat Damage step, you cast Unsummon targeting your opponent's 2/2, bouncing it to their hand. The 2/2 is gone — it deals no damage and takes none. Your 3/3 is still considered 'blocked' and, lacking trample, deals no damage to your opponent either.
This interaction is governed by CR 506.4 (creatures leaving combat), CR 509.1h (blocked status persists), and CR 510.1 (combat damage assignment requires creature to still be on battlefield and in combat).
Unofficial fan resource — not affiliated with or endorsed by Wizards of the Coast. Answers are AI-generated estimates grounded in the Comprehensive Rules and are not a substitute for an official judge. Verify anything match-critical.