← Back Card Profile (by Name)

Elspeth's Nightmare PLST

Other printings of "Elspeth's Nightmare": PLST #THB-91 THB #91

Card

id71513
artistJason Rainville
artistIds6ed7e669-579b-443d-b223-e5cbcb2a7483
asciiName
attractionLights
availabilitypaper
boosterTypesdefault
borderColorblack
colorIdentityB
colorIndicator
colorsB
defense
duelDeck
edhrecRank9708
edhrecSaltiness0.22
faceConvertedManaCost
faceFlavorName
faceManaValue
faceName
finishesnonfoil
flavorName
flavorText
frameEffects
frameVersion2015
hand
hasAlternativeDeckLimit
hasContentWarning
hasFoil0
hasNonFoil1
isAlternative
isFullArt
isFunny
isGameChanger
isOnlineOnly
isOversized
isPromo
isRebalanced
isReprint1
isReserved
isStarter
isStorySpotlight
isTextless
isTimeshifted
keywords
languageEnglish
layoutsaga
leadershipSkills
life
loyalty
manaCost{2}{B}
manaValue3
nameElspeth's Nightmare
numberTHB-91
originalPrintings
originalReleaseDate2024-08-02
originalText
otherFaceIds
power
printingsPLST, THB
promoTypes
rarityuncommon
rebalancedPrintings
relatedCards
securityStamp
setCodePLST
side
signature
sourceProducts{'nonfoil': ['1db93605-0a4e-5e5b-80a2-18a6e177f51d']}
subsets
subtypesSaga
supertypes
text(As this Saga enters and after your draw step, add a lore counter. Sacrifice after III.)
I — Destroy target creature an opponent controls with power 2 or less.
II — Target opponent reveals their hand. You choose a noncreature, nonland card from it. That player discards that card.
III — Exile target opponent's graveyard.
toughness
typeEnchantment — Saga
typesEnchantment
uuide7f89ff1-3caa-500a-8ebd-c2f68fba5cf8
variations
watermark
setNameThe List

Identifiers

id71513
cardKingdomEtchedId
cardKingdomFoilId
cardKingdomId303870
cardsphereFoilId
cardsphereId128107
deckboxId96029
mcmId
mcmMetaId
mtgArenaId
mtgjsonFoilVersionId
mtgjsonNonFoilVersionId
mtgjsonV4Id0b3a1520-8933-50b2-85c5-33cbd9419038
mtgoFoilId
mtgoId
multiverseId
scryfallCardBackId0aeebaf5-8c7d-4636-9e82-8c27447861f7
scryfallId9ecb1fd2-74e1-4981-bbc9-dc4a7e0fb7b1
scryfallIllustrationId5dfe16a3-7c4a-4b84-8470-511e713c43c5
scryfallOracleIdff768016-67f8-409e-8359-9ed05bcb46d2
tcgplayerEtchedProductId
tcgplayerProductId582662
uuide7f89ff1-3caa-500a-8ebd-c2f68fba5cf8

Legalities

id71513
alchemy
brawlLegal
commanderLegal
duelLegal
future
gladiatorLegal
historicLegal
legacyLegal
modernLegal
oathbreakerLegal
oldschool
pauper
paupercommander
penny
pioneerLegal
predh
premodern
standard
standardbrawl
timelessLegal
uuide7f89ff1-3caa-500a-8ebd-c2f68fba5cf8
vintageLegal

Purchase URLs

id71513
cardKingdomhttps://mtgjson.com/links/6e5fa3d89c50584b
cardKingdomEtched
cardKingdomFoil
cardmarket
tcgplayerhttps://mtgjson.com/links/e498bcb8825a5e1f
tcgplayerEtched
uuide7f89ff1-3caa-500a-8ebd-c2f68fba5cf8

Foreign Data (per language)

No foreign data.

Rulings

datetext
2020-01-24A chapter ability doesn’t trigger if a lore counter is put on a Saga that already had a number of lore counters greater than or equal to that chapter’s number. For example, the third lore counter put on a Saga causes the III chapter ability to trigger, but I and II won’t trigger again.
2020-01-24As a Saga enters the battlefield, its controller puts a lore counter on it. As your precombat main phase begins (immediately after your draw step), you put another lore counter on each Saga you control. Putting a lore counter on a Saga in either of these ways doesn’t use the stack.
2020-01-24Each symbol on the left of a Saga’s text box represents a chapter ability. A chapter ability is a triggered ability that triggers when a lore counter that is put on the Saga causes the number of lore counters on the Saga to become equal to or greater than the ability’s chapter number. Chapter abilities are put onto the stack and may be responded to.
2020-01-24If multiple chapter abilities trigger at the same time, their controller puts them on the stack in any order. If any of them require targets, those targets are chosen as you put the abilities on the stack, before any of those abilities resolve.
2020-01-24Once a chapter ability has triggered, the ability on the stack won’t be affected if the Saga gains or loses counters, or if it leaves the battlefield.
2020-01-24Once the number of lore counters on a Saga is greater than or equal to the greatest number among its chapter abilities, the Saga’s controller sacrifices it as soon as its chapter ability has left the stack, most likely by resolving or being countered. This state-based action doesn’t use the stack.
2020-01-24Removing lore counters won’t cause a previous chapter ability to trigger. If lore counters are removed from a Saga, the appropriate chapter abilities will trigger again when the Saga receives lore counters.

Tip: bookmark this page with your query parameters for quick access.