River Kelpie

Public decks that run River Kelpie

• Mystic Intellect - Commander 2019, led by Sevinne, the Chronoclasm
• Sultai Arisen - Tarkir: Dragonstorm Commander, led by Teval, the Balanced Scale

Commanders that run River Kelpie most

Deck counts from EDHREC.

• Teval, the Balanced Scale: 17,928 decks
• Muldrotha, the Gravetide: 7,417 decks
• Marchesa, the Black Rose: 5,656 decks
• Norman Osborn // Green Goblin: 4,475 decks
• Oskar, Rubbish Reclaimer: 1,659 decks
• Neerdiv, Devious Diver: 1,230 decks
• Princess Yue: 1,221 decks
• Sedris, the Traitor King: 854 decks

Often played with River Kelpie

Cards that show up in the same decks on EDHREC.

• Thalia's Geistcaller
• Ray of Distortion
• Purify the Grave
• Kitchen Finks
• Farm // Market
• Flayer of the Hatebound
• Death's Oasis
• Mark of Mutiny
• Pyreheart Wolf
• Voldaren Thrillseeker

Rulings

• 2008-05-01: River Kelpie doesn't give you the ability to cast spells from graveyards. Its second ability merely triggers whenever a spell is cast this way (by using Memory Plunder, for example).
• 2008-05-01: If you play a land card from a graveyard (by using Crucible of Worlds, for example), only the first ability triggers. That's because the land (which isn't a spell) is put directly onto the battlefield from the graveyard.
• 2008-05-01: If you cast another artifact, creature, enchantment, or planeswalker spell from a graveyard, only the second ability triggers. That's because the card is put onto the stack, not onto the battlefield.
• 2008-05-01: If River Kelpie and another permanent are each put onto the battlefield from a graveyard at the same time, River Kelpie's first ability will trigger twice. (It will see the other permanent entering.)
• 2008-05-01: If you cast River Kelpie itself from your graveyard (by using Yawgmoth's Will, for example), neither ability triggers. The first ability doesn't trigger because River Kelpie is put onto the stack; the second ability doesn't trigger because it works only while River Kelpie is already on the battlefield.
• 2013-06-07: When a permanent with persist returns to the battlefield, it's a new object with no memory of or connection to its previous existence.
• 2013-06-07: If a token with no -1/-1 counters on it has persist, the ability will trigger when the token is put into the graveyard. However, the token will cease to exist and can't return to the battlefield.
• 2013-06-07: If a permanent has multiple instances of persist, they'll each trigger separately, but the redundant instances will have no effect. If one instance returns the card to the battlefield, the next to resolve will do nothing.
• 2013-06-07: If multiple creatures with persist are put into the graveyard at the same time (due to combat damage or a spell that destroys all creatures, for example), the active player (the player whose turn it is) puts all of their persist triggers on the stack in any order, then each other player in turn order does the same. The last trigger put on the stack is the first one that resolves. That means that in a two-player game, the nonactive player's persist creatures will return to the battlefield first, then the active player's persist creatures do the same. The creatures return to the battlefield one at a time.
• 2013-06-07: If a creature with persist stops being a creature, persist will still work.
• 2013-06-07: The persist ability triggers when the permanent is put into a graveyard. Its last known information (that is, how the creature last existed on the battlefield) is used to determine whether it had a -1/-1 counter on it.
• 2013-06-07: If a creature with persist that has +1/+1 counters on it receives enough -1/-1 counters to cause it to be destroyed by lethal damage or put into its owner's graveyard for having 0 or less toughness, persist won't trigger and the card won't return to the battlefield. That's because persist checks the creature's existence just before it leaves the battlefield, and it still has all those counters on it at that point.