In general, when a creature enters the battlefield by any means (whether by Flickerwisp, Essence Flux, or otherwise), it can't attack and its abilities with the tap or untap symbol in their costs can't be activated until its controller begins a new turn with it continuously on the battlefield under their control (C.R. 302.6). For Flickerwisp, though, the card involved returns during the end step, not earlier in the turn.
EDIT: Struck out second sentence after comment 3 was posted; it was irrelevant.
EDIT (Oct. 12, 2019): Added text for correctness.
I'm not sure why the timing matters, given that you just said when it enters the battlefield "by any means" that it is subject to summoning sickness. It would make more sense as a loophole though, like when you "play" something versus "cast" something. It might make more sense based on the text "return" rather than "re-enter."
I'm not sure why the timing matters, given that you just said when it enters the battlefield "by any means" that it is subject to summoning sickness. It would make more sense as a loophole though, like when you "play" something versus "cast" something. It might make more sense based on the text "return" rather than "re-enter."
I'm not sure why the timing matters, given that you just said when it enters the battlefield "by any means" that it is subject to summoning sickness. It would make more sense as a loophole though, like when you "play" something versus "cast" something. It might make more sense based on the text "return" rather than "re-enter."
I edited comment 2 accordingly.
Okay so just to make sure, you are now saying that flickerwisp's ability does in fact cause summoning sickness?
When the card exiled with Flickerwisp returns, it will generally be subject to C.R. 302.6 (what is informally called the "summoning sickness" rule) in the same way as other creatures that have entered the battlefield. Here, whether the effect says "return ... to the battlefield" or "put ... onto the battlefield" doesn't matter.
Just as a quick question, blinking also causes a creature's equipment to become unattached from it right?
Yes. The creature leaves the battlefield and the equipment doesn't, so the equipment becomes unattached. The creature comes back as a new object and the equipment won't reattach to it on its own, you need an effect to equip it just like for any new creature.
Private Mod Note
():
Rollback Post to RevisionRollBack
I'm a former judge (lapsed), who keeps up to date on rules and policy. Keep in mind that judges' answers aren't necessarily more valid than those of people who aren't judges; what matters is we can quote the rules to back up our answers. When in doubt, ask for such quotes.
Just as a quick question, blinking also causes a creature's equipment to become unattached from it right?
Yes, because only the creature is exiled, but the equipment stays on the field. And as a sidenote, auras would find themselves unattached and go to the graveyard for the same reason.
For Flickerwisp, though, the card involved returns during the end step, not earlier in the turn.EDIT: Struck out second sentence after comment 3 was posted; it was irrelevant.
EDIT (Oct. 12, 2019): Added text for correctness.
Okay so just to make sure, you are now saying that flickerwisp's ability does in fact cause summoning sickness?
Wait, the rule says continuously "control." Do you still "control" a creature even if it's not in your battle zone?
Just as a quick question, blinking also causes a creature's equipment to become unattached from it right?
Yes, because only the creature is exiled, but the equipment stays on the field. And as a sidenote, auras would find themselves unattached and go to the graveyard for the same reason.
Former Rules Advisor
"Everything's better with pirates." - Lodge
(The Gamers: Dorkness Rising)
"Any sufficiently analyzed magic is indistinguishable from science."
(Girl Genius - Fairy Tale Theater Break - Cinderella, end of volume 8)